[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: forward-comment and syntax-ppss

From: Dmitry Gutov
Subject: Re: forward-comment and syntax-ppss
Date: Thu, 8 Dec 2016 23:24:12 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Thunderbird/50.0

On 08.12.2016 22:15, Alan Mackenzie wrote:

I propose, additionally, a new buffer local
variable which, if non-nil, will contain a buffer position to use in
place of the "1".

That's functionally equivalent to my proposed patch with syntax-ppss-dont-widen, except for the case where that buffer local value turns out to be higher than POS.

Can parse-partial-sexp parse backwards?

Our primitives `car', `cdr', `list', etc. also don't say
what the intention behind them is; they just work.  Narrowing is what it
is.  Simple and austere.

All the primitives you've enumerated above work on simple values and don't change the buffer state.

Narrowing is anything but austere.

Complexifying narrowing by introducing a
notion of "intention" would surely make it more difficult to use and
possibly foul things up massively.

The reasons for it have been described plenty of times. And no, it will be pretty trivial conceptually.

As I said above, I think syntax-ppss should be retired and replaced by a
function which does parse-partial-sexp starting at 1 rather than

You keep repeating that word (replace), as though that solves anything.

If we introduce the new function and all of Emacs core switches to it, and that function doesn't have an "escape hatch", the multi-mode packages will be hung out to dry.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]