[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bash History Behavior Suggestion
From: |
Chet Ramey |
Subject: |
Re: Bash History Behavior Suggestion |
Date: |
Wed, 28 Aug 2024 10:06:18 -0400 |
User-agent: |
Mozilla Thunderbird |
On 8/20/24 1:42 AM, support@eggplantsd.com wrote:
I know it can. The suggestion is that the default behavior needs some work:
The default behavior provides mostly mechanism, not policy. There are ways
to do what you want, but those are not suitable for (or desired by)
everyone. So you can change your environment to suit your needs using the
existing mechanisms.
Extending the timestamp field in the history entry struct to contain more
data after the timestamp has come up before, but I've never pursued it as
a priority.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
- Re: Bash History Behavior Suggestion, (continued)
- Re: Bash History Behavior Suggestion, Martin D Kealey, 2024/08/20
- Re: Bash History Behavior Suggestion, Martin D Kealey, 2024/08/20
- Message not available
- Re: Bash History Behavior Suggestion, support, 2024/08/20
- Re: Bash History Behavior Suggestion, Lawrence Velázquez, 2024/08/20
- Re: Bash History Behavior Suggestion, support, 2024/08/20
- Re: Bash History Behavior Suggestion, Martin D Kealey, 2024/08/20
- Re: Bash History Behavior Suggestion, support, 2024/08/20
- Re: Bash History Behavior Suggestion, Martin D Kealey, 2024/08/20
- Re: Bash History Behavior Suggestion, support, 2024/08/20
- Re: Bash History Behavior Suggestion, Chet Ramey, 2024/08/28
- Re: Bash History Behavior Suggestion,
Chet Ramey <=