@@ -267,9 +267,9 @@ persist between invocations of your application, you'll need to do a little work
267
267
268
268
Users can access command history using two methods:
269
269
270
- - the [ readline] ( https://docs.python.org/3/library/readline.html ) library which provides a Python
270
+ - The [ readline] ( https://docs.python.org/3/library/readline.html ) library which provides a Python
271
271
interface to the [ GNU readline library] ( https://en.wikipedia.org/wiki/GNU_Readline )
272
- - the ` history ` command which is built-in to ` cmd2 `
272
+ - The ` history ` command which is built-in to ` cmd2 `
273
273
274
274
From the prompt in a ` cmd2 ` -based application, you can press ` Control-p ` to move to the previously
275
275
entered command, and ` Control-n ` to move to the next command. You can also search through the
@@ -280,10 +280,10 @@ details, including all the available commands, and instructions for customizing
280
280
The ` history ` command allows a user to view the command history, and select commands from history by
281
281
number, range, string search, or regular expression. With the selected commands, users can:
282
282
283
- - re -run the commands
284
- - edit the selected commands in a text editor, and run them after the text editor exits
285
- - save the commands to a file
286
- - run the commands, saving both the commands and their output to a file
283
+ - Re -run the commands
284
+ - Edit the selected commands in a text editor, and run them after the text editor exits
285
+ - Save the commands to a file
286
+ - Run the commands, saving both the commands and their output to a file
287
287
288
288
Learn more about the ` history ` command by typing ` history -h ` at any ` cmd2 ` input prompt, or by
289
289
exploring [ Command History For Users] ( ../features/history.md#for-users ) .
0 commit comments