From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Documenting define-generic-mode.
Date: Fri, 29 Apr 2005 08:58:24 +0200 [thread overview]
Message-ID: <87oebyjchb.fsf@xs4all.nl> (raw)
In-Reply-To: <200504290015.j3T0FWA07161@raven.dms.auburn.edu> (Luc Teirlinck's message of "Thu, 28 Apr 2005 19:15:32 -0500 (CDT)")
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Lute Kamstra wrote:
>
> This macro creates a new generic mode. The argument @var{mode} is
> the name of the command for the generic mode; it need not be quoted.
>
> "Name" sounds like a string. "need not" sounds like it is up to the
> user whether he quotes it or not. Is this really correct or is it
> true that it must not be quoted? Of course, the same problems apply
> to the docstring from which the above quote was copied.
I wrote the docstring too. :-) It's true that it is up to the user to
quote the symbol or not. define-generic-mode used to be a function,
so MODE needed to be quoted. When I rewrote it into a macro, I opted
for an unquoted MODE. Similar defining macros use unquoted symbols
too. To be backward compatible, quoting the symbol is still allowed.
> What about:
>
> This macro creates a new generic mode. @var{mode} (an unquoted symbol)
> is the major mode command.
That's fine with me.
Lute.
next prev parent reply other threads:[~2005-04-29 6:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 15:56 Documenting define-generic-mode Lute Kamstra
2005-04-23 22:24 ` Richard Stallman
2005-04-28 13:50 ` Lute Kamstra
2005-04-29 0:15 ` Luc Teirlinck
2005-04-29 6:58 ` Lute Kamstra [this message]
2005-04-29 13:37 ` Luc Teirlinck
2005-05-01 12:06 ` Richard Stallman
2005-05-01 12:23 ` Lute Kamstra
2005-04-29 13:46 ` Luc Teirlinck
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=87oebyjchb.fsf@xs4all.nl \
--to=lute.kamstra.lists@xs4all.nl \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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).