When formatting for typesetters, a blank input line produces 1 vee (one line height, basically) of vertical space, but the default inter-paragraph distance in man(7) is 0.4v. Fixes numerous style war
Since the history library is explicitly line-oriented, and independent of the shell, there hasn't been a clean way to inform it about any quoting state the current line should inherit. I added an exp
Configuration Information [Automatically generated, do not change]: Machine: i386 OS: Linux Compiler: cc Compilation CFLAGS: -DHAVE_VFPRINTF -DHAVE_UNISTD_H -DHAVE_STDLIB_H -DHAVE_LIMITS_H -DHAVE_GET
Yes... Also, the same magic seems to apply to $!, even if it isn't at the end of a word. The manual page should probably mention the criteria for suppressing historyexpansion there, whatever they ar
Upgrade. Bash-2.04 handles this correctly. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet) Chet Ramey, CWRU chet@po.CWRU.Edu http://cnswww.cns.cwru.e
According to the bash man page, it appears that only backslash and single quotes can escape the historyexpansion character ('!' by default). However, bash refuses to escape the historyexpansion cha
While the delimiters for picking history expansions out of a line of input include all (most of?) the things that cause words to be delimited at the shell grammar level, it differs sufficiently that
This is the Bash FAQ, version 3.36, for Bash version 3.2. This document contains a set of frequently-asked questions concerning Bash, the GNU Bourne-Again Shell. Bash is a freely-available command in
The second release candidate of bash-4.4 is now available with the URL ftp://ftp.cwru.edu/pub/bash/bash-4.4-rc2.tar.gz and via git from http://git.savannah.gnu.org/cgit/bash.git/?h=bash-4.4-testing T
Historyexpansion is explicitly line-oriented. It doesn't know about shell state, especially shell quoting state, that spans lines. It does know about vaguely shell-like quoting that's common across
The second beta release of bash-4.4 is now available with the URL ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta2.tar.gz and via git from http://git.savannah.gnu.org/cgit/bash.git/?h=bash-4.4-testing This
Not completely. The change is that a double quote following the historyexpansion character inhibits historyexpansion in a double-quoted string. Nonsense like !"" will still attempt history expansio
This is the Bash FAQ, version 3.35, for Bash version 3.2. This document contains a set of frequently-asked questions concerning Bash, the GNU Bourne-Again Shell. Bash is a freely-available command in
If you say so. But it is nevertheless a highly unexpected and annoying behavior. I didn't look at the code, I just know it works in zsh. At least, the man page Should reflect this behavior, don't you
Historyexpansion is explicitly line-oriented, and always has been. There's not a clean way to make it aware of the shell's current quoting state (mostly since it's a library independent of the shell