From: Juanma Barranquero <lekktu@gmail.com>
To: Albert <georgealbert@qq.com>
Cc: 37495 <37495@debbugs.gnu.org>
Subject: bug#37495: 27.0.50; lwindow doesn't pass to system
Date: Wed, 25 Sep 2019 14:44:17 +0200 [thread overview]
Message-ID: <CAAeL0SQ5aLxO5aV69WPsr7k3hrq7F72FE_2JjbN5OB_bghiGZA@mail.gmail.com> (raw)
In-Reply-To: <tencent_E07382EE5E02608CE0394B22E0A44ACE1D09@qq.com>
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
In my system, using that very same snapshot, w32-pass-lwindow-to-system is
t and it doesn't swallow any LWin command.
So it seems something specific to your setup.
What does
emacs -Q --batch --eval "(princ w32-pass-lwindow-to-system)"
return?
Does it change if you do create an empty directory, let's call it C:\EMPTY,
and you set HOME to it?
set HOME=C:\EMPTY
emacs -Q --batch --eval "(princ w32-pass-lwindow-to-system)"
[-- Attachment #2: Type: text/html, Size: 679 bytes --]
next prev parent reply other threads:[~2019-09-25 12:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 1:22 bug#37495: 27.0.50; lwindow doesn't pass to system Albert
2019-09-24 4:41 ` Juanma Barranquero
2019-09-24 13:05 ` bug#37495: �ظ��� " Albert
2019-09-24 13:50 ` Juanma Barranquero
2019-09-24 16:39 ` Eli Zaretskii
2019-09-24 16:43 ` bug#37495: �ظ��� " Albert
2019-09-24 16:55 ` Juanma Barranquero
2019-09-24 16:59 ` bug#37495: �ظ��� " Albert
2019-09-24 17:17 ` Juanma Barranquero
2019-09-24 19:29 ` bug#37495: �ظ��� " Albert
2019-09-24 23:09 ` Juanma Barranquero
2019-09-24 17:17 ` Eli Zaretskii
2019-09-24 17:22 ` bug#37495: �ظ��� " Albert
2019-09-24 23:53 ` Juanma Barranquero
2019-09-25 5:27 ` bug#37495: �ظ��� " Albert
2019-09-25 6:24 ` Eli Zaretskii
2019-09-25 6:26 ` bug#37495: �ظ��� " Albert
2019-09-25 12:44 ` Juanma Barranquero [this message]
2019-09-25 12:49 ` Albert
2019-09-25 13:12 ` Juanma Barranquero
2019-09-25 13:16 ` bug#37495: �ظ��� " Albert
2019-09-25 13:41 ` Juanma Barranquero
2019-09-25 13:49 ` bug#37495: �ظ��� " Albert
2019-09-25 14:12 ` Juanma Barranquero
2019-09-25 14:16 ` bug#37495: �ظ��� " Albert
2019-09-25 15:14 ` Eli Zaretskii
2019-09-25 15:22 ` Juanma Barranquero
2019-09-25 15:30 ` bug#37495: �ظ��� " Albert
2019-09-26 5:38 ` bug#37495: 回复： " Albert
2019-09-26 11:45 ` Juanma Barranquero
2019-09-26 12:17 ` Eli Zaretskii
2019-09-26 13:40 ` bug#37495: �ظ��� bug#37495: �ظ��� " Albert
2019-09-29 3:29 ` Albert
2019-09-29 3:44 ` bug#37495: 回复： " Juanma Barranquero
2019-09-25 15:11 ` Eli Zaretskii
2019-09-25 6:12 ` Eli Zaretskii
2019-09-25 7:52 ` Andreas Schwab
2019-09-25 8:53 ` Eli Zaretskii
2019-09-25 12:36 ` Juanma Barranquero
2019-09-25 12:45 ` Juanma Barranquero
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=CAAeL0SQ5aLxO5aV69WPsr7k3hrq7F72FE_2JjbN5OB_bghiGZA@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=37495@debbugs.gnu.org \
--cc=georgealbert@qq.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 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).