From: Ken Manheimer <ken.manheimer@gmail.com>
Cc: Steve Yegge <steve.yegge@gmail.com>, emacs-devel@gnu.org
Subject: Re: show-buffer-local-variables
Date: Sun, 2 Oct 2005 17:15:04 -0400 [thread overview]
Message-ID: <2cd46e7f0510021415m49df6599h7291537115a0dc01@mail.gmail.com> (raw)
In-Reply-To: <E1ELqkE-0006jr-Gh@fencepost.gnu.org>
On 10/1/05, Richard M. Stallman <rms@gnu.org> wrote:
> 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.
if i'm understanding correctly, then i include the functionality being
sought in the new version of allout. (allout uses emacs local file
variables to stash a symmetric-key hint and a symmetric-key verifier
string in the file, when those features are enabled.)
here are excerpts from relevant functions that describe the interface:
(defun allout-adjust-file-variable (varname value)
"Adjust the setting of an emacs file variable named VARNAME to VALUE.
This activity is inhibited if either `enable-local-variables'
`allout-enable-file-variable-adjustment' are nil.
When enabled, an entry for the variable is created if not already present,
or changed if established with a different value. The section for the file
variables, itself, is created if not already present. When created, the
section lines \(including the section line) exist as second-level topics in
a top-level topic at the end of the file.
enable-local-variables must be true for any of this to happen."
[...])
(defun allout-file-vars-section-data ()
"Return data identifying the file-vars section, or nil if none.
Returns list `(beginning-point prefix-string suffix-string)'."
[...])
it would probably be trivial to revise alout-adjust-file-variable to
do wrap a file variables section it creates in an outline topic only
if the buffer is in outline mode. it would also be nice to offload
this functionality from allout, and get scrutiny from others to see
whether the functionality is sufficiently general.
i suppose these functions would be best situated in files.el, to
reside with hack-local-variables &c. ?
ken
ken.manheimer@gmail.com
next prev parent reply other threads:[~2005-10-02 21:15 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 ` show-buffer-local-variables Juri Linkov
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 ` Ken Manheimer [this message]
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=2cd46e7f0510021415m49df6599h7291537115a0dc01@mail.gmail.com \
--to=ken.manheimer@gmail.com \
--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).