From: Eijiro Sumii <sumii@ecei.tohoku.ac.jp>
To: eliz@gnu.org
Cc: 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: Fri, 16 Aug 2019 16:33:56 +0900 (JST) [thread overview]
Message-ID: <20190816.163356.2263652830545554088.sumii@ecei.tohoku.ac.jp> (raw)
In-Reply-To: <835zmyqxfz.fsf@gnu.org>
On Fri, Aug 16, 2019 at 12:07 AM Eli Zaretskii <eliz@gnu.org> wrote:
> I think PROBLEMS entries should be short and concise. They should
> tell the reader what is the reason for the problem
For this purpose, I think the first sentence suffices as a minimal
summary, while the details can only be explained via the link.
> and how to fix it
Again I think this is clear from the first sentence (and an explicit
workaround has also been added in the third sentence).
> in a cookbook fashion. Sending the reader to read up a discussion of
> a bug is inconsistent with doing that.
Since the first (and third) sentenc(es) give(s) a cookbook summary,
the details can best be left for the link (at least that was my
intention when I wrote it, which I believe is clear from the explicit
phrase "for details").
> Let's please not forget that
> people who read PROBLEMS are already annoyed by the problem, they are
> not in the mood of reading too much. They need TL;DR, the bottom
> line.
Again I believe the first (and third) sentenc(es) is/are the necessary
and sufficient TL;DR, while the link is needed for people who want to
know the details (at least I would be annoyed if there is only a few
line summary and no more information).
Best,
Eijiro
next prev parent reply other threads:[~2019-08-16 7:33 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 [this message]
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
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=20190816.163356.2263652830545554088.sumii@ecei.tohoku.ac.jp \
--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).