@@ -332,16 +332,19 @@ by the local file.
332332 (com) end
333333 (Pdb)
334334
335- To remove all commands from a breakpoint, type commands and follow it
335+ To remove all commands from a breakpoint, type `` commands `` and follow it
336336 immediately with ``end ``; that is, give no commands.
337337
338- With no *bpnumber * argument, commands refers to the last breakpoint set.
338+ With no *bpnumber * argument, `` commands `` refers to the last breakpoint set.
339339
340340 You can use breakpoint commands to start your program up again. Simply use
341- the continue command, or step, or any other command that resumes execution.
341+ the :pdbcmd: `continue ` command, or :pdbcmd: `step `,
342+ or any other command that resumes execution.
342343
343- Specifying any command resuming execution (currently continue, step, next,
344- return, jump, quit and their abbreviations) terminates the command list (as if
344+ Specifying any command resuming execution
345+ (currently :pdbcmd: `continue `, :pdbcmd: `step `, :pdbcmd: `next `,
346+ :pdbcmd: `return `, :pdbcmd: `jump `, :pdbcmd: `quit ` and their abbreviations)
347+ terminates the command :pdbcmd: `list ` (as if
345348 that command was immediately followed by end). This is because any time you
346349 resume execution (even with a simple next or step), you may encounter another
347350 breakpoint—which could have its own command list, leading to ambiguities about
0 commit comments