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 22:16:13 +0800 [thread overview]
Message-ID: <tencent_4EFFF96F4EEDDD40009D5138A75F848D9406@qq.com> (raw)
In-Reply-To: <CAAeL0SQ=REd3dmZZkTaxXZP0LHtj2xvrGJSiRopsQC3X_4xDsQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset="gb18030", Size: 710 bytes --]
C-h k then press lwindow + r, emacs 27.0.50 displays nothing. It seems lwindow is ignored.
------------------ ÔʼÓʼþ ------------------
·¢¼þÈË: "Juanma Barranquero"<lekktu@gmail.com>;
·¢ËÍʱ¼ä: 2019Äê9ÔÂ25ÈÕ(ÐÇÆÚÈý) ÍíÉÏ10:12
ÊÕ¼þÈË: "Albert"<georgealbert@qq.com>;
³ËÍ: "Eli Zaretskii"<eliz@gnu.org>;"37495"<37495@debbugs.gnu.org>;
Ö÷Ìâ: Re: bug#37495: 27.0.50; lwindow doesn't pass to system
On Wed, Sep 25, 2019 at 3:54 PM Albert <georgealbert@qq.com> wrote:
>
> Sorry for the low res pictures. What about this picture?
:-)
So, if you do
C-h k
and then
lwindow r
Emacs says this
[-- Attachment #1.2: Type: text/html, Size: 1354 bytes --]
[-- Attachment #2: 965AB6E7@2150CE72.AD768B5D.jpg --]
[-- Type: image/jpeg, Size: 18388 bytes --]
next prev parent reply other threads:[~2019-09-25 14:16 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 ` Albert [this message]
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_4EFFF96F4EEDDD40009D5138A75F848D9406@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).