On 6/11/19 10:07 AM, Andreas Schwab wrote:
> On Jun 11 2019, Chet Ramey 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 tu
On Jun 11 2019, Chet Ramey 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 histo
On 6/11/19 9:38 AM, _...@crans.org wrote:
> Chet Ramey wrote (2019-06-10 15:22):
>> On 6/8/19 3:41 PM, _...@crans.org wrote:
>>>
>>> What makes me think it is an actual bug is that when the
>>> "history" option was already enabled, "set -o history" should
>>> have no effect; yet lines b
Chet Ramey wrote (2019-06-10 15:22):
> On 6/8/19 3:41 PM, _...@crans.org wrote:
>>
>> What makes me think it is an actual bug is that when the
>> "history" option was already enabled, "set -o history" should
>> have no effect; yet lines before are not recorded, and lines
>> afte
