Hi Chet, I was doing the experiment on my macOS, and the bash version is 3.2.57. After that, I tried again with my Ubuntu, which has bash 4.4.19, can't reproduce that. Maybe it's because of the bash version?
Best, John Lin Chet Ramey <[email protected]> 於 2019年1月31日 週四 下午10:54寫道： > On 1/30/19 10:34 PM, 林自均 wrote: > > Hi Chet, > > > > Sorry. I realized that I didn't understand what "revert-all-at-newline" > is > > doing. I checked the manual, it says: > > > > revert-all-at-newline (Off) > > If set to On, readline will undo all changes to history > lines > > before returning when accept-line is executed. By default, > > history lines may be modified and retain individual undo > lists > > across calls to readline. > > > > According to the description, I set it to "On" and tried the following > > steps in bash: > > > > 1. Type "echo 5566" and hit "enter" > > 2. Hit "up" to navigate to the history "echo 5566" > > 3. Change it to "echo 7788" and DON'T hit "enter" > > 4. Hit "down" to navigate to an empty place > > 5. Type "ls" and hit "enter" > > 6. Type "history | tail -n 3" and hit "enter" > > > > After that, I expected that I can see the history "echo 5566" in the last > > command since it should be reverted. However, I still see "echo 7788" in > > the results: > > > > $ history | tail -n 3 > > 501* echo 7788 > > 502 ls > > 503 history | tail -n 3 > > > > What did I miss? Thank you. > > It's hard to say. When I try this, I get 'echo 5566' as expected. I suspect > something about how you set revert-all-at-newline, since the `echo 7788' > line has a `*' preceding it, indicating that it's still got an active undo > list. > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRU [email protected] http://tiswww.cwru.edu/~chet/ >
_______________________________________________ Bug-readline mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-readline
