[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#77989: [PATCH] Use future history to select current script for pdb e
From: |
Paul D. Nelson |
Subject: |
bug#77989: [PATCH] Use future history to select current script for pdb et al |
Date: |
Tue, 22 Apr 2025 17:01:18 +0200 |
The simplest way I know to debug the current Python script is:
1. Copy the name of the current file (C-x C-j C-0 w)
2. M-x pdb RET yank RET (possibly after deleting previous file name)
This seems like a good place to introduce a "future history" operation.
The attached patch does so, via a new optional argument to
gud-query-cmdline. The above then simplifies to M-x pdb RET M-n RET.
Existing behavior is unchanged. I added the same feature to other gdb
commands for which it seemed to make sense (perldb, guiler). Feedback
or other suggestions would be welcome.
0001-Add-forward-history-support-for-some-debuggers.patch
Description: Text Data
- bug#77989: [PATCH] Use future history to select current script for pdb et al,
Paul D. Nelson <=