GNU bug report logs -
#22983
syntax-ppss returns wrong result.
Previous Next
Reported by: Alan Mackenzie <acm <at> muc.de>
Date: Fri, 11 Mar 2016 15:13:02 UTC
Severity: normal
Done: Alan Mackenzie <acm <at> muc.de>
Bug is archived. No further changes may be made.
Full log
Message #32 received at 22983 <at> debbugs.gnu.org (full text, mbox):
Hello, Stefan.
On Sun, Mar 13, 2016 at 01:37:27PM -0400, Stefan Monnier wrote:
> >> But it's not the semantics these .el files get. What's probably keeping
> >> them functional is the rarity with which buffers are narrowed to an
> >> "awkward" point-min.
> > Another thing that keeps it together, is that narrowing, as a user-level
> > operator, is not that popular.
> Luckily, yes.
I happen to use it frequently. I expect other users do, to. It's
useful.
> > Personally, I consider it an anti-feature.
> Same here. Luckily also, as pointed out elsewhere, the semantics of it
> is unclear, so that in several important cases, whichever behavior we
> end up choosing will be both correct for some users and incorrect
> for others.
That's pure sophistry. The semantics needed are quite clear: What were
strings and comments before narrowing should remain strings and comments
after narrowing. Otherwise, nothing would work in such a narrowed
buffer. font-locking, for example, behaves properly in a narrowed
buffer.
> Hence, so far, I didn't make any effort to try and "do the right thing"
> for user-activated narrowing, since these are just not well defined
> enough to even determine what is "the right thing".
Lets define them as I said in the previous paragraph. Or can you
conceive of a use case where one would want narrowing to invert strings
and non-strings, leaving comments totally random?
Do you have any views on how the bug should be resolved?
> Stefan
--
Alan Mackenzie (Nuremberg, Germany).
This bug report was last modified 7 years and 229 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.