I just installed hstr for the first time on both Ubuntu 22.04 and 24.04 machines, and I way just about to say "awesome", when I realized that if I view the history in chronological order (view:history (C-/)), and then I scroll with Up or Down arrow (or Ctrl-J/K, or Ctrl-N/P, once I scroll past the final history line shown in terminal - it simply wraps back to the first line shown in the terminal, it does not scroll to other entries! And that means I cannot browse the entire history ?!
Actually, I just tested this with filter as well - I just typed "a", and I'm certain I've had more commands in history with "a" than the 31 rows that my terminal currently shows - and again, navigating past the ends of the shown list, simply wraps the selection highlight at the other end of the list, without any scrolling at all! So how am I supposed to say select the 40th oldest command, if my terminal shows only 31 commands currently?
Is this how this program is supposed to work? In any case, it should have been stated in the README how it behaves in terms of entire history ....
I just installed
hstrfor the first time on both Ubuntu 22.04 and 24.04 machines, and I way just about to say "awesome", when I realized that if I view the history in chronological order (view:history (C-/)), and then I scroll with Up or Down arrow (or Ctrl-J/K, or Ctrl-N/P, once I scroll past the final history line shown in terminal - it simply wraps back to the first line shown in the terminal, it does not scroll to other entries! And that means I cannot browse the entire history ?!Actually, I just tested this with filter as well - I just typed "a", and I'm certain I've had more commands in history with "a" than the 31 rows that my terminal currently shows - and again, navigating past the ends of the shown list, simply wraps the selection highlight at the other end of the list, without any scrolling at all! So how am I supposed to say select the 40th oldest command, if my terminal shows only 31 commands currently?
Is this how this program is supposed to work? In any case, it should have been stated in the README how it behaves in terms of entire history ....