From: Juri Linkov <juri@jurta.org>
Cc: steve.yegge@gmail.com, emacs-devel@gnu.org
Subject: Re: show-buffer-local-variables
Date: Sun, 02 Oct 2005 23:22:52 +0300 [thread overview]
Message-ID: <87wtkvzvdf.fsf@jurta.org> (raw)
In-Reply-To: <E1ELqkE-0006jr-Gh@fencepost.gnu.org> (Richard M. Stallman's message of "Sat, 01 Oct 2005 19:26:18 -0400")
> I noticed this entry in emacs/etc/TODO:
>
> ** Add a command to make a local variables list in the current buffer
> and/or add a variable to the list.
>
> I recently wrote a function that does the former, if I understand the
> entry correctly.
>
> No, it is a misunderstanding. A local variables list is text
> at the end of the file.
It seems this command should do the same thing as currently `dcl-save-option'
and `dcl-save-all-options' from emacs/lisp/progmodes/dcl-mode.el do,
but more generally.
These commands make a Local Variables section with prefix/suffix strings
extracted from `comment-start' and `comment-end'. But the result is not
always nice. For example, in Emacs-Lisp mode the value of `comment-start'
is ";", but a nicer prefix would be ";;" or ";;;". Perhaps some modes
should override this value with a new variable like `local-variables-prefix'.
Also the local variables list for `dcl-save-all-options' is not general.
A better choice is a list like used by desktop.el to save the values of
local variables in the desktop file, i.e. the option `desktop-locals-to-save'.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-10-02 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 13:02 show-buffer-local-variables Steve Yegge
2005-10-01 23:26 ` show-buffer-local-variables Richard M. Stallman
2005-10-02 20:22 ` Juri Linkov [this message]
2005-10-03 14:42 ` show-buffer-local-variables Stefan Monnier
2005-10-04 5:02 ` show-buffer-local-variables Richard M. Stallman
2005-10-02 21:15 ` show-buffer-local-variables Ken Manheimer
2005-10-03 15:34 ` show-buffer-local-variables Richard M. Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wtkvzvdf.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=steve.yegge@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).