ash.c history loading and ENABLE_FEATURE_EDITING_SAVEHISTORY
Kang-Che Sung
explorer09 at gmail.com
Sun Dec 24 01:26:37 UTC 2017
2017年12月24日 09:17,"Ceriel Jacobs" <linux-ide at crashplan.pro>寫道:
There is no need to remember what was just typed.
There is a need to use commands that were typed a long time (years) ago.
Disasters often happen a long time after the backup (script/system) was
made.
The point is that you don't have to:
1. remember the commands
2. type the commands
3. correct typing mistakes
I know that I can save .ash_history
but it seems I can't load it without feature ENABLE_FEATURE_EDITING_SAVEHISTORY
set.
And convincing Arch Linux developers to turn on the
ENABLE_FEATURE_EDITING_SAVEHISTORY feature will be difficult. Because in
their initramfs environment they don't want to have a SAVEHISTORY to file
functionality.
I'm not convinced by this. Since your use case is a very rare one
(read-only "history" somehow defeats the purpose of the history - and it
overlaps what pre-written shell function is for). While I'm not one who can
make decisions on this, I'd suggest you just keep your local patch to do
this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20171224/d06bf8bc/attachment.html>
More information about the busybox
mailing list