Mercurial > emacs
changeset 103044:cede530821ca
* entering.texi (Entering Emacs): Document initial-buffer-choice.
* building.texi (Lisp Interaction): Document initial-scratch-message.
author | Chong Yidong <cyd@stupidchicken.com> |
---|---|
date | Wed, 22 Apr 2009 01:29:25 +0000 |
parents | 527362da5918 |
children | 1699b004aa7f |
files | doc/emacs/ChangeLog doc/emacs/building.texi doc/emacs/entering.texi |
diffstat | 3 files changed, 28 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/emacs/ChangeLog Tue Apr 21 12:03:46 2009 +0000 +++ b/doc/emacs/ChangeLog Wed Apr 22 01:29:25 2009 +0000 @@ -1,3 +1,9 @@ +2009-04-22 Chong Yidong <cyd@stupidchicken.com> + + * entering.texi (Entering Emacs): Document initial-buffer-choice. + + * building.texi (Lisp Interaction): Document initial-scratch-message. + 2009-04-18 Juanma Barranquero <lekktu@gmail.com> * msdog.texi (Windows Fonts): Fix typos.
--- a/doc/emacs/building.texi Tue Apr 21 12:03:46 2009 +0000 +++ b/doc/emacs/building.texi Wed Apr 22 01:29:25 2009 +0000 @@ -1404,6 +1404,13 @@ before point. The result is a complete typescript of the expressions you have evaluated and their values. +@vindex initial-scratch-message + At startup, the @samp{*scratch*} buffer contains a short message, in +the form of a Lisp comment, that explains what it is for. This +message is controlled by the variable @code{initial-scratch-message}, +which should be either a string or @code{nil}. If you set it to the +empty string, or @code{nil}, the initial message is suppressed. + @findex lisp-interaction-mode All other commands in Lisp Interaction mode are the same as in Emacs Lisp mode. You can enable Lisp Interaction mode by typing @kbd{M-x
--- a/doc/emacs/entering.texi Tue Apr 21 12:03:46 2009 +0000 +++ b/doc/emacs/entering.texi Wed Apr 22 01:29:25 2009 +0000 @@ -64,13 +64,13 @@ features exist mainly for advanced users. @xref{Emacs Invocation}. @vindex inhibit-startup-screen - If the value of the variable @code{inhibit-startup-screen} is -non-@code{nil}, Emacs does not display the startup screen. In that -case, if one or more files were specified on the command line, Emacs -simply displays those files; otherwise, it displays a buffer named -@samp{*scratch*}, which can be used to evaluate Emacs Lisp expressions -interactively (@pxref{Lisp Interaction}). You can set the variable -@code{inhibit-startup-screen} by using the Customize facility + If the variable @code{inhibit-startup-screen} is non-@code{nil}, +Emacs does not display the startup screen. In that case, if one or +more files were specified on the command line, Emacs simply displays +those files; otherwise, it displays a buffer named @samp{*scratch*}, +which can be used to evaluate Emacs Lisp expressions interactively. +@xref{Lisp Interaction}. You can set the variable +@code{inhibit-startup-screen} using the Customize facility (@pxref{Easy Customization}), or by editing your initialization file (@pxref{Init File}).@footnote{Note that setting @code{inhibit-startup-screen} in @file{site-start.el} doesn't work, @@ -78,6 +78,14 @@ @file{site-start.el}. @xref{Init File}, for information about @file{site-start.el}.} + You can also force Emacs to display a file or directory at startup +by setting the variable @code{initial-buffer-choice} to a +non-@code{nil} value. (In that case, even if you specify one or more +files on the command line, Emacs opens but does not display them.) +The value of @code{initial-buffer-choice} can be either the name of +the desired file or directory, or @code{t}, which means to display the +@samp{*scratch*} buffer. + @node Exiting, Basic, Entering Emacs, Top @section Exiting Emacs @cindex exiting