From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: discrepancy between read-key-sequence and manual
Date: Mon, 11 Sep 2006 16:25:34 +0200 [thread overview]
Message-ID: <85d5a2h44h.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3d5a2h4ca.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Mon\, 11 Sep 2006 16\:20\:53 +0200")
storm@cua.dk (Kim F. Storm) writes:
> David Kastrup <dak@gnu.org> writes:
>
>> Should the code be made to match the documentation, or the other way
>> round?
>
> The manual is supposed to document the current behaviour.
> So please fix the manual.
Will do once I am through with this mess. Good for headaches.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-09-11 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 13:42 discrepancy between read-key-sequence and manual David Kastrup
2006-09-11 14:20 ` Kim F. Storm
2006-09-11 14:25 ` David Kastrup [this message]
2006-09-11 19:58 ` Richard Stallman
2006-09-11 20:05 ` David Kastrup
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=85d5a2h44h.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@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).