-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/22/15 6:17 PM, Karl-Philipp Richter wrote:
> Hi,
> Currently, syntax error messages like ``bash: syntax error near
> unexpected token `;'``, e.g. after issuing `echo a &; echo b &; echo c
> &;` aren't as helpful as they could be. It'd be nice to
On 12/26/15 6:15 PM, james harvey wrote:
> When I turn on timestamps for history, .bash_history records without a
> timestamp (and possibly in-memory records without a timestamp - not
> sure, haven't tested) inherit the modified timestamp of .bash_history
> next time it is read.
No. History entri
On 12/26/15 6:15 PM, james harvey wrote:
> It appears bash sends an executed quoted multiline command to the
> in-memory history list as one command.
Yes. The history file, through readline-6.3, is completely line-based.
The history library assumes that each line in the history file is a single
On 12/27/15 4:58 PM, Adrien Nader wrote:
> Hi,
>
> I have recently been getting "save_bash_input: buffer already exists for
> new fd XXX" very often when running a fairly simple script (really
> nothing complicated) with bash 4.3.42.
>
> I have no idea of what could cause this, especially since v
Hi,
I have recently been getting "save_bash_input: buffer already exists for
new fd XXX" very often when running a fairly simple script (really
nothing complicated) with bash 4.3.42.
I have no idea of what could cause this, especially since very similar
scripts work fine.
Which steps should I tak
