Re: ash.c history loading and ENABLE_FEATURE_EDITING_SAVEHISTORY

On 12/24/2017 4:43 AM, Ceriel Jacobs wrote: Where is the user interface to quickly issue a pre-written shell function? And how to see the available functions? ls /usr/local/bin ...? Just add your "pre-written shell commands" in script files, give them a useful name, and put them in the

Re: ash.c history loading and ENABLE_FEATURE_EDITING_SAVEHISTORY

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

Re: ash.c history loading and ENABLE_FEATURE_EDITING_SAVEHISTORY

2017年12月24日 09:17，"Ceriel Jacobs" 寫道： 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

Re: ash.c history loading and ENABLE_FEATURE_EDITING_SAVEHISTORY

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.

Re: ash.c history loading and ENABLE_FEATURE_EDITING_SAVEHISTORY

2017-12-24 07:55，"Ceriel Jacobs" 寫道： It seems that BusyBox v1.27.2 doesn't load history from a history file when ENABLE_FEATURE_EDITING_SAVEHISTORY is not set. I think that the corresponding source code logic is here:

ash.c history loading and ENABLE_FEATURE_EDITING_SAVEHISTORY

It seems that BusyBox v1.27.2 doesn't load history from a history file when ENABLE_FEATURE_EDITING_SAVEHISTORY is not set. I think that the corresponding source code logic is here: Such logic doesn't match the feature name, which is