From: Eijiro Sumii <sumii@ecei.tohoku.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Eijiro Sumii <sumii@ecei.tohoku.ac.jp>, 36779@debbugs.gnu.org
Subject: bug#36779: 25.1; mouse click not recognized for frames with large left position
Date: Sat, 17 Aug 2019 06:09:54 +0900 [thread overview]
Message-ID: <CAB0_Sias91A37ooeuEMG-fmebgoECVMXiudBvuHVL4_NGK2Kvg@mail.gmail.com> (raw)
In-Reply-To: <83y2ztnqw9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
> > As I wrote a few times, the reason why the problem seems to happen
> > only to Emacs is still unknown, and I presume some readers would be
> > eager to understand the (rather complex) situation, for which they
> > have to read the gdb logs and watch the movie. I don't think there is
> > any way to explain them in "a few lines".
>
> An entry in PROBLEMS doesn't need to explain all the internal details,
> just what software causes it and how to work around it.
In our case "what software causes it" (Emacs or the X server) is not clear,
and the "workaround" is quite unsatisfactory (having to restart the entire
X system - the server and all the clients). That's why some readers would
need the link to the details. (At least I would be rather frustrated if
the file only tells the problem without information for such details!)
[-- Attachment #2: Type: text/html, Size: 1166 bytes --]
next prev parent reply other threads:[~2019-08-16 21:09 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 4:18 bug#36779: 25.1; mouse click not recognized for frames with large left position Eijiro Sumii
2019-07-24 14:29 ` Eli Zaretskii
2019-07-25 4:32 ` Eijiro Sumii
2019-07-25 12:49 ` Eli Zaretskii
2019-07-25 14:13 ` Eijiro Sumii
2019-07-27 1:05 ` Eijiro Sumii
2019-07-27 6:52 ` martin rudalics
2019-07-29 9:20 ` Eijiro Sumii
2019-07-29 15:16 ` martin rudalics
2019-07-30 4:30 ` Eijiro Sumii
2019-07-30 7:01 ` martin rudalics
2019-07-30 12:01 ` Eijiro Sumii
2019-07-30 14:45 ` Eli Zaretskii
2019-07-30 15:21 ` Robert Pluim
2019-07-30 21:27 ` Eijiro Sumii
2019-08-01 1:27 ` Eijiro Sumii
2019-07-31 9:12 ` martin rudalics
2019-07-31 9:38 ` Eijiro Sumii
2019-08-07 3:07 ` Eijiro Sumii
2019-08-07 12:04 ` martin rudalics
2019-08-13 9:09 ` Eijiro Sumii
2019-08-13 14:26 ` Eli Zaretskii
2019-08-14 2:11 ` Eijiro Sumii
2019-08-14 8:59 ` martin rudalics
2019-08-14 10:01 ` Eijiro Sumii
2019-08-15 8:11 ` martin rudalics
2019-08-15 15:07 ` Eli Zaretskii
2019-08-16 7:33 ` Eijiro Sumii
2019-08-16 8:20 ` Eli Zaretskii
2019-08-16 8:43 ` Eijiro Sumii
2019-08-16 12:49 ` Eli Zaretskii
2019-08-16 13:03 ` Eijiro Sumii
2019-08-16 14:09 ` Eli Zaretskii
2019-08-16 21:09 ` Eijiro Sumii [this message]
2019-08-17 6:23 ` Eli Zaretskii
2019-08-17 7:37 ` Eijiro Sumii
2020-08-26 0:15 ` Stefan Kangas
2020-08-26 6:10 ` Eli Zaretskii
2020-08-26 6:19 ` Eijiro Sumii
2020-08-26 6:35 ` Eli Zaretskii
2020-08-26 7:40 ` Eijiro Sumii
2020-08-26 8:00 ` Eli Zaretskii
2020-08-27 9:36 ` Stefan Kangas
2020-08-27 9:45 ` Eli Zaretskii
2020-08-27 10:08 ` Stefan Kangas
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=CAB0_Sias91A37ooeuEMG-fmebgoECVMXiudBvuHVL4_NGK2Kvg@mail.gmail.com \
--to=sumii@ecei.tohoku.ac.jp \
--cc=36779@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).