history
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | history [2007/03/16 22:57] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | # $EPIC: history.txt, | ||
+ | ======Synopsis: | ||
+ | /[[load]] history \\ | ||
+ | /bind //< | ||
+ | /bind //< | ||
+ | /bind //< | ||
+ | /bind //< | ||
+ | /[[set]] history //< | ||
+ | /set history_circleq [ON|OFF|TOGGLE] \\ | ||
+ | /set history_persistent [ON|OFF|TOGGLE] \\ | ||
+ | /set history_remove_dupes [ON|OFF|TOGGLE] \\ | ||
+ | /set history_save_file //< | ||
+ | /set history_save_position [ON|OFF|TOGGLE] \\ | ||
+ | /set history_timestamp [ON|OFF|TOGGLE] \\ | ||
+ | /history //< | ||
+ | / | ||
+ | $historyctl(add //< | ||
+ | $historyctl(delete //< | ||
+ | $historyctl(get //< | ||
+ | $historyctl(index //< | ||
+ | $historyctl(read //< | ||
+ | $historyctl(reset) \\ | ||
+ | $historyctl(save //< | ||
+ | $historyctl(set //< | ||
+ | |||
+ | ======Description: | ||
+ | This script implements input line history retention and recall. | ||
+ | far more featureful than the built in history recall ever was. | ||
+ | |||
+ | It is helpful to note that there are two modes: " | ||
+ | " | ||
+ | |||
+ | Any time you use SEND_LINE (ie, the < | ||
+ | line are added to the history. | ||
+ | back and recall these entries. | ||
+ | |||
+ | =====Keybindings: | ||
+ | ^Name^Action^ | ||
+ | | BACKWARD_HISTORY | Go back (older) one entry in the history buffer. | | ||
+ | | ERASE_HISTORY | Delete the input line and exit browsing mode.| | ||
+ | | FORWARD_HISTORY | Go forward (newer) one entry in the history buffer.| | ||
+ | | SHOVE_TO_HISTORY | Add the input buffer to history, but don't run it. | | ||
+ | |||
+ | For backwards compatability, | ||
+ | save the current contents of the input line in the history (as | ||
+ | SHOVE_TO_HISTORY does) if you are in non-browsing mode. If you are in | ||
+ | browsing mode, it does not save it again, even if you've made changes. | ||
+ | |||
+ | =====Sets: | ||
+ | ^Name^Action^ | ||
+ | |history|How many entries to hold in the history buffer.| | ||
+ | |history_circleq|When ON, BACKWARD_HISTORY and FORWARD_HISTORY "wrap around" | ||
+ | |history_remove_dups|When ON, if a new entry is exactly the same as any old entry, all the old entries are deleted. | ||
+ | |history_persistent|When ON, all history entries will be written to a file during shutdown. | ||
+ | |history_save_file|This is the name of the file that history entries should be saved to on shutdown.| | ||
+ | |history_save_position|When ON, doing a history search (with **/!**) puts you in browsing mode. When OFF, doing a history search merely retrieves the entry but does not put you in browsing mode.| | ||
+ | |history_timestamp|When ON, the **history** command will show the timestamp of each entry in the history buffer. | ||
+ | |||
+ | =====Commands: | ||
+ | | /HISTORY | Show all entries in the history buffer. | | ||
+ | | /HISTORY //< | ||
+ | | / | ||
+ | | / | ||
+ | |||
+ | =====Historyctl function: | ||
+ | You can perform low level operations on the history buffer by using the | ||
+ | historyctl function. | ||
+ | |||
+ | ^Name^Action^ | ||
+ | |add //< | ||
+ | |delete //< | ||
+ | |get //< | ||
+ | |index //< | ||
+ | |read //< | ||
+ | |reset|Clear the history buffer.| | ||
+ | |save //< | ||
+ | |set //< | ||
+ | |||
+ | ======History: | ||
+ | The history script first appeared in epic5-0.0.5. | ||
+ | |||
history.txt · Last modified: 2007/03/16 22:57 by 127.0.0.1