Re: [BUG] assignments preceding 'read' persist past command in POSIX mode

On 5/24/18 5:23 PM, Martijn Dekker wrote: > In bash-20180511 and bash-20180518 snapshots and in bash 5.0.0-alpha, in > POSIX mode, assignments preceding 'read' incorrectly persist past the > command. 'read' is a regular builtin so they should not persist. > > $ ./bash -o posix -c 'v=ok; v=bug read

Re: [PATCH] Add nofirstword completion option

On Wed, 2018-05-23 at 09:53 -0400, Chet Ramey wrote: > On 5/23/18 9:34 AM, Luca Boccassi wrote: > > On Wed, 2018-05-23 at 09:15 -0400, Chet Ramey wrote: > > > On 5/23/18 5:44 AM, Luca Boccassi wrote: > > > > > > > So by that, do you mean that it's possible to stop > > > > autocompleting > > > > to

Re: [PATCH] Add nofirstword completion option

On 5/25/18 1:42 PM, Luca Boccassi wrote: >> There is already logic that determines whether the shell is trying to >> complete a command word (in_command_position). The existing code does >> not attempt programmable completion if in_command_position == 1. The >> additional functionality would: >> >

Readline documentation error

There is an unnecessary closing parenthesis under /bracketed-paste-begin ()/ from section 8.4.3 of /Bash Reference Manual/ diff --git a/lib/readline/doc/rluser.texi b/lib/readline/doc/rluser.texi index 1c9acdc..d42f6f6 100644 --- a/lib/readline/doc/rluser.texi +++ b/lib/readline/doc/rluser.texi @