parse-partial-sexp parses only Lisp?

parse-partial-sexp parses only Lisp?

[Lennart Borgman (gmail)]

The first line of the doc string says so.

Re: parse-partial-sexp parses only Lisp?

[martin rudalics]

 > The first line of the doc string says so.

`parse-partial-sexp' only happens to work correctly in many other modes
hence I think that line is good.  However, the doc string should mention
the "9th element" of the parse state and the fact that element 8 is
significant in STATE.  Finally, the term "character address" should be
replaced by "character position".

Re: parse-partial-sexp parses only Lisp?

[Lennart Borgman (gmail)]

martin rudalics wrote:
>  > The first line of the doc string says so.
> 
> `parse-partial-sexp' only happens to work correctly in many other modes
> hence I think that line is good.  However, the doc string should mention
> the "9th element" of the parse state and the fact that element 8 is
> significant in STATE.  Finally, the term "character address" should be
> replaced by "character position".

Thanks Martin. Some more things that I would like to know (from the doc 
string in the future):

- What variables are used when searching for comments?
- What do I have to put in OLDSTATE to make it parse comments and 
strings correctly? - assuming that I know about previous comments and 
strings and if FROM is inside a comment or string.

Re: parse-partial-sexp parses only Lisp?

[martin rudalics]

 > - What variables are used when searching for comments?

I don't understand: `parse-partial-sexp' uses the syntax-table to
identify start and end sequences of comments and strings.  Sometimes
syntax-table text-properties are used.  What kind of "variables" do you
have in mind?

 > - What do I have to put in OLDSTATE to make it parse comments and
 > strings correctly? - assuming that I know about previous comments and
 > strings and if FROM is inside a comment or string.

You know about previous comments and strings iff you are neither in a
comment nor in a string.  Strings and comments can be nested in so many
forms that it's strongly encouraged to either use the state returned by
a previous call of `parse-partial-sexp' or assure that you start outside
of any comments or strings.  `syntax-begin-function' if provided is a
good choice here.

Re: parse-partial-sexp parses only Lisp?

[Lennart Borgman (gmail)]

martin rudalics wrote:
 >  > - What variables are used when searching for comments?
 >
 > I don't understand: `parse-partial-sexp' uses the syntax-table to
 > identify start and end sequences of comments and strings.  Sometimes
 > syntax-table text-properties are used.  What kind of "variables" do you
 > have in mind?

syntax-table? Is that the syntax table returned by (syntax-table) and 
set by (set-syntax-table TABLE)? The doc string does not mention this.

I thought that perhaps the comment delimiters where involved. The syntax 
tables as above seems to be able to take care of C style comments (max 2 
chars in delimeters), but it can not handle html comments AFAICS.

I guess then parse-partial-sexp can not return info about html comments, 
right? Can syntax-pps do that? (The doc string for syntax-ppss says the 
return values are the same as for parse-partial-sexp.)

 >  > - What do I have to put in OLDSTATE to make it parse comments and
 >  > strings correctly? - assuming that I know about previous comments and
 >  > strings and if FROM is inside a comment or string.
 >
 > You know about previous comments and strings iff you are neither in a
 > comment nor in a string.  Strings and comments can be nested in so many
 > forms that it's strongly encouraged to either use the state returned by
 > a previous call of `parse-partial-sexp' or assure that you start outside
 > of any comments or strings.  `syntax-begin-function' if provided is a
 > good choice here.

Thanks.

Re: parse-partial-sexp parses only Lisp?

[David Hansen]

On Wed, 02 Apr 2008 19:58:18 +0200 Lennart Borgman wrote:

> I thought that perhaps the comment delimiters where involved. The
> syntax tables as above seems to be able to take care of C style
> comments (max 2 chars in delimeters), but it can not handle html
> comments AFAICS.
>
> I guess then parse-partial-sexp can not return info about html
> comments, right? Can syntax-pps do that? (The doc string for
> syntax-ppss says the return values are the same as for
> parse-partial-sexp.)

You can use `font-lock-syntactic-keywords' and
`parse-sexp-lookup-properties'.

BTW, in some source file I read that font-lock-syntactic-keywords should
be made independent of font-lock.  Is there anything planned in this
direction?

I think syntax-ppss does the same as parse-partial-sexp except that it
automatically caches a state.

David

Re: parse-partial-sexp parses only Lisp?

[Stefan Monnier]

>> > The first line of the doc string says so.
>> 
>> `parse-partial-sexp' only happens to work correctly in many other modes
>> hence I think that line is good.  However, the doc string should mention
>> the "9th element" of the parse state and the fact that element 8 is
>> significant in STATE.  Finally, the term "character address" should be
>> replaced by "character position".

> Thanks Martin. Some more things that I would like to know (from the doc
> string in the future):

> - What variables are used when searching for comments?
> - What do I have to put in OLDSTATE to make it parse comments and strings
> correctly? - assuming that I know about previous comments and strings and if
> FROM is inside a comment or string.

The description of the output is also the description of OLDSTATE.


        Stefan

Re: parse-partial-sexp parses only Lisp?

[Lennart Borgman (gmail)]

Stefan Monnier wrote:
>>>> The first line of the doc string says so.
>>> `parse-partial-sexp' only happens to work correctly in many other modes
>>> hence I think that line is good.  However, the doc string should mention
>>> the "9th element" of the parse state and the fact that element 8 is
>>> significant in STATE.  Finally, the term "character address" should be
>>> replaced by "character position".
> 
>> Thanks Martin. Some more things that I would like to know (from the doc
>> string in the future):
> 
>> - What variables are used when searching for comments?
>> - What do I have to put in OLDSTATE to make it parse comments and strings
>> correctly? - assuming that I know about previous comments and strings and if
>> FROM is inside a comment or string.
> 
> The description of the output is also the description of OLDSTATE.


Ok, thanks.