![]() ![]() However, other units, aliases, and appropriate conversion functions have been implemented. ![]() 'b' is for the number of bytes that are allowed on the file systemįor all history files to collectively consume. Is effectively a timeout of the history files, and 's' is for the number of seconds in the past that are allowed - which 'files' is for specifying the total number of history files to keep, 'commands' is for limiting the number of past commands executed in the.The garbage collector accepts four canonical units: Two arguments to the -size option, a la -size 8128 commands. On the command line, though, you just pass in However, you can also use a string with the same This variable is usually a tuple or list of a To determine the size and units of what should be allowed to remain on disk. Normally, the garbage collector uses the environment variable $XONSH_HISTORY_SIZE The action here allows you to manually start a new garbage collector, possibly with The garbage collector only operates on unlocked history files. Garbage control is launched automatically for every xonsh thread, but runs in theĪ background thread. To be stored, it is necessary to be able to clean out the cache every once in a Since history has the potential for a lot of information Last, but certainly not least, the gc action is a manual hook into executing Previous commands won’t be saved, but future Only session metadata will be saved, not commands or output. Later commandsĭeletes the history from the current session and turns off history saving for the clear action #ĭeletes the history from the current session up until this point. Tries to pull the history from parallel sessions and add to the current session.įor example if there are two parallel terminal windows the run of history pullĬommand from the second terminal window will get the commands from the first terminal. The flush action to immediately save the session history to disk and make itĪccessible from other shell sessions. May be useful to share entries between shell sessions. Keep session history free from noise from other sessions. This is in order to reduce unnecessary I/O and to Normally, the history entries are kept in memory and are only saved to disk once In a terminal, this will appear in color, with the first history The commands list this differences in the command themselves.įor the commands, the input sequences are diff’d first, prior to the outputsīeing compared. The environment section describes the differences in the environment Their file names, sessionids, and time stamps. The header describes the meta-information about the histories, such as
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |