Re: bash manual on interactive shell

On 2021-12-13 at 11:23 +, Kerin Millar wrote: > You mentioned being confused by how the and's and or's combine. The > wording of the bash man page seems marginally less ambiguous in that > regard, partly owing to its sparse use of the comma. > > "An interactive shell is one started without non

Re: Line is corrupted when pasting long string in vi mode with exit_attribute_mode prompt

Ahh my bad, didn't read that section of the manual carefully enough. Thanks Andreas! Jack On December 18, 2021 8:03:17 AM PST, Andreas Schwab wrote: >On Dez 17 2021, Jack Pearson wrote: > >> PS1='$(tput sgr0)' # emit exit_attribute_mode capability string > >Non-printable characters in the pr

Re: in-line calls to functions cause "exit" in the function to act like "return"

x=$( exit 2 ) ; printf $?\\n On Sat, Dec 18, 2021, 17:03 Kerin Millar wrote: > On Sat, 18 Dec 2021 13:07:03 + > yesxorno via Bug reports for the GNU Bourne Again SHell > wrote: > > > Description: > > > > When 'exit' is executed in a function called to "in-line" its output to > stdout, the '

Re: Line is corrupted when pasting long string in vi mode with exit_attribute_mode prompt

On Dez 17 2021, Jack Pearson wrote: > PS1='$(tput sgr0)' # emit exit_attribute_mode capability string Non-printable characters in the prompt must be bracketed by \[ \]. PS1='\[$(tput sgr0)\]' -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E

Re: in-line calls to functions cause "exit" in the function to act like "return"

On Sat, 18 Dec 2021 13:07:03 + yesxorno via Bug reports for the GNU Bourne Again SHell wrote: > Description: > > When 'exit' is executed in a function called to "in-line" its output to > stdout, the 'exit' acts like return, leaving the function scope, but not > terminating the bash proces

Re: in-line calls to functions cause "exit" in the function to act like "return"

you execute it in a separate bash subshell via $( .. ) this code parsing layer u bring to exit On Sat, Dec 18, 2021, 16:50 yesxorno via Bug reports for the GNU Bourne Again SHell wrote: > (Composed using 'bashbug')

in-line calls to functions cause "exit" in the function to act like "return"

(Composed using 'bashbug')From: yesxo...@protonmail.ch To: bug-bash@gnu.org Subject: in-line calls to functions cause "exit" in the function to act like "return" Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2

Line is corrupted when pasting long string in vi mode with exit_attribute_mode prompt

To reproduce: - Launch a bash shell in a terminal emulator (I've tested konsole and gnome-terminal on KDE 5.23.4 with X11, if that matters). - Copy "Lorem ipsum dolor sit amet, consectetur adipiscing elit" (without the quotes) to your clipboard. - Run these commands in the terminal: ```

Feature Request: Allow each completion to have their own wordbreaks

Right now I'm trying to perfect this completion script for rake (https://git.io/JDaSA), but the problem is it has to rely on modifying the COMP_WORDBREAKS variable so it doesn't contain '=' and ':'. This conflicts with git's completion script at least which prefers `:` to be assigned, and I'm not