* Add PUDB_RDB_REVERSE var to control reverse mode

* Fix flake8 warnings

* Allow defining term_size via PUDB_TERM_SIZE env var

* Add doc

* Fix flake8 issue

* Describe the terminal size precedence

* Mention the PUDB_RDB_HOST and PUDB_RDB_PORT as well

* Fail on invalid PUDB_TERM_SIZE

* Remove dependence on telnetlib which was removed from Python 3.13

Only some constant values were being used so those values were copied
into remote.py instead of being referenced from telnetlib.

* Replace bytes function calls with bytes literals

raphTec authored May 12, 2023 and Andreas Klöckner committed Sep 17, 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.

raphTec authored May 12, 2023 and Andreas Klöckner committed Sep 17, 2023

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.

raphTec authored May 12, 2023 and Andreas Klöckner committed Sep 17, 2023

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

raphTec authored Apr 26, 2023 and Andreas Klöckner committed Sep 17, 2023

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.

raphTec authored Apr 25, 2023 and Andreas Klöckner committed Sep 17, 2023

A deque handles the size limit internally, eliminating some logic in the
debugger itself.

https://github.com/inducer/pudb/pull/603

raphTec authored Apr 25, 2023 and Andreas Klöckner committed 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.

Wu Zhenyu authored Mar 06, 2023 and Andreas Klöckner committed Mar 06, 2023

Support completing python modules