On Sat, Feb 03, 2018 at 02:57:33PM +0100, Egmont Koblinger wrote:
> So the use case is: Someone wants to _add_ something to
> PROMPT_COMMAND. How to do that?
PROMPT_COMMAND+=$'\n''my new stuff'
Or, test whether PROMPT_COMMAND is currently empty, and only
append the newline (or semicolon) if it's
I witnessed the following in the word-splitting results passed to
custom completion functions. The word splitting performed goes haywire
when it sees the =' (equal, quote) or =" (equal double-quote)
character sequences. From this point on, practically no word-splitting
is performed. As these sequen
On 2/2/18 3:19 PM, Chet Ramey wrote:
> On 2/2/18 9:50 AM, Sten Westerback wrote:
>> Hi
>>
>> After trying to figure out what causes a weird bug, which i can see with
>> lots of shells and connection types (local terminal on linux, ssh +
>> numerous shells on AIX and putty (linux & windows)+numero
On 2/5/18 9:05 AM, Greg Wooledge wrote:
> On Sat, Feb 03, 2018 at 02:57:33PM +0100, Egmont Koblinger wrote:
>> So the use case is: Someone wants to _add_ something to
>> PROMPT_COMMAND. How to do that?
>
> PROMPT_COMMAND+=$'\n''my new stuff'
>
> Or, test whether PROMPT_COMMAND is currently empty,
On 2/5/18 2:25 AM, Nick Patavalis wrote:
> I witnessed the following in the word-splitting results passed to
> custom completion functions. The word splitting performed goes haywire
> when it sees the =' (equal, quote) or =" (equal double-quote)
> character sequences. From this point on, practicall
