NonGNU-devel ELPA - bash-completion

bash-completion

Description
Bash completion for the shell buffer
Latest
bash-completion-3.1.1.0.20230612.110320.tar (.sig), 2024-Mar-31, 100 KiB
Maintainer
Stephane Zermatten <szermatt@gmail.com>
Atom feed
bash-completion.xml
Website
http://github.com/szermatt/emacs-bash-completion
Browse ELPA's repository
CGit or Gitweb
Badge

To install this package from Emacs, use package-install or list-packages.

Full description

bash-completion for Emacs test melpa melpa-stable

bash-completion.el defines dynamic completion hooks for shell-mode and shell-command prompts that is based on bash completion.

Bash completion for Emacs:

  • is aware of bash builtins, aliases and functions
  • does file expansion inside of colon-separated variables and after redirections (> or <)
  • escapes special characters when expanding file names
  • is configurable through programmable bash completion
  • works on remote shells, through TRAMP.

A simpler and more complete alternative to bash-completion.el is to run a bash shell in a buffer in term mode (M-x ansi-term). Unfortunately, many Emacs editing features are not available when running in term mode. Also, term mode is not available in shell-command prompts.

INSTALLATION

Copy bash-completion.el into a directory that's on Emacs load-path. You can do that manually, or by installing it from MELPA.

Shell completion

To enable bash completion in shell buffers as well as in command prompts, such as the prompt started by compile, add the hook bash-completion-dynamic-complete to shell-dynamic-complete-functions.

For example:

elisp (autoload 'bash-completion-dynamic-complete "bash-completion" "BASH completion hook") (add-hook 'shell-dynamic-complete-functions 'bash-completion-dynamic-complete)

or simpler, but forces you to load bash-completion at startup:

elisp (require 'bash-completion) (bash-completion-setup)

After that reload your .emacs (M-x eval-buffer) or restart.

When called from a bash shell buffer, bash-completion-dynamic-complete communicates with the current shell to reproduce, as closely as possible the normal bash auto-completion, available on full terminals.

When called from non-shell buffers, such as the prompt of M-x compile, bash-completion-dynamic-complete creates a separate bash process just for doing completion. Such processes have the environment variable EMACS_BASH_COMPLETE set to t, to help distinguish them from normal shell processes.

Completion at point

You can also use bash completion as an additional completion function in any buffer that contains bash commands. To do that, add bash-completion-capf-nonexclusive to the buffer-local completion-at-point-functions. For example, you can setup bash completion in eshell-mode by invoking

elisp (add-hook 'eshell-mode-hook (lambda () (add-hook 'completion-at-point-functions 'bash-completion-capf-nonexclusive nil t)))

There is also a lower-level function bash-completion-dynamic-complete-nocomint which allows you to construct your own completion-at-point function.

elisp (bash-completion-dynamic-complete-nocomint COMP-START COMP-POS DYNAMIC-TABLE)

COMP-START is where the bash command starts --- it depends on the mode of the calling buffer. In most cases, line-beginning-position works because it uses field boundaries.

COMP-POS is usually the current position of the cursor.

When calling from completion-at-point, make sure to pass a non-nil value to the DYNAMIC-TABLE argument so it returns a function instead of a list of strings. This isn't just an optimization: returning a function instead of a list tells Emacs it should avoids post-filtering the results and possibly discarding useful completion from bash.

TROUBLESHOOTING

If completion in a bash shell doesn't behave as you think it should, check the following:

  • Does bash behave differently when run outside of Emacs? If not, check your shell configuration.
  • Call M-x bash-completion-debug and look at the output-buffer section. Does it match the expected set of completion? If yes, it might be a display problem. Are you using a completion engine other than the default, such as ivy or helm? Try turning it off to confirm, then file a bug
  • If all else fails, file a bug. Please include the output of M-x bash-completion-debug, the command you're trying to use and the function or package providing completion for that command and where to download it.

CONTRIBUTING

To report bugs, features or even to ask questions, please open an issue. To contribute code or documentation, please open a pull request.

See CONTRIBUTING.md for more details.

COMPATIBILITY

bash-completion.el is known to work with Bash 4.2 and later and Bash 5, on Emacs, starting with version 25.3, under Linux and OSX.

Old versions

bash-completion-3.1.1.0.20230607.93124.tar.lz2023-Jun-0724.2 KiB
bash-completion-3.1.1.0.20230315.191832.tar.lz2023-Mar-1524.2 KiB
bash-completion-3.1.1.0.20230309.155634.tar.lz2023-Mar-0924.1 KiB
bash-completion-3.1.1.0.20230302.195945.tar.lz2023-Mar-0224.1 KiB
bash-completion-3.1.1.0.20230225.191542.tar.lz2023-Feb-2523.9 KiB
bash-completion-3.1.1.0.20230208.190338.tar.lz2023-Feb-0824.0 KiB
bash-completion-3.1.1.0.20230201.181022.tar.lz2023-Feb-0123.7 KiB
bash-completion-3.1.1.0.20230131.173938.tar.lz2023-Jan-3123.5 KiB
bash-completion-3.1.1.0.20230115.184752.tar.lz2023-Jan-1523.7 KiB
bash-completion-3.1.0.0.20220531.110444.tar.lz2022-Dec-0334.7 KiB