-
Notifications
You must be signed in to change notification settings - Fork 89
Optional configure flag to flush history after each command? #10
Open
Description
Hello,
I understand the current history behavior is conservative for compatibility and historical performance reasons (which made sense in the 1990s with slower disks and different workloads).
However, would it be acceptable to add an optional ./configure flag (e.g. --enable-immediate-history-flush) that makes interactive shells append to $HISTFILE after each executed command?
Today this requires PROMPT_COMMAND="history -a". A compile-time opt-in would preserve defaults while allowing crash-resilient history persistence on modern systems.
Would this be considered?
Thanks.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Give feedbackNo fields configured for issues without a type.