all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: What lookup-key returns for an undefined key
Date: Sat, 15 Jan 2005 11:18:28 -0600 (CST)	[thread overview]
Message-ID: <200501151718.j0FHISK05626@raven.dms.auburn.edu> (raw)
In-Reply-To: <01c4fb00$Blat.v2.2.2$c89387a0@zahav.net.il> (eliz@gnu.org)

Eli Zaretskii wrote"
   
   In Emacs 21.3, lookup-key returns `undefined' for an undefined key; in
   the current CVS it returns nil.

   If this change is intentional, I think we should reflect that in NEWS.

   Two bundled Lisp packages are affected by this: woman.el and
   gnus-util.el.  I've fixed the former, but not the latter.

There are three types of key that are commonly referred to as
"undefined":  keys that are not bound, keys bound to the symbol nil and
keys bound to the command `undefined'.  If nothing else tries to
define the key, the end result is the same, in as far as the user is
concerned.  If something else tries to define the key, there are
subtle differences.  `lookup-key' returns nil for the first two types
and `undefined' for the latter.

`dired-mode-map' used by woman.el has been changed from 21.3 to unbind
several keys that were formerly bound to the command `undefined'.  I
believe that your change to woman.el is correct.  However that code
was _already_ broken in 21.3.  Probably, gnus-util.el needs a similar
change.

Sincerely,

Luc.

  parent reply	other threads:[~2005-01-15 17:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15 12:49 What lookup-key returns for an undefined key Eli Zaretskii
2005-01-15 16:33 ` Luc Teirlinck
2005-01-15 17:18 ` Luc Teirlinck [this message]
2005-01-16  4:41   ` Eli Zaretskii
2005-01-16  4:58     ` Luc Teirlinck
2005-01-17  2:08     ` Richard Stallman
2005-01-17  3:22       ` Luc Teirlinck
2005-01-17 23:43         ` Richard Stallman
2005-01-15 18:36 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200501151718.j0FHISK05626@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.