[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: `eval` pollutes the history when it runs "set -o history"

From: Chet Ramey
Subject: Re: `eval` pollutes the history when it runs "set -o history"
Date: Tue, 11 Jun 2019 10:10:45 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0

On 6/11/19 10:07 AM, Andreas Schwab wrote:
> On Jun 11 2019, Chet Ramey <address@hidden> wrote:
>> Maybe. But the user-visible option that says whether or not to save
>> commands in the history is decoupled from the internal set of flags that
>> control it. The option should remain visibly on unless the user turns it
>> off, even if saving commands in the history is temporarily suppressed. The
>> thing is that enabling history with `set -o history' turns all of these
>> things on.
> But should the effect of `set -o history' be deferred until the end of
> the temporary suppression?

It's ambiguous. `set -o history' has clearly-defined effects and can be
used while the shell is not interactive.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://tiswww.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]