The use case is not so "very rare" and is used within the
Relax-and-Recover (rear) project. Albeit bash is used there.
In case ENABLE_FEATURE_EDITING_HISTORY would be split in:
ENABLE_FEATURE_EDITING_LOADHISTORY
ENABLE_FEATURE_EDITING_SAVEHISTORY
then there is more purpose in having
ENABLE_FEATURE_EDITING_SAVEHISTORY depend upon
ENABLE_FEATURE_EDITING_LOADHISTORY
then LOAD depends on SAVE.
Thank you for the re-written shell function hint.
<newbie>
Where is the user interface to quickly issue a pre-written shell
function? And how to see the available functions?
</newbie>
Op 24-12-17 om 02:26 schreef Kang-Che Sung:
2017年12月24日 09:17，"Ceriel Jacobs" <[email protected]
<mailto:[email protected]>>寫道：
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.
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
