all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: net june <netjune@outlook.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "32157@debbugs.gnu.org" <32157@debbugs.gnu.org>
Subject: bug#32157: Emacs 26.1.50: Error in post-command-hook (icomplete-post-command-hook): (void-function set-message-beep)
Date: Mon, 16 Jul 2018 03:21:33 +0000	[thread overview]
Message-ID: <PS1PR04MB2821BE8F35FE8D250F74BD00B75D0@PS1PR04MB2821.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <83k1pwa7q1.fsf@gnu.org>



On 07/15/2018 10:34 PM, Eli Zaretskii wrote:
>> From: net june <netjune@outlook.com>
>> CC: "32157@debbugs.gnu.org" <32157@debbugs.gnu.org>
>> Date: Sun, 15 Jul 2018 03:58:56 +0000
>>
>> On 07/15/2018 12:04 AM, Glenn Morris wrote:
>>>
>>> I imagine this is fixed on master by 109a3bf6a1.
>>> (ie, a duplicate of bug#6997).
>>>
>>
>> It is fixed on master, not on emacs-26. Can you backport it to emacs-26?
> 
> No, it's too extensive, and the problem itself is not important
> enough, I think (why would a GNU/Linux user want to display help on
> Windows-specific features?).  The emacs-26 branch is for fixing bugs
> that are either serious/urgent or which were caused by recent
> regressions.
> 

OK. No perfect product. I can stay with it.

  reply	other threads:[~2018-07-16  3:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-14 11:58 bug#32157: Emacs 26.1.50: Error in post-command-hook (icomplete-post-command-hook): (void-function set-message-beep) net june
2018-07-14 15:58 ` Eli Zaretskii
2018-07-14 16:04   ` Glenn Morris
2018-07-14 16:27     ` Eli Zaretskii
2018-07-15  3:58     ` net june
2018-07-15 14:34       ` Eli Zaretskii
2018-07-16  3:21         ` net june [this message]
2018-07-16  3:23         ` net june
2018-07-16 14:18           ` Eli Zaretskii
2018-07-15  3:29   ` net june
2018-07-15  3:47   ` net june
2018-07-17 20:28     ` Rolf Ade
2018-07-18  1:24     ` 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

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

  git send-email \
    --in-reply-to=PS1PR04MB2821BE8F35FE8D250F74BD00B75D0@PS1PR04MB2821.apcprd04.prod.outlook.com \
    --to=netjune@outlook.com \
    --cc=32157@debbugs.gnu.org \
    --cc=eliz@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.