Skip to content
  1. Apr 13, 2024
  2. Feb 21, 2024
  3. Jan 16, 2024
  4. Jan 15, 2024
  5. Jan 05, 2024
  6. Dec 29, 2023
  7. Dec 05, 2023
  8. Oct 16, 2023
  9. Oct 06, 2023
  10. Sep 24, 2023
  11. Sep 18, 2023
    • raphTec's avatar
      Document shift page up/down · 55a8d759
      raphTec authored and Andreas Klöckner's avatar Andreas Klöckner committed
      55a8d759
    • raphTec's avatar
      Scroll cmdline results on shift page up/down · 82713008
      raphTec authored and Andreas Klöckner's avatar Andreas Klöckner committed
      82713008
    • raphTec's avatar
      Always recall the just executed command on arrow up · c2b68cea
      raphTec authored and Andreas Klöckner's avatar Andreas Klöckner committed
      After executing a command, immediatly hitting the arrow up key should
      recall the just executed command again, like in all shells.
      This commit ensures this behavior by clearing out the saved edit text on
      successful command execution.
      
      Previously, it recalled the last saved edit text if set, which is an
      annoying workflow break compared to other shells.
      c2b68cea
    • raphTec's avatar
      Reword command line help to distinguish history types · 888c7010
      raphTec authored and Andreas Klöckner's avatar Andreas Klöckner committed
      There is the
      - command history, which stores previously executed commands
      - result scrollback, which refers to list of shell prompts and their
        results
      
      The latter one was previously called 'command line history'.
      To avoid confusion, this commit introduces a major new term.
      888c7010
    • raphTec's avatar
      Use arrow keys for command history browsing · ea7981bc
      raphTec authored and Andreas Klöckner's avatar Andreas Klöckner committed
      This changes the arow keys from accessing the command line results to
      browsing the command history, as requested by the main developer:
      https://github.com/inducer/pudb/pull/600#issuecomment-1532444371
      ea7981bc
    • raphTec's avatar
      Restore cmdline text input when browsing history · e39ff402
      raphTec authored and Andreas Klöckner's avatar Andreas Klöckner committed
      Text input to the internal command line is now restored and not lost
      after browsing the history. It is designed to behave just like a
      dedicated history item at the end of the history. This matches the
      behavior of readline in most shells.
      For example, writing a command without executing it, then moving up to
      the most recent history item and down again restores the typed command.
      
      The pudb special behavior of clearing the command when moving down from
      the end of the history is also preserved. In that case the text can be
      restored too by moving up in the history again before typing anything
      new.
      This is akin to using Ctrl-C in common shells to clear the current
      command, but with the ability to restore the input again.
      
      Using the clear button which empties the displayed shell history now
      also clears the command input, since it can be easily restored.
      
      This fixes one of my pain points with the internal pudb command line:
      When writing a lengthy command, accidentally hitting Ctrl-N or Ctrl-P
      overwrites the input text field with no possibility to get the content
      back.
      This is particularly bad after using vim's word completion with Ctrl-N
      for an extensive amount of time, and then accidentally hitting the same
      shortcut in pudb instead of tab completion.
      e39ff402
    • raphTec's avatar
      Use deque with maxsize for command line history · f9ca705b
      raphTec authored and Andreas Klöckner's avatar Andreas Klöckner committed
      A deque handles the size limit internally, eliminating some logic in the
      debugger itself.
      f9ca705b
  12. Aug 01, 2023
  13. May 23, 2023
  14. May 13, 2023