|
| 1 | +Configuration |
| 2 | +------------- |
| 3 | + |
| 4 | +Following options are available to customise PuDB behaviour: |
| 5 | + |
| 6 | +shell |
| 7 | +***** |
| 8 | + |
| 9 | +This is the shell that will be used when you hit ``!``. Available choices: |
| 10 | + |
| 11 | +* internal |
| 12 | +* classic |
| 13 | +* ipython |
| 14 | +* bpython |
| 15 | +* ptpython |
| 16 | + |
| 17 | +theme |
| 18 | +***** |
| 19 | + |
| 20 | +PuDB UI theme. Select one available or use your own by setting ``custom_theme``. |
| 21 | + |
| 22 | +custom_theme |
| 23 | +************ |
| 24 | + |
| 25 | +To use a custom theme, see example-theme.py in the pudb distribution. Enter |
| 26 | +the full path to a file like it in the box above. ``~`` will be expanded to |
| 27 | +your home directory. Note that a custom theme will not be applied until you |
| 28 | +close this dialog. |
| 29 | + |
| 30 | + |
| 31 | +line_numbers |
| 32 | +************ |
| 33 | + |
| 34 | +Show or hide the line numbers in the source code pane. |
| 35 | + |
| 36 | +sidebar_width |
| 37 | +************* |
| 38 | + |
| 39 | +The sidebar pane width. |
| 40 | + |
| 41 | +variables_weight |
| 42 | +**************** |
| 43 | + |
| 44 | +The variables pane height. |
| 45 | + |
| 46 | +stack_weight |
| 47 | +************ |
| 48 | + |
| 49 | +The stack pane height. |
| 50 | + |
| 51 | +breakpoints_weight |
| 52 | +****************** |
| 53 | + |
| 54 | +The breakpoints pane height. |
| 55 | + |
| 56 | +current_stack_frame |
| 57 | +******************* |
| 58 | + |
| 59 | +Show the current stack frame at the top or at the bottom. |
| 60 | + |
| 61 | +stringifier |
| 62 | +*********** |
| 63 | + |
| 64 | +This is the default function that will be called on variables in the variables |
| 65 | +list. Note that you can change this on a per-variable basis by selecting a |
| 66 | +variable and hitting Enter or by typing ``t``/``s``/``r``. Note that str and |
| 67 | +repr will be slower than type and have the potential to crash PuDB. |
| 68 | + |
| 69 | +custom_stringifier |
| 70 | +****************** |
| 71 | + |
| 72 | +To use a custom stringifier, see example-stringifier.py in the pudb |
| 73 | +distribution. Enter the full path to a file like it in the box above. ``~`` |
| 74 | +will be expanded to your home directory. The file should contain a function |
| 75 | +called ``pudb_stringifier()`` at the module level, which should take a single |
| 76 | +argument and return the desired string form of the object passed to it. Note |
| 77 | +that if you choose a custom stringifier, the variables view will not be updated |
| 78 | +until you close this dialog. |
| 79 | + |
| 80 | +wrap_variables |
| 81 | +************** |
| 82 | + |
| 83 | +Note that you can change this option on a per-variable basis by selecting the |
| 84 | +variable and pressing ``w``. |
| 85 | + |
| 86 | +display |
| 87 | +******* |
| 88 | + |
| 89 | +What driver is used to talk to your terminal. ``raw`` has the most features |
| 90 | +(colors and highlighting), but is only correct for XTerm and terminals like it. |
| 91 | +``curses`` has fewer features, but it will work with just about any terminal. |
| 92 | +``auto`` will attempt to pick between the two based on availability and |
| 93 | +the ``$TERM`` environment variable. |
| 94 | + |
| 95 | +Changing this setting requires a restart of PuDB. |
| 96 | + |
| 97 | +prompt_on_quit |
| 98 | +************** |
| 99 | + |
| 100 | +Prompt or not before quitting. |
0 commit comments