From bfd4555f960a888085745fc50deb17a6aae9703b Mon Sep 17 00:00:00 2001 From: Kévin Le Gouguec Date: Sat, 4 Feb 2023 12:50:20 +0100 Subject: Refine bash-completion sales pitch --- itches/emacs/interpreters.org | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'itches/emacs/interpreters.org') diff --git a/itches/emacs/interpreters.org b/itches/emacs/interpreters.org index bb53fa5..7273a3c 100644 --- a/itches/emacs/interpreters.org +++ b/itches/emacs/interpreters.org @@ -30,11 +30,14 @@ Bash's; e.g. typing ~ls TAB~ in a folder with a single file expands to Also, in general, =*shell*= has no clue about - changes to =$PATH=, which affect what programs are available, -- Bash aliases, - changes to the current working directory not triggered by an explicit ~cd~, and not announced by OSC 7, -- commands (functions, aliases) defined during the session -- etc. +- commands (functions, aliases) defined… + - in startup files (=.bashrc= et al.), + - during the interactive session, +- programmable completions contributed by authors of CLI applications. + +Querying Bash for completions would solve all of the above. See [[https://debbugs.gnu.org/26661][bug#26661]], and [[https://github.com/szermatt/emacs-bash-completion/issues/45][szermatt/emacs-bash-completion!45]]. ** Handle DECSC, DECRC, CUU, ED, HVP and DECSTBM console codes -- cgit v1.2.3