226_emacs lisp log record entry of the control limits emacs

A complete set of common lisp study are summarized as follows:

    https://github.com/GreyZhang/g_lisp

    Analysis spacemacs continue configuration, the above analysis to the following code:

    The first 29 lines of code, the basic functional analysis, the next emacs will probably go look for core-spacemacs.el file in the load-path. This file exists in the following directory:

    Highlight the file is on the map.

    Continue to learn this configuration, start analyzing this document. There are code is as follows:

    Line 11 of the code, is a simple variable assignment. However, this assignment what use is it? Try to look at this variable helps explain:

    This variable is a variable control the number of log messages, should be the display information of the * Message * buffer. My current state of this buffer is as follows:

    I can track record of operational behavior of emacs. Before seeing this buffer of time, but I thought: This is a content emacs tool set can display log records. However, whether this can also be custom modifications? How many log records can be displayed? Can you turn off? A series of questions, I have not thought about before. However, today all of a sudden your answer.

    Next, I did a test, try to try to turn off the log.

    This log record, I set to the maximum 10. I restart emacs, there are several operations, and now the log states are as follows:

    These are all of the log, it also happens to be the number 10 line. Next, try to do some other operations, look at the log sort of content as well as the state.

    Operation can be traced to, and agreed to limit the number of messages also follow me settings. It appears that this feature set from the understanding is correct. As several other settings do not try.

A complete set of common lisp study are summarized as follows:

    https://github.com/GreyZhang/g_lisp

Published 812 original articles · won praise 163 · Views 1.72 million +

Guess you like

Origin blog.csdn.net/grey_csdn/article/details/104270841