Show slash if a directory upon TAB

$ pdf pdf pdf2ps pdfcrack pdffonts pdfinfo pdfsig pdftocairo pdftoppm pdftotext pdf2dsc pdfattach pdfdetach pdfimages pdfseparate pdftexi2dvi pdftohtml pdftops pdfunite What's this, a new command called "pdf". I must try it! $ pdf bash: pdf: command not found $ ls -d pdf pdf Oh, all along it was

Junk at the end on history

$ history works fine if I pipe it into tail. But if I just let it pour out on the screen, I get this junk after it sitting at the prompt: 9997 Tue, 04 Apr 2023 17:31:36 +0800 history 9998 Tue, 04 Apr 2023 17:31:59 +0800 history |tail Tue, 04 Apr 2023 17:32:06 +0800 history $ 64;1;2;6;9;1

Re: Junk at the end on history

There probably was. Say, there should be a way to protect the user against something like that. I wish I could just tell it to only allow utf-8 in my history.

Re: Junk at the end on history

Sorry everybody. I cannot reproduce it. Nor is anything wrong with the HISTFILEs... It must of had something to do with me exploring many "i3" windows configurations that day.

Document m=1 m=2; echo $m result

man page says: A variable may be assigned to by a statement of the form name=[value] If value is not given, the variable is assigned the null string. All values undergo tilde expansion, parameter and variable expansion... OK, but do please mention s

Re: Document m=1 m=2; echo $m result

> "LV" == Lawrence Velázquez writes: LV> This is stated under "Simple Command Expansion". OK good. No more issue.

set -x vs. n=($@)

It's not fair: set -x a b c m=$@ n=($@) == gives == + m='a b c' + n=($@) please either say + m=$@ + n=($@) or better: + m='a b c' + n=('a' 'b' 'c') or metion on https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html the special exception. GNU bash, version 5.2.15

Warn upon "declare -ax"

Shouldn't "declare -ax" print a warning that it is useless?

Re: set -x vs. n=($@)

m=$@; n=($@)' + m='a b c' + n=($@) ) >>>>> "CR" == Chet Ramey writes: CR> On 9/3/23 6:08 AM, Dan Jacobson wrote: >> It's not fair: >> set -x a b c >> m=$@ n=($@) >> == gives == >> + m='a b c' >> + n=($@)

Make reverse-i-search failure joltingly clear

Type ^R and some string, At the point while we are typing that the search fails, all that happens is the word "failed" gets added at front, (reverse-i-search)`nni': set jida^Ci.org/geo/house_numbering/grids/us/il/lake/lake_county/ (failed reverse-i-search)`nnii': set jida^Ci.org/geo/house_number

Re: Make reverse-i-search failure joltingly clear

Well these days the chances of bells, visual or audible, getting through are less and less, e.g., https://github.com/alacritty/alacritty/issues/1528 and on chromebook one must turn the bell on, etc. So I still think something different should happen than each forlorn character just mounting up on

Add example of bind readline-command-line

bash man page says -v Display readline variable names and values in such a way that they can be re-read. Perhaps add an example of rereading via the bind command: $ bind 'set bell-style visible' else the user might try: $ echo set bell-style visible|bind Yes,

Add option to just print history, with no added timestamps or line numbers

$ help history should mention how in the world one is supposed to just print the plain history, without any line numbers or time stamps. You might say, "Just strip it off with perl or sed." Well, fine. Then mention that in help history. Currently one needs massive superfund environmental clean-u

Re: Add option to just print history, with no added timestamps or line numbers

> "MDK" == Martin D Kealey writes: MDK> How about « fc -ln » ? I like it! P.S., $ help fc -nomit line numbers when listing Yes, it omits the line numbers. But leaves the "^I " separators! $ fc -l 999 1000|cat -vt 999^I echo invite Nerbleson for dinner 1000^I echo and Snordsw

Re: Add option to just print history, with no added timestamps or line numbers

How unfortunate. P.S., "\t%s" seems to have an extra space squeezed between them with bash: "\t %s", unless perhaps the spec says that %s always starts with a space.

Re: Add option to just print history, with no added timestamps or line numbers

Hmm, so no matter POSIX mode or not, both will be dragging around that little piece of toilet paper stuck to their shoes (\t)... unless some new option is invented.

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

Thanks fellows but now bash has become very slow to the touch that way.

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

Can you somehow give the user his prompt first and then wait, instead of the other way around? Also rapid ^P RET ^P RET should somehow be exempt.

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

> "PG" == Pierre Gaston writes: PG> Maybe try something like: PROMPT_COMMAND='read -t0 && sleep 10' But how will that on its own stop me from dumping tons of lines of junk into bash via one accidental mouse click?

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

Ah ha! Thanks for the private tip 4 minutes ago. This works!: saftey_seconds=5 PROMPT_COMMAND='if ((SECONDS==0)); then echo TOO FAST HOLMES, waiting '\ $saftey_seconds' seconds or hit ^C; sleep '$saftey_seconds'; else SECONDS=0; fi' Hope somebody documents it somewhere as otherwise, well, "the sh

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

case $- in *i*) saftey_seconds=5 SECONDS=1 PROMPT_COMMAND="if ((SECONDS==0)); then echo TOO FAST HOLMES, waiting \ $saftey_seconds seconds or hit ^C; sleep $saftey_seconds; else SECONDS=0; fi" esac

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

OK fixed spelling. Put in .bashrc to prevent accidental execution of many line clipboard paste dumps: case $- in *i*) safety_seconds=5 SECONDS=1 PROMPT_COMMAND="if ((SECONDS==0)); then echo TOO FAST HOLMES, waiting \ $safety_seconds seconds or hit ^C; sleep $saftey_seconds; else SEC

Segmentation fault when -x is added and variable contains nulls

# su - nobody No directory, logging in with HOME=/ $ cat /tmp/r LC_CTYPE=zh_TW.UTF-8 N=$(echo 統一|iconv -t big5 -f utf-8) sh -xc ': $N' $ sh /tmp/r /tmp/r: line 1: 4551 Segmentation fault LC_CTYPE=zh_TW.UTF-8 N=$(echo 統一|iconv -t big5 -f utf-8) sh -xc ': $N' Something about that embedded nul

Re: Segmentation fault when -x is added and variable contains nulls

What a clod I was, thinking @ was ^@. OK glad you guys are hot on the trail.

Hitting C-c C-c in Emacs' *shell* causes segmentation fault

Dear Bug-Bash gentlemen, http://debbugs.gnu.org/16665 says it seems like a bash bug. Please have a look if you are also an emacs person.

Re: Hitting C-c C-c in Emacs' *shell* causes segmentation fault

