From: martin rudalics <rudalics@gmx.at>
To: Miles Bader <miles.bader@necel.com>
Cc: emacs-devel@gnu.org
Subject: Re: whitespace.el's permanent-locals
Date: Wed, 14 Mar 2007 10:33:53 +0100 [thread overview]
Message-ID: <45F7C181.1090203@gmx.at> (raw)
In-Reply-To: <buoveh4zagv.fsf@dhapc248.dev.necel.com>
> I'm inclined to agree, but ... any idea why they were put there in the
> first place?
Putting a nil value into a symbol's property list makes sense iff I want
to keep a record that at some time a value was put there but is no more
needed. Well, maybe also because I'm too lazy to remove an association.
But whitespace.el never puts anything but nil there, does that only when
it's loaded, and nowhere uses `plist-member'.
prev parent reply other threads:[~2007-03-14 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 22:09 whitespace.el's permanent-locals martin rudalics
2007-03-14 4:59 ` Miles Bader
2007-03-14 9:33 ` martin rudalics [this message]
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=45F7C181.1090203@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=miles.bader@necel.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).