From: Stefan Kangas <stefan@marxist.se>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Alan Mackenzie <acm@muc.de>, Paul Pogonyshev <pogonyshev@gmx.net>,
5851@debbugs.gnu.org
Subject: bug#5851: 24.0.50; first character after opening quote often gets eaten in CC modes
Date: Sun, 6 Oct 2019 13:36:52 +0200 [thread overview]
Message-ID: <CADwFkmmcYQO=i_Nk7aPA1tqmQDk+8BHGYMosy50tC-L=Sp0w=g@mail.gmail.com> (raw)
In-Reply-To: <201004062321.07973.pogonyshev@gmx.net>
npostavs@gmail.com writes:
> Paul Pogonyshev <pogonyshev@gmx.net> writes:
>
>> FWIW the bug is still present. I get this backtrace (2011-02-19
>> build):
>>
>> (error "Invalid search bound (wrong side of point)")
>> signal(error ("Invalid search bound (wrong side of point)"))
>> byte-code(" b\210\302 @ A\"\207" [start err signal] 3)
>> c-syntactic-re-search-forward("[;{}]" 8510 end)
>> c-before-change-check-<>-operators(6462 6462)
>> #[(fn) " \n\"\207" [fn beg end] 3](c-before-change-check-<>-operators)
>> mapc(#[(fn) " \n\"\207" [fn beg end] 3] (c-extend-region-for-CPP c-before-change-check-<>-operators))
>> c-before-change(6462 6462)
>> self-insert-command(1)
>> call-interactively(self-insert-command nil nil)
>>
>> I cannot find a reliable way to reproduce, but it happens often
>> enough. Apparently, buffers not touched in quite a while are more
>> prone. I.e. open a C++ file and leave it alone for 5 minutes. Then
>> switch to the buffer and type outside any string a double quote
>> following by any other character --- the second character will likely
>> get eaten with an error as above. M-x toggle-debug-on-error helps
>> spotting it.
>
> Maybe this is fixed in master now, along with Bug#28850? (the error
> there is the same, though the backtrace is a bit different)
Indeed, it looks like this has been fixed on master -- or at least I
can't reproduce it. Alan, what do you think?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-10-06 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 20:21 bug#5851: 24.0.50; first character after opening quote often gets eaten in CC modes Paul Pogonyshev
2011-02-22 21:39 ` Paul Pogonyshev
2019-05-17 17:11 ` npostavs
2019-10-06 11:36 ` Stefan Kangas [this message]
2019-11-23 23:42 ` Stefan Kangas
2019-11-25 18:59 ` Alan Mackenzie
2019-11-26 5:09 ` 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='CADwFkmmcYQO=i_Nk7aPA1tqmQDk+8BHGYMosy50tC-L=Sp0w=g@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=5851@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=npostavs@gmail.com \
--cc=pogonyshev@gmx.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).