From: Richard Stallman <rms@gnu.org>
Cc: juanleon1@gmail.com, emacs-devel@gnu.org
Subject: Re: Making hide-ifdef-use-define-alist more user friendly
Date: Tue, 22 Feb 2005 13:11:50 -0500 [thread overview]
Message-ID: <E1D3eVi-0000Q0-Me@fencepost.gnu.org> (raw)
In-Reply-To: <m3650m437r.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
In alists and hash tables, the key must be a string, while in vectors,
the key must be a symbol...
The following patch changes this to accept both strings and symbols as
keys in all cases.
It sounds good to me. Thanks for thinking of it.
Could you also mention this in NEWS, and update the Lisp manual?
next prev parent reply other threads:[~2005-02-22 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 9:03 Making hide-ifdef-use-define-alist more user friendly Juan-Leon Lahoz Garcia
2005-02-21 10:28 ` Kim F. Storm
2005-02-21 11:13 ` Juan LEON Lahoz Garcia
2005-02-22 18:12 ` Richard Stallman
2005-02-22 18:11 ` Richard Stallman [this message]
2005-02-22 20:54 ` Kim F. Storm
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=E1D3eVi-0000Q0-Me@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juanleon1@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).