uzix/picocom
1
0
Fork 0
mirror of https://github.com/UzixLS/picocom.git synced 2025-07-19 07:21:18 +03:00
Code Issues Projects Releases Wiki Activity

Merged bash_completion/readme.txt in README.md

Browse Source
This commit is contained in:
Nick Patavalis
2018-02-10 10:52:40 +02:00
parent a6a7c70f1b
commit fc44525696
2 changed files with 73 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

73
README.md
View File

@ -189,6 +189,79 @@ or (assuming you have installed the manual page to a suitable place):
Thanks for using picocom
## Custom bash completion
Starting with release 3.2, picocom includes support for custom
bash-shell completion. With this you can press the [TAB] key and the
bash shell will complete command-line option names and values and
propose valid selections for both. This makes the experience of using
picocom more pleasant.
Custom bash-shell completion works only with recent versions of the
bash shell (>= 4.3). Here's how you can enable it.
To manually enable custom completion support you need to source the
file (custom completion script):
<picocom source dir>/bash_completion/picocom
Assuming you are inside the picocom source directory, you can do it
like this:
. ./bash_completion/picocom
This will enable custom completion support for the current shell
session only. Give it a ride and see if you like it.
To enable support automatically for all bash-shell sessions, you have
the following options:
1. If you are running a relatively modern Debian or Ubuntu or other
Debian-based distribution, and you have package bash-completion
installed, you can simply copy the custom completion script to the
directory:
/etc/bash_completion.d/
Obviously, you need to be root to do this. Assuming you are inside
the picocom source directory, something like this will do it:
sudo cp ./bash_completion/picocom /etc/bash_completion.d/
This will enable custom completion support for picocom, globaly
(for all bash-shell users).
For other distributions and operating systems you have to check
their documentation to see if they provide a similar mechanism for
automatically sourcing custom completion scripts.
2. If you want to automatically enable support *only for the current
user*, you must arange for your user's `.bashrc` to source the
custom completion script. There are, obviously, many ways to do
this, so the following *is only a suggestion*:
Create a directory to keep the custom completion scripts
mkdir ~/.bash_completion.d
Copy the picocom completion script to the directory you
created. Assuming you are inside the picocom source directory:
cp ./bash_completion/picocom ~/.bash_completion.d
Add the following (or similar) to the end of your `.bashrc`
# Source custom bash completions
if [ -d "$HOME"/.bash_completion.d ]; then
for c in "$HOME"/.bash_completion.d/*; do
[ -r "$c" ] && . "$c"
done
fi
From now on every new shell session you start will load (source)
all the custom completion scripts you have put in
`~/.bash_completion.d`
## A low-tech terminal server
You can use *picocom* to patch-together a very simple, *very

70
bash_completion/readme.txt
View File

@ -1,70 +0,0 @@
Starting with release 3.2, picocom includes support for custom
bash-shell completion. With this you can press the [TAB] key and have
the bash shell complete command-line option names and values and
propose valid selections for both. This makes the experience of using
picocom much more pleasant.
Custom bash-shell completion works only with recent versions of the
bash shell (>= 4.3).
To manually enable custom completion support you need to source the
file (custom completion script):
<picocom source dir>/bash_completion/picocom
Assuming you are inside the picocom source directory, you can do it
like this:
. ./bash_completion/picocom
This will enable custom completion support for the current shell
session only. Give in a ride and see if you like it.
To enable support automatically for all bash-shell sessions, you have
the following options:
1. If you are running a relatively modern Debian or Ubuntu or other
Debian-based distribution, you can simply copy the custom
completion script to the directory:
/etc/bash_completion.d/
Obviously, you need to be root to do this. Assuming you are inside
the picocom source directory, something like this will do it:
sudo cp ./bash_completion/picocom /etc/bash_completion.d/
This will enable custom completion support for picocom, globaly
(for all bash-shell users).
For other distributions and operating systems you have to check
their documentation to see if they provide a similar mechanism for
automatically sourcing custom completion scripts.
2. If you want to automatically enable support *only for the current
user*, you must arange for your user's `.bashrc` to source the
custom completion script. There are, obviously, many ways to do
this, so the following *is only a suggestion*:
Create a directory to keep the custom completion scripts
mkdir ~/.bash_completion.d
Copy the picocom completion script to the directory you
created. Assuming you are inside the picocom source directory:
cp ./bash_completion/picocom ~/.bash_completion.d
Add the following to the end of your `.bashrc`
# Source custom bash completions
if [ -d "$HOME"/.bash_completion.d ]; then
for c in "$HOME"/.bash_completion.d/*; do
[ -r "$c" ] && . "$c"
done
fi
From now on every new shell session you start will load (source)
all the custom completion scripts you have put in
`~/.bash_completion.d`