From: npostavs@gmail.com
To: Paul Pogonyshev <pogonyshev@gmx.net>
Cc: 5851@debbugs.gnu.org
Subject: bug#5851: 24.0.50; first character after opening quote often gets eaten in CC modes
Date: Fri, 17 May 2019 13:11:36 -0400 [thread overview]
Message-ID: <851s0xdn07.fsf@gmail.com> (raw)
In-Reply-To: <201102222339.31284.pogonyshev@gmx.net> (Paul Pogonyshev's message of "Tue, 22 Feb 2011 23:39:31 +0200")
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("\bb\210\302 @ A\"\207" [start err signal] 3)
> c-syntactic-re-search-forward("[;{}]" 8510 end)
> c-before-change-check-<>-operators(6462 6462)
> #[(fn) "\b \n\"\207" [fn beg end] 3](c-before-change-check-<>-operators)
> mapc(#[(fn) "\b \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)
next prev parent reply other threads:[~2019-05-17 17:11 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 [this message]
2019-10-06 11:36 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=851s0xdn07.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=5851@debbugs.gnu.org \
--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 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.