From: "Albert" <georgealbert@qq.com>
To: "Juanma Barranquero" <lekktu@gmail.com>, "Eli Zaretskii" <eliz@gnu.org>
Cc: 37495 <37495@debbugs.gnu.org>
Subject: bug#37495: 回复: bug#37495: 27.0.50; lwindow doesn't pass to system
Date: Thu, 26 Sep 2019 13:38:02 +0800 [thread overview]
Message-ID: <tencent_05031C8C0838CB2240A506CF6772E0EF6009@qq.com> (raw)
In-Reply-To: <tencent_A2E44E3E60D14893532D4253CAE51C322705@qq.com>
[-- Attachment #1.1: Type: text/plain, Size: 1892 bytes --]
I compiled emacs from the latest code. But lwindow is still not passed to windows.
Albert@Albert MSYS /e/workspace/emacs_src/emacs
$ git log
commit 07367e5b95fe31f3d4e994b42b081075501b9b60 (grafted, HEAD -> master, origin/master, origin/HEAD)
Author: Mattias Engdegård <mattiase@acm.org>
Date: Wed Sep 25 14:29:50 2019 -0700
------------------ 原始邮件 ------------------
发件人: "Albert"<georgealbert@qq.com>;
发送时间: 2019年9月25日(星期三) 晚上11:30
收件人: "Juanma Barranquero"<lekktu@gmail.com>;"Eli Zaretskii"<eliz@gnu.org>;
抄送: "37495"<37495@debbugs.gnu.org>;
主题: 回复: bug#37495: 27.0.50; lwindow doesn't pass to system
Picture above is emacs 26.2, it is ok. I can't figure out why emacs 26.3 and 27.0.50 are not ok with the same config of emacs 26.2. Maybe I should trye to compile emacs from source. I use emacs on linux by compiling from trunk. But I don't set up develop environment on windows.
------------------ 原始邮件 ------------------
发件人: "Juanma Barranquero"<lekktu@gmail.com>;
发送时间: 2019年9月25日(星期三) 晚上11:22
收件人: "Eli Zaretskii"<eliz@gnu.org>;
抄送: "Albert"<georgealbert@qq.com>;"37495"<37495@debbugs.gnu.org>;
主题: Re: bug#37495: 27.0.50; lwindow doesn't pass to system
On Wed, Sep 25, 2019 at 5:14 PM Eli Zaretskii <eliz@gnu.org> wrote:
> I see the same, FWIW, and the *Help* window pops up before I hit 'r',
> just after I hit lwindow.
>
> I think this is normal.
Yes, it is normal. But it's not what happens to Albert.
So I think you're right, something in his system's set up is messing with keyboard handling, and it's not an Emacs thing.
But somehow it didn't affect 26.2... Weird.
[-- Attachment #1.2: Type: text/html, Size: 2698 bytes --]
[-- Attachment #2: F2C2AF47@A1867239.BA4E8C5D.jpg --]
[-- Type: image/jpeg, Size: 55856 bytes --]
next prev parent reply other threads:[~2019-09-26 5:38 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
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 ` Albert [this message]
2019-09-26 11:45 ` bug#37495: 回复: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tencent_05031C8C0838CB2240A506CF6772E0EF6009@qq.com \
--to=georgealbert@qq.com \
--cc=37495@debbugs.gnu.org \
--cc=eliz@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 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.