From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: contovob@tcd.ie, 40573@debbugs.gnu.org, juri@linkov.net,
monnier@iro.umontreal.ca, dgutov@yandex.ru
Subject: bug#40573: 27.0.90; flymake-mode broken in scratch buffer
Date: Mon, 20 Apr 2020 16:41:29 +0300 [thread overview]
Message-ID: <835zdui8ae.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm528bU=BhiLoAaNexKeE6FbBbDK=zW+X-Wd1-Yax2v95ig@mail.gmail.com> (message from João Távora on Sun, 19 Apr 2020 21:17:47 +0100)
> From: João Távora <joaotavora@gmail.com>
> Date: Sun, 19 Apr 2020 21:17:47 +0100
> Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, Stefan Monnier <monnier@iro.umontreal.ca>,
> Juri Linkov <juri@linkov.net>, 40573@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
>
> The new mode should be called out in NEWS, yes.
>
> Do you suggest any starting suggestion fpr phrasing?
Just that there's this new mode, and what files will (or should) turn
it on.
> I ask because you frequently find flaws in my
> English.
You make it sound like fixing the wording or changing it is some kind
of sin that you need to apologize. It isn't: I frequently find
phrases or wording in the documentation that could be improved, and
when I do, I fix them. Others fix what I wrote when they find similar
opportunities. This is routine, and says nothing bad about you or
your English. No one can excel in everything they do, and there's no
need to apologize or feel victimized when someone improves some text
you wrote.
> Please don't make this backward-incompatible change. Let's keep the
> API of this function unchanged.
>
> OK. See the latest commit.
LGTM, thanks.
next prev parent reply other threads:[~2020-04-20 13:41 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 13:18 bug#40573: 27.0.90; flymake-mode broken in scratch buffer João Távora
2020-04-12 13:48 ` Eli Zaretskii
2020-04-12 14:24 ` João Távora
2020-04-12 14:44 ` Eli Zaretskii
2020-04-12 17:02 ` João Távora
2020-04-12 17:17 ` Eli Zaretskii
2020-04-12 17:50 ` João Távora
2020-04-12 23:58 ` Juri Linkov
2020-04-13 4:36 ` Eli Zaretskii
2020-04-13 23:17 ` Juri Linkov
2020-04-14 5:51 ` Eli Zaretskii
2020-04-14 8:48 ` João Távora
2020-04-14 11:29 ` Eli Zaretskii
2020-04-14 11:48 ` João Távora
2020-04-14 12:38 ` Eli Zaretskii
2020-04-14 12:56 ` João Távora
2020-04-14 15:42 ` Eli Zaretskii
2020-04-14 16:42 ` João Távora
2020-04-14 20:05 ` Stefan Monnier
2020-04-16 21:43 ` Juri Linkov
2020-04-16 23:06 ` Stefan Monnier
2020-04-17 6:49 ` Eli Zaretskii
2020-04-17 10:07 ` João Távora
2020-04-17 10:12 ` Eli Zaretskii
2020-04-17 10:21 ` João Távora
2020-04-17 11:49 ` Eli Zaretskii
2020-04-17 11:57 ` João Távora
2020-04-17 13:05 ` Eli Zaretskii
2020-04-17 15:20 ` João Távora
2020-04-17 15:28 ` Eli Zaretskii
2020-04-17 15:35 ` João Távora
2020-04-17 15:46 ` Eli Zaretskii
2020-04-17 15:55 ` João Távora
2020-04-17 17:19 ` Eli Zaretskii
2020-04-18 8:26 ` João Távora
2020-04-18 9:28 ` Eli Zaretskii
2020-04-18 10:03 ` João Távora
2020-04-18 11:08 ` Eli Zaretskii
2020-04-18 11:57 ` João Távora
2020-04-18 12:35 ` Eli Zaretskii
2020-04-18 15:10 ` João Távora
2020-04-18 23:36 ` João Távora
2020-04-19 0:05 ` Dmitry Gutov
2020-04-19 9:25 ` João Távora
2020-04-19 13:57 ` Dmitry Gutov
2020-04-19 16:31 ` João Távora
2020-04-19 16:38 ` Dmitry Gutov
2020-04-19 2:44 ` Stefan Monnier
2020-04-19 14:01 ` Eli Zaretskii
2020-04-19 20:17 ` João Távora
2020-04-20 13:41 ` Eli Zaretskii [this message]
2020-04-20 14:02 ` João Távora
2020-04-20 16:05 ` Eli Zaretskii
2020-05-01 11:10 ` João Távora
2020-04-18 11:55 ` Basil L. Contovounesios
2020-04-18 12:03 ` João Távora
2020-04-19 0:20 ` Basil L. Contovounesios
2020-04-19 11:41 ` João Távora
2020-04-18 23:42 ` Juri Linkov
2020-04-19 9:16 ` João Távora
2020-04-17 14:44 ` Basil L. Contovounesios
2020-04-17 16:04 ` Stefan Monnier
2020-04-17 6:23 ` Eli Zaretskii
2020-04-18 23:36 ` Juri Linkov
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=835zdui8ae.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40573@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=dgutov@yandex.ru \
--cc=joaotavora@gmail.com \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
/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.