From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: net june <netjune@outlook.com>
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: Tue, 17 Jul 2018 21:24:54 -0400 [thread overview]
Message-ID: <jwvfu0hz6h4.fsf-monnier+bug#32157@gnu.org> (raw)
In-Reply-To: <PS1PR04MB2821A417DA0FC6D9344224F5B75E0@PS1PR04MB2821.apcprd04.prod.outlook.com> (net june's message of "Sun, 15 Jul 2018 03:47:21 +0000")
> In step 3, it seems that ONLY THE FIRST tab key produce the error
> message for a emacs instance. Pressing the tab key twice, it will show
> the completion window with content as following:
In my tests, the first TAB already brings up the completion you describe
(and doesn't signal any error).
> Why these symbols are visible on GNU/Linux?
Because these are functions defined in Elisp files available in
load-path, so they can be loaded (and you can subsequently call them)
even on GNU/Linux (at that point, they likely won't work as expected
because their implementation depends on underlying features only
provided by the w32 part of the C code).
In some unlikely hypothetical future, they could even be useful if we
can manage to build a GNU/Linux version of Emacs which links with Wine
to display w32 frames.
> Is there something wrong with my build commands?
No,
Stefan
prev parent reply other threads:[~2018-07-18 1:24 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
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 [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='jwvfu0hz6h4.fsf-monnier+bug#32157@gnu.org' \
--to=monnier@iro.umontreal.ca \
--cc=32157@debbugs.gnu.org \
--cc=netjune@outlook.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.