> "CR" == Chet Ramey writes: CR> OK, I'll bite. What is C-c C-c supposed to do? It looks like it just CR> spews a bunch of garbage to your screen. Is that the intent? C-c C-c runs the command comint-interrupt-subjob, which is an interactive compiled Lisp function in `comint.el'. (comint-

two ESC . in a row on a fresh shell kills it

Try su - nobody #(pristine account) then type : then type ESC . ESC . Whammo! The shell dies! The second ESC . acts like ^D. # su - nobody No directory, logging in with HOME=/ nobody@jidanni5:/$ cd /tmp nobody@jidanni5:/tmp$ script Script started, file is typescript nobody@jidanni5:/tmp$ : nobody

~ vs. filename expansion

Hitting TAB twice at the end of nobody@jidanni5:/$ : /home/jidanni/jidanni.org/location/directions/ nobody@jidanni5:/$ : ~jidanni/jidanni.org/location/directions/ shows a list of list of the filenames for the former, but not the latter. Indeed the for the latter one will have to type the filenames

Bug#739835: ~ vs. filename expansion

X-debbugs-cc: chet.ra...@case.edu bug-bash@gnu.org Package: bash-completion Version: 1:2.1-2 >>>>> "CR" == Chet Ramey writes: CR> On 2/21/14, 9:33 PM, Dan Jacobson wrote: >> Hitting TAB twice at the end of >> nobody@jidanni5:/$ : /home/jidanni/jidanni.org

user not informed of inputrc errors

In the man page history-preserve-point needs its default value listed: history-preserve-point (Off) P.S., let's say one just wants to turn it on for a couple of commands. The man page's Readline Initialization section makes it seem that the only chance of setting history-preserve-poi

^B should be allowed to climb back up to the previous line

It seems ^B should be allowed to climb back up to the previous line here, instead of only allowing ^P to do it: $ e\ > f^B^B ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Re: ^B should be allowed to climb back up to the previous line

>> It seems ^B should be allowed to climb back up to the previous line >> here, instead of only allowing ^P to do it: >> $ e\ >> >>> f^B^B Chet> Why? To readline, they're two separate lines. Well real emacs can. So we emacs users get the feeling that something is broken and give up hope of get

Re: transpose-words on $? $@

This happened in Makefile mode. Well OK, they aren't words. By the way, in bash, one at least gets a beep and the cursor doesn't move. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

set -x makes "r=1 echo" and "r=1; echo" look the same

Hurmf, I don't like how the former looks like it was two separate commands according to set -x: $ set -x $ r=1 echo + r=1 + echo $ r=1; echo + r=1 + echo They shouldn't give exactly the same, no? ___ Bug-bash mailing list Bug-bash@gnu.org http://lists

help should check 2nd ... args

$ help : ! :: : No effect; the command does nothing. A zero exit code is returned. What about that second argument? $ help ! bash: help: no help topics match `!'. Try `help help' or `man -k !' or `info !'. Regarding RESERVED WORDS $ set ! case do done elif else esac fi for function \ if

wishlist: an absolute ESC .

How can one make a "ESC ." command that will get the last word from the last line, even if we have just hit a few ^P's? ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

set -x and $''

Interesting, here in big5 land I notice set -x will encode into octal its output unless the item has certian printing non alphanumerics in it I suppose. Anyways, there should be a way to tell set -x that one doesn't want the $'' help, and would just like the raw chars. Also a way to have set -x pri

$(case x in x)...

The man page berates old-timers: When the old-style backquote form of substitution is used... However, who is it that is too hungry for the next ")"?: $ k=$(case x in x) :;; esac) bash: syntax error near unexpected token `;;' $ k=$(case x in x) :; esac) bash: syntax error near unexpected tok

prompt miscalculations seen more often in 3.1.0?

Prompt miscalculations seems to happen slightly more in 3.1.0? Live with this below script for a few days and often using ^R, ^A, combined with inserting characters etc. and you too should see how often bash miscalculates where things are on the screen. It's hard to describe, so no precise examples

yank-last-arg after a #

I do $ # x y z $ zzz the ESC. doesn't get the last argument these days if there was a #. I get a bell. OK, I'll use ":" then I suppose now. Wait, $ xx yy zz # qq ESC. still gets the qq. And ^P still recalls lines, no matter where the # is. bash3.1.0(1). __

man page doesn't say typeset obsolete

But the man page doesn't say obsolete: $ help typeset typeset: typeset [-afFirtx] [-p] name[=value] ... Obsolete. See `declare'. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

say how to remove functions too

The FUNCTIONS part of the man page should mention that functions can be destroyed with unset, even if it is mentioned elsewhere. E.g., unalias is mentioned right away in the ALIAS section. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/

expansion fails upon pipes in big5 chars

$ echo 05017法規修訂座* 05017法規修訂座談會-1.pdf 05017法規修訂座談會.pdf hitting tab gets caught in the hidden "|" in the last byte: $ echo 05017法規修訂座談愧| Display all 3261 possibilities? (y or n) Therefore bash filename expansion fails upon pipes in big5 chars $ echo 會|qp-encode =B7| It knows it is one char though:

Re: yank-last-arg after a #

>> $ xx yy zz # qq >> ESC. still gets the qq. C> I get `zz'. Oops, me too. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

can't expand after colon

Must one use \: to make this work? $ cd /tmp/jidanni.org jidanni.org/ jidanni.org:2082/ $ cd /tmp/jidanni.org: Display all 456 possibilities? (y or n) ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

whole line echoed every char I type

Holy moly, without LC_ALL=C, for every character I type, the whole line is echoed! 03:39 ~$ LC_ALL=C script Script started, file is typescript 03:39 ~$ exit Script done, file is typescript 03:39 ~$ cat -v typescript Script started on Tue Jan 24 03:39:46 2006 ^[[01;35m03:39 ~$^[[00m exit^M Script

Re: whole line echoed every char I type

If I do set +o emacs, the problem goes away. Anyway, you must admit it is a big problem. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

one by one undo the undos

We see: (C-_, C-x C-u) Incremental undo, separately remembered for each line. Each line? Fancy. I'd trade it for a way to back out once one has undone too much. Like real emacs, one can do e.g., ^F to break the undo "habit" and then begin undoing the undos. With bash there is no way

warn on bad $'...' stings?

Maybe there should be a mechanism to output warning or $?=1 for things like $ echo $'\0x11' where the user has fudged the syntax etc. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

document that echo can't be given a NULL

No way to hand echo or /bin/echo a NULL. $ set a $'\x00' b $ echo $# 3 $ echo A$'\x01'B|wc -c 4 $ echo A$'\x00'B|wc -c 3 $ echo -n `echo -ne 000`|wc -c 0 BASH_VERSION='3.1.0(1)-release' At least the echo docs should say so. ___ Bug-bash mailing lis

"syntax error near unexpected token `done'" could be more wordy

$ for i do case $i in *!*) echo $i;done bash: syntax error near unexpected token `done' Well OK, but you could also say "... while looking for esac ...". I bet perl would say that if it had esacs. Would help in big programs. ___ Bug-bash mailing list B

HISTFILE vs. two or more bashes

The HISTORY section on the man page should mention the case where one has one bash session in one window, and another in another, etc., both with all the same history related environment variables, including $HISTFILE, inherited from a parent shell. Is it only the shell that exits last the one who

current input line lost on ^Z

Perhaps bad? $ cat > p bb ccc^Z $ something_else $ fg zzz ^D $ cat pr bb zzz "I was not finished composing line ccc when I had to do something_else. Now I have to remember what I was typing to type line ccc all over again, and it might not even be left o

message: ^Z: nothing to suspend

Maybe bash should print a message when one hits ^Z but there is nothing to suspend: $ bla& ^Z bash: useless hit of ^Z or bash: ^Z: nothing to suspend ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

mention kill 0

The kill(1) man page doesn't mention "kill 0". /bin/kill 0 #scripts proceed no further The bash man page mentions kill 0, but not in its main kill paragraph. The bash man page doesn't mention kill -1. The bash "help kill" bulrb doesn't mention kill 0 or -1. The kill(1) man page, as of procps: Ins

Re: message: ^Z: nothing to suspend

By the way, printing such a message, one could tell if one's program died and we are back in the shell or is just not responding. (Yes one can also see Terminated messages.) ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinf

set -e vs. !

$ cat t.sh set -ex ! true #should stop here but doesn't!?! ! false true false : already quit $ bash t.sh + true + false + true + false $ pdksh t.sh + true $ dash t.sh + true + false + true + false ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.

${//}: say how to non-destructively prefix/suffix

Regarding the ${parameter/pattern/string} ${parameter//pattern/string} discussion on the man page: You don't mention what if pattern is null. Seems that will never match. Anyway, no way to $ set aa bb cc $ echo [EMAIL PROTECTED] so that one gets all parameters to have a string appende

need \:

Not sure if there is much that can be done here. The user needs to know to enter \: instead of : which causes him to just see the files in $PWD. Wait, is needing a \ reasonable? $ man /usr/share/man/man3/XBase XBase.3pm.gz XBase::Index.3pm.gz XBaseFontNameListOfFon

one undo too many and bye bye line

Type $ abcde then five DELs or ^H's to erase it, then five undos (^/ or whatever) to restore it, and then one more undo for good luck, and wham, bye bye line. No getting back anything whatever you type. You'll just have to type abcde all over again. ___

disown, unlike fg, can't realize current job

How inconvenient, disown, unlike fg, can't realize the current job or whatever: $ sleep 111& [1] 7125 $ sleep 222& [2] 7126 $ disown $ disown bash: disown: current: no such job $ jobs [1]- Running sleep 111 & $ disown %1 $ ___ Bug-bash

disowned not the job expected

Another disown adventure. # suspend [1]+ Stopped su $ emacs -f gnus fileA & [2] 4865 $ disown bash: warning: deleting stopped job 1 with process group 3457 $ jobs [2]- Running emacs -f gnus fileA & $ help disown disown: disown [-h] [-ar] [jobspec ...] By default, removes each

bash -x $'' hexadecimal

I notice bash -x prints some messages in octal, $'\345\226\256\350\252\236\345\214\226' I bet there's no way to get it to print them in hexadecimal. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

help kill should also mention man kill

Incompatibility: one verbose, one not. $ kill -1 1812 1818 1825 1826 1857 bash: kill: (1812) - No such process bash: kill: (1818) - No such process... $ /bin/kill -1 1812 1818 1825 1826 1857 $ Or at least also mention /bin/kill here $ help kill ...Kill is a shell builtin for two reasons... $

Bug#442077: su + ssh + false kills $PPID?

Package: openssh-client Version: 1:4.6p1-5 Severity: normal File: /usr/bin/ssh Why does this script not finish, only when using su, and only when using ssh? # cat script su my_username_here <<\EOEOE set -x echo $- #no -e here, see remote=my.remote.host.here false ssh $remote false #Why does this

cannot execute binary file

Perhaps it's about time to fix this? $ head -1 one_time_job wget --spider -Y off -S http://www.ham.com.tw/ctarl/940524-940604衛生署公文.jpg $ sh -n one_time_job one_time_job: one_time_job: cannot execute binary file $ bash --version GNU bash, version 3.00.16(1)-release (i386-pc-linux-gnu) Workaround: a

ESC t not ready for Chinese

If I put the cursor between the last two items, $ search 鼓山 福州 and type ESC t, I get $ s 福州 鼓山earch Whereas in real emacs, I correctly get $ search 福州 鼓山 P.S., Here are the items again in case this mail gets mangled $ echo search 鼓山 福州|qp-encode search =B9=AA=A4s =BA=D6=A6{ $ set BASH_VERSI

wait: mention PID must be a child of this shell

$ help wait doesn't mention that PID must be a child of this shell. Nor does it advise how to wait if PID is not a child of this shell. User wanted to do noffle --f & (wait $!; noffle -f) & for better or worse. User forced to use (noffle -f; noffle -f)& ___

add PS1 to messages?

Not sure if there is any fix for this. When sending messages like "Terminated" to the terminal, maybe also send a PS1, if indeed we are in prompt waiting foreground mode or whatever. Don't just leave the users cursor parked at column 1: # PS1="# " # sleep 33& [1] 3355 # killall sleep # [1]+ Termin

${p+\"$p\"}

So how am I to get "A" with bash? $ cat z p=A cat <

$ < some_file some_command Tab expansion

Tab expansion works for both parts of $ some_command < some_file but not the some_command of $ < some_file some_command BASH_VERSION='4.4.0(1)-rc1'

TAB expand as much as you can before asking "Display all possibilities"

Here we observe that bash _could_ first expand as much as it could, before asking us y or n, $ find .backups/\!h Display all 277 possibilities? (y or n) n $ find .backups/\!home\!jidanni\! Instead it waits until we say "n". (All I typed was the first line, and the "n"). BASH_VERSION='4.4.0(1)-rc

why would anybody want ESC . to remember "&" ?

$ bla1 bla2 bla3 & $ $ & Why not $ bla3 What value is remembering "&". Emacs' doesn't, and doesn't bother even mentioning it: C-c . runs the command comint-insert-previous-argument, which is an interactive compiled Lisp function in `comint.el'. It is bound to C-c .. (comint-insert-previous-a

run_readline_command to avoid the bother of binding something

On the bash page at the end of Readline Command Names The following is a list of the names of the commands and the default key sequences to which they are bound. Command names without an accom- panying key sequence are unbound by default. In the following descrip-

Re: run_readline_command to avoid the bother of binding something

Furthermore, one could finally do $ run_readline_command dump-variables | grep bell prefer-visible-bell is set to `on' bell-style is set to `audible' which is rather impossible, even if one does bind unbound commands. Currently one must probably use script(1), bind the key, and then exit and grep

Re: Add option to just print history, with no added timestamps or line numbers

>>>>> "CR" == Chet Ramey writes: CR> On 3/24/24 11:39 PM, Lawrence Velázquez wrote: >> On Sun, Mar 24, 2024, at 11:01 PM, Dan Jacobson wrote: >>> P.S., "\t%s" seems to have an extra space squeezed between them with >>> bash: "\t

sh vs. bash -xc 'a=b c=$a'

It seems these should both make one line "+ a=b c=b" output, for s in sh bash do $s -xc 'a=b c=$a' done I mean they give the same results, but bash splits it into two lines, so the user reading the bash -x output cannot tell if one (correct) or two (incorrect) lines were used. They can tell with

Poor messages when the '#!' file isn't found

$ echo \#!/usr/bin/python > k $ chmod +x k $ ./k bash: ./k: cannot execute: required file not found Bash should really mention what file it is talking about. $ echo 'x:k; ./$<' > Makefile $ make ./k make: ./k: No such file or directory make: *** [Makefile:1: x] Error 127 $ ls ./k ./k Make is wor

history -f filename

$ history is nice, but what if you want to have it read from a different file? $ help history says If FILENAME is given, it is used as the history file. Otherwise, if HISTFILE has a value, that is used, else ~/.bash_history. Alas, it also says history: history [-c] [-d offset] [n] or

Re: history -f filename

$ history |wc - $HISTFILE|sed \$d 7622 75741 532254 - 14973 29625 320996 /home/jidanni/.bash_history_jidanni Works as expected. $ (a=~/.bash_history_jidanni-emacs; HISTFILE=$a history |wc - $a|sed \$d) 7625 75780 532531 - ### I expected to see about 1399/2 here. 13993535

Document variable names need to be all ASCII

$ e哈=1 bash: e哈=1: command not found OK, but on man bash is it ever mentioned that a variable name must be all ASCII? ENVIRONMENT When a program is invoked it is given an array of strings called the environment. This is a list of name-value pairs, of the form nam

Document that set -v inside case statements is special

Please document on the man page somewhere that set -v, +v inside case statements is special: $ cat A case x in x) set -v : B case y in y) set -v : Z ;; esac

"command" help page

$ help command | grep -i -- -v -vprint a description of COMMAND similar to the `type' builtin -Vprint a more verbose description of each COMMAND $ command -v cat /bin/cat $ type cat cat is /bin/cat $ command -V cat cat is /bin/cat So it turns out -V is like type, not -v! Also

help for needs to mention for ((...))

$ help for only mentions for name [ [ in [ word ... ] ] ; ] do list ; done and needs to be updated to mention for (( expr1 ; expr2 ; expr3 )) ; do list ; done $ echo $BASH_VERSION 5.1.8(1)-release

Re: help for needs to mention for ((...))

OK, then "help for" should at least mention that trick to get the rest of the story.

Re: help for needs to mention for ((...))

$ help f|wc -l 72 $ help fo |wc -l 24 $ help for |wc -l 10 $ help for\ |wc -l 14 $ help for\ \( |wc -l 14 $ help for\ \(\(|wc -l 14 So help help's 'If PATTERN is specified, gives detailed help on all commands matching PATTERN." is not telling the whole story about matching.

Re: help for needs to mention for ((...))

OK, so it first looks for exact hits, then does a grep style match. And we see that $ help f|grep :. false: false fc: fc [-e ename] [-lnr] [first] [last] or fc -s [pat=rep] [command] fg: fg [job_spec] for: for NAME [in WORDS ... ] ; do COMMANDS; done for ((: for (( exp1; exp2; exp3 )); do COMMANDS

Document -x and -vx give the same results

Man page says: -vPrint shell input lines as they are read. -xPrint commands and their arguments as they are executed. Perhaps mention that -x and -vx give the same results, often or always. GNU bash, version 5.1.8

Re: Document -x and -vx give the same results

I was testing -xeu vs. -vxeu on set -xeu set /var/lib/exim4/config.autogenerated cp $@ /tmp update-exim4.conf --verbose diff /tmp $@||: set update-exim4.conf.conf echo . $PWD/$@-jidanni > /tmp/$@ diff $@ /tmp and no matter STDOUT or STDERR they gave the same results, there in emacs' *compilation*

>| expansion assumes | rules instead of > rules

# su - nobody #create pristine bug testing environment $ : >| /tmp/ shows much less choices than $ : > /tmp/ It is probably wrongly assuming we want to see the $ : | /tmp/ choices! BASH_VERSION='4.3.0(1)-release' $ apt-cache policy bash-completion bash-completion: Installed: (none)

'help' command adds unnecessary trailing blanks indenting empty lines

No big deal but, $ help :|cat -e :: :$ Null command.$ $ No effect; the command does nothing.$ $ Exit Status:$ Always succeeds.$

Display all 132 possibilities? (y, n, or t) t=time!

Super duper idea: you know when we hit TAB and it says Display all 132 possibilities? (y or n) Well, that happens to be the 'ls -a' format it is asking about. Well, who says that is the most natural format or the format we want at that time? What if occasionally we want the 'ls -t' or 'ls -ta' f

Re: expand x*y concludes with one

OK I submitted http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865875 against bash-completion.

ulimit -c unlimited

$ ulimit -c 99 $ ulimit -c 99 $ ulimit -c unlimited bash: ulimit: core file size: cannot modify limit: Operation not permitted Maybe say: try again with numbers, not letters.

Re: ulimit -c unlimited

$ ulimit -c 0 $ ulimit -c 99 $ ulimit -c 99 $ ulimit -c 99 bash: ulimit: 99: limit out of range $ ulimit -c 999 bash: ulimit: 999: limit out of range

Re: ulimit -c unlimited

CR> The third command attempts to increase the limit beyond the current hard CR> limit. If you're not root, this is not permitted. I find it odd that a normal user can raise it only once...

variables not TAB expanded except in first position

$ $BRO #makes $BROWSER. Good! $ xargs $BRO #just beeps. Bad. Yes I have bash-completions installed but am not sure what is to blame.

help complete: mention remove all AND restore all

$ help complete -rremove a completion specification for each NAME, or, if no NAMEs are supplied, all completion specifications Add To later restore them do ... as one often wants to remove them all, try something, and then put them all back. I am no

Re: variables not TAB expanded except in first position

OK submitted https://github.com/scop/bash-completion/issues/173

Re: help complete: mention remove all AND restore all

PG> There is no magic way to restore them Actually it also says -pprint existing completion specifications in a reusable format So maybe it should say do I=$(completion -p); completion -r; : your tests; $I but I didn't test it.

  1   2   >