From: "João Távora" <joaotavora@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 34294@debbugs.gnu.org
Subject: bug#34294: 27.0.50; flymake-start-on-save-buffer has no effect
Date: Wed, 8 May 2019 00:10:11 +0100 [thread overview]
Message-ID: <CALDnm50LBqGPHqTscGL32CgopHzFkynaP7teqamVMw5sVzHs4Q@mail.gmail.com> (raw)
In-Reply-To: <874l66t3dd.fsf@mail.linkov.net>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Tue, May 7, 2019 at 9:30 PM Juri Linkov <juri@linkov.net> wrote:
> >> Anyway, your initiative got my attention. Do you remember what I
> >> wrote previously?
> >>
> >>> [jt] I would even go as far as obsoleting the variable entirely, and
> >>> use make-obsolete-variable instead: there's no real reason
> >>> why newline should be given special treatment. And users
> >>> that need this for some obscure reason can probably plug it
> >>> in post-self-insert-hook.
> >>
> >>> If you obsolete the variable, you can remove it from the
> >>> manual, too.
> >>
> >> I still think this is the best option, so if you didn't already push
> that,
> >> I would be thankful that you do. It should solve your issue and make
> >> the code and manual simpler.
> >
> > I had doubts about removing it, but since you are sure about this,
> > then please see the following patch attached. If basically this is ok,
> > I'll also change the manual, NEWS, etc.
>
> Now the variable is obsoleted in master.
>
The patch is fine (but did you push it already?). I have a minor grammar
nit (you should connect both variables with "and" when you mention them
in comments and docstrings).
Also the manual and NEWS entries are missing. Don't forget about those.
And thanks, of course :-)
João
[-- Attachment #2: Type: text/html, Size: 1858 bytes --]
prev parent reply other threads:[~2019-05-07 23:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 21:30 bug#34294: 27.0.50; flymake-start-on-save-buffer has no effect Juri Linkov
2019-02-02 22:40 ` João Távora
2019-02-03 20:42 ` Juri Linkov
2019-02-03 22:10 ` João Távora
2019-02-04 21:24 ` Juri Linkov
2019-02-04 22:41 ` João Távora
2019-02-17 20:11 ` Juri Linkov
2019-03-18 21:10 ` Juri Linkov
2019-03-18 21:43 ` João Távora
2019-03-19 20:46 ` Juri Linkov
2019-03-27 21:38 ` Juri Linkov
2019-04-17 20:29 ` Juri Linkov
2019-04-18 11:36 ` João Távora
2019-04-18 20:42 ` Juri Linkov
2019-04-19 6:35 ` Eli Zaretskii
2019-04-24 20:25 ` Juri Linkov
2019-04-25 5:46 ` Eli Zaretskii
2019-04-25 8:07 ` martin rudalics
2019-04-29 20:15 ` Juri Linkov
2019-05-01 8:29 ` martin rudalics
2019-05-01 21:10 ` Juri Linkov
2019-05-04 17:34 ` martin rudalics
2019-05-04 21:16 ` Juri Linkov
2019-05-05 9:04 ` martin rudalics
2019-05-05 22:46 ` Richard Stallman
2019-05-05 23:09 ` João Távora
2019-05-05 20:08 ` Juri Linkov
2019-05-05 23:02 ` João Távora
2019-05-06 20:15 ` Juri Linkov
2019-05-07 20:29 ` Juri Linkov
2019-05-07 23:10 ` João Távora [this message]
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=CALDnm50LBqGPHqTscGL32CgopHzFkynaP7teqamVMw5sVzHs4Q@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=34294@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).