From: Lars Ingebrigtsen <larsi@gnus.org>
To: Glyph Lefkowitz <glyph@twistedmatrix.com>
Cc: 21840@debbugs.gnu.org
Subject: bug#21840: 24.5; semantic analysis of python files is broken by strings that end in backslash
Date: Thu, 03 Dec 2020 11:46:06 +0100 [thread overview]
Message-ID: <875z5jupzl.fsf@gnus.org> (raw)
In-Reply-To: <F9F51B47-4DF3-4AA6-95CF-C15F9DEAE9D7@twistedmatrix.com> (Glyph Lefkowitz's message of "Thu, 5 Nov 2015 18:16:32 -0800")
Glyph Lefkowitz <glyph@twistedmatrix.com> writes:
> Python string literals that end in a backslash cause Semantic's parser
> to halt and not recognize anything further in the buffer. I personally
> ran across this because I frequently use helm-semantic-or-imenu, but can
> be demonstrated equally well by semantic-complete-jump-local or anything
> else that makes use of the buffer's symbol list.
>
> The trivial way to reproduce this is to put the string literal "\\" at
> the top of a Python buffer and then invoke semantic in one of the ways
> just mentioned and notice that nothing is picked up. You can move the
> backslash literal down in the file and see every symbol up to the point
> where it is placed.
(This bug report unfortunately got no response at the time.)
Do you have a step-by-step recipe to reproduce this bug, starting from
"emacs -Q"?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-03 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 2:16 bug#21840: 24.5; semantic analysis of python files is broken by strings that end in backslash Glyph Lefkowitz
2020-12-03 10:46 ` Lars Ingebrigtsen [this message]
2020-12-03 18:48 ` Glyph
2020-12-04 9:54 ` Lars Ingebrigtsen
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=875z5jupzl.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21840@debbugs.gnu.org \
--cc=glyph@twistedmatrix.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.