unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: emacs-devel@gnu.org
Subject: Re: Define-key doc string - binding changes always if it exists
Date: Thu, 11 Aug 2005 17:45:08 +0200	[thread overview]
Message-ID: <42FB7284.4000900@student.lu.se> (raw)
In-Reply-To: <ddfpgo$m1t$1@sea.gmane.org>

Kevin Rodgers wrote:

> I don't agree.  You've changed:
>
> > -If KEYMAP is a sparse keymap with a binding for KEY, the existing
> > -binding is altered.  If there is no binding for KEY, the new pair
> > -binding KEY to DEF is added at the front of KEYMAP.  */)
>
> to:
>
> > +If KEYMAP is a sparse keymap and there is no binding for KEY, the new
> > +pair binding KEY to DEF is added at the front of KEYMAP.  */)
>
> The original does not say anything about full keymaps (because there is
> nothing to add), whereas your version doesn't say anything about a KEY
> that's already bound in a sparse KEYMAP.

I thought that in the same way there is nothing to add about full 
keymaps there is nothing to add in the case when there is a binding. It 
behaves the same for both full and sparse keymaps.

>
> Your version is close to what's in Emacs 21, which was corrected to
> distinguish between a new binding and an altered binding:
>
> | If KEYMAP is a sparse keymap, the pair binding KEY to DEF is added at
> | the front of KEYMAP.

Yes, but with the important distinction that it is more specific, it 
tries to say clearly that it is just for the case when there is no 
binding. However if people do not find this clear then of course we 
should not change it. Though I personally think it is more clear... ;-)

This is no big issue of course.

  reply	other threads:[~2005-08-11 15:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 21:37 Define-key doc string - binding changes always if it exists Lennart Borgman
2005-08-11 15:05 ` Kevin Rodgers
2005-08-11 15:45   ` Lennart Borgman [this message]
2005-08-12  7:19 ` Stefan Monnier

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=42FB7284.4000900@student.lu.se \
    --to=lennart.borgman.073@student.lu.se \
    --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).