From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: "João Távora" <joaotavora@gmail.com>,
"Dima Kogan" <dima@secretsauce.net>,
35254@debbugs.gnu.org, "Noam Postavsky" <npostavs@gmail.com>
Subject: bug#35254: 27.0.50; cc-mode/electric-pair-mode/electric-layout-mode: bad trailing whitespace behavior in cc-mode
Date: Tue, 14 May 2019 09:27:35 +0000 [thread overview]
Message-ID: <20190514092735.GB4231__10924.7567526594$1557826217$gmane$org@ACM> (raw)
In-Reply-To: <jwvimue9bzj.fsf-monnier+emacs@gnu.org>
Hello, Stefan.
On Mon, May 13, 2019 at 19:32:49 -0400, Stefan Monnier wrote:
> >> Electric indent mode's post-self-insert hook entry has 3 effects:
> >> 1. Indent the previous line.
> >> 2. Remove trailing whitespace from the previous line.
> >> 3. Indent the current line (when at beginning of line).
> Note that `newline` itself already does some subset of 2 (before running
> electric-indent's post-self-insert hook).
> > I interpret the problem a little differently.
> > electric-indent-post-self-insert-function, when electric-indent-inhibit
> > is set, is inhibiting actions which are not really part of electric
> > indentation, in particular action 2 (above). This is the heart of the
> > bug. The following patch fixes the bug. It would need tidying up before
> > being committed:
> I haven't followed enough of the discussion to understand why that might
> cause a bug.
The bug is, type lots of <CR>s in a row; the indentation WS isn't
getting removed from the blank lines. Currently electric-indent-inhibit
is inhibiting this removal.
> > diff --git a/lisp/electric.el b/lisp/electric.el
> > index 07da2f1d9e..15a42930c1 100644
> > --- a/lisp/electric.el
> > +++ b/lisp/electric.el
> > @@ -282,9 +282,15 @@ electric-indent-post-self-insert-function
> > (condition-case-unless-debug ()
> > (indent-according-to-mode)
> > (error (throw 'indent-error nil)))
> > - ;; The goal here will be to remove the trailing
> > - ;; whitespace after reindentation of the previous line
> > - ;; because that may have (re)introduced it.
> > + )
> > + (unless (memq indent-line-function
> > + electric-indent-functions-without-reindent)
> > + ;; The goal here will be to remove the indentation
> > + ;; whitespace from an otherwise blank line after
> > + ;; typing <CR> twice in succession. Also to remove
> > + ;; trailing whitespace after reindentation of the
> > + ;; previous line because that may have
> > + ;; (re)introduced it.
> > (goto-char before)
> > ;; We were at EOL in marker `before' before the call
> > ;; to `indent-according-to-mode' but after we may
> I don't understand why you distinguish
> electric-indent-inhibit
> from
> (memq indent-line-function
> electric-indent-functions-without-reindent)
It was quite late when I worked out the patch. I just did it
mechanically, to get the discussion moving.
> When I introduced these, electric-indent-functions-without-reindent was
> only meant to paper over those pre-existing cases that don't set
> electric-indent-inhibit.
> So, I'd suggest an even simpler patch which just closes the `unless`
> earlier. Would that work?
Probably. Maybe João should check this, once he's fully back with us.
> Stefan
> diff --git a/lisp/electric.el b/lisp/electric.el
> index 07da2f1d9e..beb3348755 100644
> --- a/lisp/electric.el
> +++ b/lisp/electric.el
> @@ -281,7 +281,7 @@ electric-indent-post-self-insert-function
> (goto-char before)
> (condition-case-unless-debug ()
> (indent-according-to-mode)
> - (error (throw 'indent-error nil)))
> + (error (throw 'indent-error nil))))
> ;; The goal here will be to remove the trailing
> ;; whitespace after reindentation of the previous line
> ;; because that may have (re)introduced it.
> @@ -290,7 +290,7 @@ electric-indent-post-self-insert-function
> ;; to `indent-according-to-mode' but after we may
> ;; not be (Bug#15767).
> (when (and (eolp))
> - (delete-horizontal-space t))))))
> + (delete-horizontal-space t)))))
> (unless (and electric-indent-inhibit
> (not at-newline))
> (condition-case-unless-debug ()
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-05-14 9:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 6:32 bug#35254: 27.0.50; cc-mode/electric-pair-mode/electric-layout-mode: bad trailing whitespace behavior in cc-mode Dima Kogan
2019-05-11 3:12 ` Noam Postavsky
2019-05-11 12:05 ` Alan Mackenzie
[not found] ` <20190511120524.GA15991@ACM>
2019-05-11 14:06 ` Noam Postavsky
2019-05-11 16:19 ` Alan Mackenzie
2019-05-11 19:34 ` Basil L. Contovounesios
2019-05-12 16:14 ` Alan Mackenzie
2019-05-12 21:45 ` Basil L. Contovounesios
2019-05-13 10:14 ` Alan Mackenzie
[not found] ` <20190513101448.GA5525@ACM>
2019-05-13 12:49 ` Basil L. Contovounesios
2019-05-12 15:12 ` Alan Mackenzie
2019-05-12 18:42 ` Noam Postavsky
2019-05-13 19:53 ` Alan Mackenzie
[not found] ` <20190513195323.GB5525@ACM>
2019-05-13 22:39 ` João Távora
2019-05-13 23:38 ` Noam Postavsky
2019-05-14 1:20 ` João Távora
2019-05-14 1:28 ` Stefan Monnier
2019-05-14 1:56 ` Noam Postavsky
2019-05-14 8:38 ` Alan Mackenzie
2019-05-13 23:32 ` Stefan Monnier
[not found] ` <jwvimue9bzj.fsf-monnier+emacs@gnu.org>
2019-05-13 23:45 ` Noam Postavsky
2019-05-14 1:26 ` Stefan Monnier
2019-05-14 9:27 ` Alan Mackenzie [this message]
2019-05-14 9:34 ` Alan Mackenzie
[not found] ` <20190514092735.GB4231@ACM>
2019-05-14 10:34 ` João Távora
2019-05-15 10:03 ` Alan Mackenzie
2019-05-15 11:27 ` João Távora
2019-05-15 13:19 ` Stefan Monnier
2019-05-15 13:55 ` João Távora
2019-05-15 14:03 ` João Távora
2019-07-01 12:24 ` João Távora
2019-07-01 13:34 ` Alan Mackenzie
[not found] ` <20190701133427.GA23312@ACM>
2019-07-06 16:24 ` Noam Postavsky
2019-07-06 22:24 ` João Távora
2019-07-06 22:50 ` Noam Postavsky
2019-07-06 22:33 ` João Távora
[not found] ` <20190514093415.GC4231@ACM>
2019-05-14 15:38 ` Stefan Monnier
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='20190514092735.GB4231__10924.7567526594$1557826217$gmane$org@ACM' \
--to=acm@muc.de \
--cc=35254@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--cc=joaotavora@gmail.com \
--cc=monnier@IRO.UMontreal.CA \
--cc=npostavs@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).