Docs: "shell-transpose-words" in "8.4.4 Killing And Yanking"

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.

Some Readline variables are not available in "bind -v"

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.

history-size reported as "0" even is value is "-1"

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

Docs: Mention that hash resets after changing PATH

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.

Re: maybe a bug in bash?

commands). To get the input via an password manager (like Bitwarden CLI) is at this point the better way I think (code injection stay be a problem, if I use the passwords in an awkward way in my script). Mit freundlichen Grüßen Sebastian Luhnburg IT

Re: maybe a bug in bash?

#x27;$abc&xyz'\''' password in subshell in here document:  ''\''&xyz'\''' p.s.: in the final script, it is only one SSH: ssh user@machine << EOF /bin/bash -c "do something with the password" EOF Mit fr

Docs: Duplicated explanation of "quote removal" on manual

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

maybe a bug in bash?

ord in here document: " ${password@Q} /bin/bash -c "echo 'password in subshell in here document: ' ${password@Q}" EOF The output: initial password:  $abc&xyz initial password with escaped characters:  \$abc\&xyz password in here document:  \$abc\&xyz password in

maybe a bug in bash?

nt:  \$abc\&xyz password in subshell in here document:  $abc\&xyz Thank you very much! Mit freundlichen Grüßen Sebastian Luhnburg IT -- swp software systems GmbH & Co. KG Königsbrücker Straße 124 01099 Dresden Tel: 0351-492

The bash built-ins 'true' and 'false' are undocumented in info and man page.

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

Re: bash built-ins `true' and `false' undocumented

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

Feature request: alternating keys & values syntax for hashes

#x27;s just about allowing hashes to accept series of values, being the k&v-s alternating. Is there a chance for such an extension? PS. The *-symbol might be the right choice, as it inherits the glob meaning "match all", and this translates to the hash variable "give back all,

Re: bash tab variable expansion question?

On 05.03.2012 21:28, Chet Ramey wrote: On 3/5/12 2:07 PM, Sebastian Siebert wrote: Thanks for the great patch. I have applied your patch in our bash 4.2 + Patchlevel 20. It is solved an issue with variable expansion. But on the other side bash completion is broken. :-( Bash completion with

Re: bash tab variable expansion question?

. It would be nice if you have a look to the patch and let me know if this is ok. Thank you. -- Kind regards, Sebastian - openSUSE Member (Freespacer) Website/Blog: <http://www.sebastian-siebert.de> Important notes on openSUSE Mailing List: <http://en.opensuse.org/openSUSE:Mailing_l

Text cursor hangs/freezes, 2 x backspace unfreezes

Configuration Information [Automatically generated, do not change]: Machine: i386 OS: solaris2.9 Compiler: /opt/studio/SOS12/SUNWspro/bin/cc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='solaris2.9' -DCONF_MACHTYPE='i386-pc-solaris2.9' -DCONF_VENDOR='pc' -DLOCALEDIR=

Cursor stuck/frozen, only backspace unfreezes

Configuration Information [Automatically generated, do not change]: Machine: i386 OS: solaris2.9 Compiler: /opt/studio/SOS12/SUNWspro/bin/cc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='solaris2.9' -DCONF_MACHTYPE='i386-pc-solaris2.9' -DCONF_VENDOR='pc' -DLOCALEDIR=

Re: Is this bash-doable job?

em than any other programming language. -- Best Regards, | Hi! I'm a .signature virus. Copy me into Sebastian | your ~/.signature to help me spread!

Re: globstar syntax

n **; do if [[ ${i} =~ \.c$ ]]; then ; fi; done Huh? So what's the difference between the following two lines echo ** echo `find` Quoting? -- Best Regards, | Hi! I'm a .signature virus. Copy me into Sebastian | your ~/.signature to help me spread!

Re: "C-z bg" without the lurch

assume this is X11): pkill -CONT emacs This does work for programs that don't insist on reading from the TTY they're on, which is probably true for the X11 version of Emacs (I prefer more spartanic editors myself *g*). -- Best Regards, | Hi! I'm a .signature virus. Copy me into Sebastian | your ~/.signature to help me spread!

Re: bash 3.2, escape sequences

> Sebastian Kapfer wrote: > >> I'm not quite getting the changes in bash's handling of escape >> sequences. > > I can't reproduce your results: [...] > I suspect that you have echo defined as a function or alias, or > something in $PROMPT_COMMAND or $

bash 3.2, escape sequences

;t get it. On a related note, the documented escape sequences handled by "echo" differ between help echo and man echo (-e vs. -E). -- Best Regards, | Hi! I'm a .signature virus. Copy me into Sebastian | your ~/.signature to help me spread! signature.asc Description: Dies is

readline post-hook?

Is there a way to run a function after the user has finished a line with RETURN to add characters to the readline buffer? Of course one could malloc new memory and copy the stuff got by the call of readline but may be there is a more smart way of doing it? Thanks for your help! Sebastian

DEBUG trap and job names

ould be very grateful if someone in the know would spend a few thoughts on this one :-) For the record: I'm running bash version "3.1.17(1)-release", at least that's what Ubuntu calls it, should be up-to-date. -- Best Regards, | Hi! I'm a .signature virus. Copy me into

Re: Can't get the set-user-id bit to work

[EMAIL PROTECTED] (Paul Jarc) wrote: > Sebastian Tennant <[EMAIL PROTECTED]> wrote: >> OK, but mandb _is_ a member of the root group, so shouldn't it be able >> to write files in /tmp with the permissions as they stand? > > No, you'd have to make it setuid t

Re: Can't get the set-user-id bit to work

[EMAIL PROTECTED] (Paul Jarc) wrote: > Sebastian Tennant <[EMAIL PROTECTED]> wrote: >> I have a 3-line script; foo: > > The setuid bit works only for binaries, not scripts. This is a > limitation of the kernel, necessary for security. Ah. I read the chmod manpage an

Can't get the set-user-id bit to work

Hi all, If it's a festive time of year where you are then I hope you're enjoying it. First of all, apologies if this is not the correct list for this query. Perhaps you could suggest where else I should go. I have a 3-line script; foo: #!/bin/bash id -u # EUID id -u -r # `re