unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: npostavs@users.sourceforge.net
Cc: 9898@debbugs.gnu.org
Subject: bug#9898: 24.0.90; doc of :key-sequence
Date: Fri, 16 Jul 2021 15:52:37 +0200	[thread overview]
Message-ID: <874kcu8ixm.fsf@gnus.org> (raw)
In-Reply-To: <87ziga11m7.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net's message of "Fri, 24 Mar 2017 23:22:56 -0400")

npostavs@users.sourceforge.net writes:

> As far as I can tell, `:key-sequence nil' doesn't actually do anything
> different from just not specifying `:key-sequence' at all (with the
> minor exception that passing both `:keys STRING' and `:key-sequence nil'
> causes the `:keys STRING' to be ignored).  So I propose just removing
> both `:key-sequence nil' paragraphs.

Looks like Stefan did something along those lines last year:

commit 5734339f4017836a2b171071056a320899a7c8e5
Author:     Stefan Monnier <monnier@iro.umontreal.ca>
AuthorDate: Sun Apr 19 11:19:03 2020 -0400

    * doc/lispref/keymaps.texi (Extended Menu Items, Easy Menu) <:key-sequence>:
    
    Clarify the documentation further

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-07-16 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28 18:48 bug#9898: 24.0.90; doc of :key-sequence Drew Adams
2014-02-09  5:58 ` Lars Ingebrigtsen
2017-03-25  3:22   ` npostavs
2021-07-16 13:52     ` Lars Ingebrigtsen [this message]

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=874kcu8ixm.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=9898@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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).