all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 39630@debbugs.gnu.org, 39802@debbugs.gnu.org,
	"積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#39802: bug#39630: Mention how to unset keys in Your Init File
Date: Sat, 29 Feb 2020 06:22:58 +0100	[thread overview]
Message-ID: <87blpi6k7h.fsf@stefankangas.se> (raw)
In-Reply-To: <87wo867ztf.fsf@gmail.com> (Noam Postavsky's message of "Sat, 29 Feb 2020 00:00:28 -0500")

Noam Postavsky <npostavs@gmail.com> writes:

> I don't know about 39631, but 39630 is clearly the same as 39802 (I did
> have a feeling of familiarity when I initially read that one), so it
> doesn't make sense to mark it as wontfix when we are actually fixing it.

Thanks.  I had missed the ongoing work in Bug#39802.

Best regards,
Stefan Kangas





      reply	other threads:[~2020-02-29  5:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16  3:28 bug#39630: Mention how to unset keys in Your Init File 積丹尼 Dan Jacobson
     [not found] ` <handler.39630.C.15829502435362.notifdonectrl.0@debbugs.gnu.org>
2020-02-16  4:14   ` bug#39631: Mention how to remove entire keymaps " 積丹尼 Dan Jacobson
2020-02-16 15:20     ` Eli Zaretskii
2020-02-16 16:30       ` 積丹尼 Dan Jacobson
2020-02-16 16:37       ` 積丹尼 Dan Jacobson
2020-02-29  4:28       ` Stefan Kangas
2020-02-29  4:51     ` bug#39631: Actually 39802 solves the need for 39630 and 39631 積丹尼 Dan Jacobson
2020-02-29  5:17     ` bug#39631: Zapping a whole keymap 積丹尼 Dan Jacobson
2020-02-16 15:19 ` bug#39630: Mention how to unset keys in Your Init File Eli Zaretskii
2020-02-16 16:28   ` 積丹尼 Dan Jacobson
2020-02-16 16:44   ` 積丹尼 Dan Jacobson
2020-02-29  4:23   ` Stefan Kangas
2020-02-29  5:00     ` Noam Postavsky
2020-02-29  5:22       ` Stefan Kangas [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

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

  git send-email \
    --in-reply-to=87blpi6k7h.fsf@stefankangas.se \
    --to=stefan@marxist.se \
    --cc=39630@debbugs.gnu.org \
    --cc=39802@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=npostavs@gmail.com \
    /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.