From: Alan Mackenzie <acm@muc.de>
To: Ergus <spacibba@aol.com>
Cc: 36423-done@debbugs.gnu.org
Subject: bug#36423: 27.0.50; electric-pair-mode not working properly depending of file content.
Date: Mon, 8 Jul 2019 10:29:22 +0000 [thread overview]
Message-ID: <20190708102922.GA25404@ACM> (raw)
In-Reply-To: <20190708094801.GC4529@ACM>
Hello again, Ergus.
On Mon, Jul 08, 2019 at 09:48:01 +0000, Alan Mackenzie wrote:
> On Wed, Jul 03, 2019 at 21:32:00 +0200, Ergus wrote:
> > Hi Alan:
> > Sorry for the bother again. After the fix you did, the "" issue is
> > better, but now there are new issues with the {} when I use pragmas for
> > example.
> OK, thanks! I've corrected a further problem with " in
> electric-pair-mode, and I'm taking the liberty of closing your bug. ;-)
> > I attached you a picture (because this is the easier way to explain it)
> This is actually a different bug. If you haven't done so already, could
> you please raise this as a bug in its own right. Thanks.
Actually, there's no need for this, I understand what's happening now
and it's "not a bug" - sort of.
In the lines:
1. printf ("Hello
2. world");
, there is an invalid string on L1, extending from " to the end of the
line. There is also an invalid string on L2, starting at the ", which
encloses the ). Thus this ), being inside a string, can't match the (
on L1.
Sorry I hadn't realised this half an hour ago.
Due to insistent complaints, I'm looking at modifying this "invalid
string" mechanism so that although it would fontify as it does now, it
would allow things like these two parentheses to match up.
[ .... ]
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2019-07-08 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 19:01 bug#36423: 27.0.50; electric-pair-mode not working properly depending of file content Ergus
2019-07-02 13:36 ` Alan Mackenzie
2019-07-03 19:32 ` Ergus
2019-07-04 14:14 ` Alan Mackenzie
2019-07-08 9:48 ` Alan Mackenzie
2019-07-08 10:29 ` Alan Mackenzie [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190708102922.GA25404@ACM \
--to=acm@muc.de \
--cc=36423-done@debbugs.gnu.org \
--cc=spacibba@aol.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 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.