Hello,
The "shell-transpose-words" command is documented in the section "8.4.4
Killing And Yanking", but I think it should be in "8.4.3 Commands For
Changing
Text".
That way, just like the other "shell-*" commands, it would be documented
next
to its counterpart "transpose-words".
Thanks.
Hello,
I noticed that the following variables are not visible in "bind -v":
- active-region-start-color
- active-region-end-color
- isearch-terminators
Thanks for your time.
Hello,
history-size is documented as follows:
> If set to a value less than zero, the number of history entries is not
limited.
But after setting it to "-1", for example with this line in .inputrc:
> set history-size -1
It is still reported as "0" in "bind -v":
> set history-size 0
Nevertheless
Hello,
I noticed that there's no mention in the manual that, when the PATH changes,
"hash -r" is run. I think that would be a nice addition, possibly on "4.1
Bourne Shell Builtins / hash"
Thanks.
Hello,
The manual seems to repeat the same information two paragraphs apart:
On Section 3.5 Shell Expansions, a paragraph reads:
> After these expansions are performed, quote characters present in the
original word are removed unless they have been quoted themselves (quote
removal).
Then, after
I guess there is not too much to say about the bash built-ins 'true' and
'false'. Nonetheless, I suggest that the info pages should list these
built-ins individually like other built-ins. Currently, the only hint on
their
existence in the info or man page is in the node (or man page section)
calle
I am writing to follow up on this old bug report about the lack of
documentation for the bash built-ins 'true' and 'false'. I agree with the
previous arguments on why these built-ins should be documented in 'info
bash',
and I would like to add two more reasons:
- The commands 'true' and 'false' th
