[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: doc elisp intro cross reference fixes

From: Juri Linkov
Subject: Re: doc elisp intro cross reference fixes
Date: Tue, 18 Nov 2003 17:34:28 +0200
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

"Robert J. Chassell" <address@hidden> writes:
> Juri Linkov <address@hidden> wrote
>     The edit-options command is no longer described in the emacs
>     manual, because it is obsolete now.  Perhaps emacs-lisp-intro
>     shouldn't suggest obsolete packages, so all these three paragraphs
>     about edit-options should be removed from emacs-lisp-intro.
> This is a good idea.  I have commented out the three paragraphs in 
> emacs/lispintro/emacs-lisp-intro.texi 
>     (eintr)defvar and asterisk
> Next time you `make info dvi html' the surface representations should
> be updated.
> Is the main point of the node still accurate?
>     When you specified a variable using the @code{defvar} special
>     form, you could distinguish a readily settable variable from
>     others by typing an asterisk, @samp{*}, in the first column of its
>     documentation string.  ....

Yes, this point is still accurate.  However, I'd like to propose a
better alternative for the above mentioned three paragraphs: to replace
in those three paragraphs the command `edit-options' by its valid
equivalent `set-variable'.  Sorry, I didn't propose this earlier,
this idea came to me just now.

This means that you could (and still can) use the @code{set-variable}
command to change the value of
@code{shell-command-default-error-buffer} temporarily.

@findex set-variable
However, options set using @code{set-variable} are set only for the
duration of your editing session.  The new values are not saved
between sessions.  Each time Emacs starts, it reads the original
value, unless you change the value within your @file{.emacs} file,
either by setting it manually or by using @code{customize}.
@xref{Emacs Initialization, , Your @file{.emacs} File}.

For me, the major use of the @code{set-variable} command is to suggest
variables that I might want to set in my @file{.emacs} file.  I urge
you to look through the list.

Seems this last paragraph should be improved to tell that full list
of user options can be displayed by pressing the tab character in the
minibuffer after calling the `M-x set-variable' command.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]