Replies: 2 comments 3 replies
-
It's a trade-off. We programmatically write to the config file (when changes to the preferences dialog are made), and I'm sure it would be sort of unpopular if we obliterated code in the config file every time a change is made from the UI. It's not unheard of for config files to have both machine-written and code sections (Emacs's config file comes to mind), but it's sort of more engineering than I'd like to do. It's always possible to make it a separate file, but that's also kind of confusing. In short, don't know. |
Beta Was this translation helpful? Give feedback.
-
What's the actual use-case for a dynamic configuration? You want to define hotkeys that depend on other values? |
Beta Was this translation helpful? Give feedback.
-
Many python develop tools use python as its config file, such as python use
$PYTHONSTARTUP
which is a python file, ptpython use~/.config/ptpython/config.py
, ipython use~/.ipython/profile_default/ipython_config.py
. How about let pudb use python toconfig itself? I think it can provide more flexibility than dosini file,
especially define of hot key. A
referable example is https://github.com/prompt-toolkit/ptpython/blob/master/examples/ptpython_config/config.py
I think all users of pudb should know how to write python (pudb is python
debugger) so the situation that user don't know how to write the config shouldn't exist.
Beta Was this translation helpful? Give feedback.
All reactions