- Oct 06, 2023
-
-
Andreas Klöckner authored
-
Andreas Klöckner authored
-
Andreas Klöckner authored
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Sep 24, 2023
-
-
Andreas Klöckner authored
-
- Sep 18, 2023
-
-
-
-
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.
-
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.
-
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
-
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.
-
A deque handles the size limit internally, eliminating some logic in the debugger itself.
-
- Aug 01, 2023
-
-
Andreas Klöckner authored
-
- May 23, 2023
-
-
- May 13, 2023
-
-
- Apr 30, 2023
-
-
This function may cause an import cycle when it is called during early startup. Specifically, during import of debugger.py, the settings are loaded. Exceptions during load are forwarded to the logging system, where they are handled by TerminalOrStreamHandler. This is turn will call _have_debugger() to determine whether to display an UI dialog. The function attempts to import debugger.py, completing the import cycle.
-
- Apr 26, 2023
-
-
Andreas Klöckner authored
-
- Mar 13, 2023
-
-
- Mar 06, 2023
-
-
Support completing python modules
-
- Jan 10, 2023
-
-
Andreas Klöckner authored
-
- Jan 04, 2023
-
-
Aaron Meurer authored
* Start implementing jump command Right now it doesn't stop on the line (like t), which would be ideal. I can't figure out how to make it do that. pdb's j does it, so it should be possible. It also isn't documented or heavily tested yet. See issue #129. * Fix function name that has changed * Fix the jump command We need to update the UI manually as end() will run past the current line. Also, setting a temporary breakpoint is unnecessary. * Fix keyboard help for jump * Fix flake8 issues Co-authored-by: Andreas Klöckner <inform@tiker.net>
-
- Jan 03, 2023
-
-
- Jan 01, 2023
- Nov 20, 2022
-
-
- Also continue to show the error message in the ui_log
-
Andreas Klöckner authored
-
- Nov 07, 2022
-
-
Being more specific about which keys adjust width or height. See also https://stackoverflow.com/a/64482286
-
- Nov 03, 2022
-
-
Andreas Klöckner authored
-