unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Albert" <georgealbert@qq.com>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: 37495 <37495@debbugs.gnu.org>
Subject: bug#37495: ��� bug#37495: 27.0.50; lwindow doesn't pass to system
Date: Wed, 25 Sep 2019 03:29:13 +0800	[thread overview]
Message-ID: <tencent_F34B40BA5110E75084B094C83952CECFDD06@qq.com> (raw)
In-Reply-To: <CAAeL0SRWLA5u666Z7q-Q8J_MNZ0Es7vidx63RSgPqJD+bMFnnA@mail.gmail.com>


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset="gb18030", Size: 1965 bytes --]

So, let's recapitulate.


- You start Emacs 27.0.50
- In your init file(s), you do not change the default value of w32-pass-lwindow-to-system
- While Emacs has the focus, if you press an lwindow combination, Emacs catches it and it is not passed back to Windows.
- So, from inside 27.0.50, you cannot do LWin+R o LWin+D, etc.
- But this didn't happen with Emacs 26.2.


&gt; Am I right now?


&nbsp;&nbsp; Yes, you are right. 



If  so, when you're inside Emacs 27.0.50, what does it say when you examine  the value of w32-pass-lwindow-to-system? For example, with  describe-variable.


Does still happen if you start Emacs with&nbsp;


&nbsp; &nbsp;emacs -Q


C:\emacs-27.0.50-snapshot-2019-09-18-x86_64\bin&gt;emacs -Q



------------------&nbsp;ԭʼÓʼþ&nbsp;------------------
·¢¼þÈË:&nbsp;"Juanma Barranquero"<lekktu@gmail.com&gt;;
·¢ËÍʱ¼ä:&nbsp;2019Äê9ÔÂ25ÈÕ(ÐÇÆÚÈý) Á賿1:17
ÊÕ¼þÈË:&nbsp;"Albert"<georgealbert@qq.com&gt;;
³­ËÍ:&nbsp;"Eli Zaretskii"<eliz@gnu.org&gt;;"37495"<37495@debbugs.gnu.org&gt;;
Ö÷Ìâ:&nbsp;Re: bug#37495: 27.0.50; lwindow doesn't pass to system




On Tue, Sep 24, 2019 at 6:59 PM Albert <georgealbert@qq.com&gt; wrote:

&gt; I'm sorry, the default value of w32-pass-lwindow-to-system is t. I dont' change w32-pass-lwindow-to-system in init file.


So, let's recapitulate.


- You start Emacs 27.0.50
- In your init file(s), you do not change the default value of w32-pass-lwindow-to-system
- While Emacs has the focus, if you press an lwindow combination, Emacs catches it and it is not passed back to Windows.
- So, from inside 27.0.50, you cannot do LWin+R o LWin+D, etc.
- But this didn't happen with Emacs 26.2.


Am I right now?


If so, when you're inside Emacs 27.0.50, what does it say when you examine the value of w32-pass-lwindow-to-system? For example, with describe-variable.


Does still happen if you start Emacs with&nbsp;


&nbsp; &nbsp;emacs -Q


?

[-- Attachment #1.2: Type: text/html, Size: 2832 bytes --]

[-- Attachment #2: 2D01D01B@E6FD2546.896E8A5D.jpg --]
[-- Type: image/jpeg, Size: 50491 bytes --]

  reply	other threads:[~2019-09-24 19:29 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               ` Albert [this message]
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
2019-09-25 12:49           ` bug#37495: �ظ��� " 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=tencent_F34B40BA5110E75084B094C83952CECFDD06@qq.com \
    --to=georgealbert@qq.com \
    --cc=37495@debbugs.gnu.org \
    --cc=lekktu@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 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).