Re: outrageous comment syntax

Re: outrageous comment syntax

[Stefan Monnier]

> comment-start-skip's value is 
> "\\(\\(^\\|[^\\\\\n]\\)\\(\\\\\\\\\\)*\\);+ *"
> Local in buffer simple-haskell.el; global value is nil

> Documentation:
> *Regexp to match the start of a comment plus everything up to its body.
> If there are any \(...\) pairs, the comment delimiter text is held to begin
> at the place matched by the close of the first pair.

> However, I have a language with two comment syntaxes, one of which
> depends on leading context and the other doesn't.  How in the world can
> I set this variable properly?  The context must be within the first
> group, and it cannot be :-(

I guess you can't.  Unless of course some concrete detail makes it possible,
but since you haven't provided any...

If you indeed can't, report it with M-x report-emacs-bug, of course,


        Stefan

Re: outrageous comment syntax

[rgb]

Ian Zimmerman wrote:
> comment-start-skip's value is
> "\\(\\(^\\|[^\\\\\n]\\)\\(\\\\\\\\\\)*\\);+ *"
> Local in buffer simple-haskell.el; global value is nil
>
> Documentation:
> *Regexp to match the start of a comment plus everything up to its body.
> If there are any \(...\) pairs, the comment delimiter text is held to begin
> at the place matched by the close of the first pair.
>
>
> However, I have a language with two comment syntaxes, one of which
> depends on leading context and the other doesn't.  How in the world can
> I set this variable properly?  The context must be within the first
> group, and it cannot be :-(

When you san "cannot be" I assume you mean that use of shy groups
(?: ...) is insufficient to your needs?

I suggested a generalized fix for problems such as this a couple
months ago.  I'm not sure how to tell if it was dismissed, or if it's
in some state of analysis or even implementation.

Basically it involved a seemingly simple change to regexp primatives
to accept symbols as well as strings.  Accepting a symbol was a
compromise to my original suggestion of allowing functions to be
passed which apparently introduces problems.

The idea is to make regexp handling work more like font-lock.  With
font-lock routines, anywhere a regexp is legal you can pass a function
which is expected to behave like re-search...  When I say `behave
like' I mean in the way it leaves point, returns t or nil depending on
success and setting of match-data.

This would give everyone with problems such as this the ability to
simply code a custom solution without having to hack up an otherwise
useful package that simply needs search results to do it's job.

Re: outrageous comment syntax

[Ian Zimmerman]

rgb wrote:
> Ian Zimmerman wrote:
> 
>>comment-start-skip's value is
>>"\\(\\(^\\|[^\\\\\n]\\)\\(\\\\\\\\\\)*\\);+ *"
>>Local in buffer simple-haskell.el; global value is nil
>>
>>Documentation:
>>*Regexp to match the start of a comment plus everything up to its body.
>>If there are any \(...\) pairs, the comment delimiter text is held to begin
>>at the place matched by the close of the first pair.
>>
>>
>>However, I have a language with two comment syntaxes, one of which
>>depends on leading context and the other doesn't.  How in the world can
>>I set this variable properly?  The context must be within the first
>>group, and it cannot be :-(
> 
> 
> When you san "cannot be" I assume you mean that use of shy groups
> (?: ...) is insufficient to your needs?
> 

I didn't know Emacs had them.  Thanks for pointing them out to me.

Re: outrageous comment syntax

[Stefan Monnier]

>> comment-start-skip's value is
>> "\\(\\(^\\|[^\\\\\n]\\)\\(\\\\\\\\\\)*\\);+ *"
>> Local in buffer simple-haskell.el; global value is nil
>> 
>> Documentation:
>> *Regexp to match the start of a comment plus everything up to its body.
>> If there are any \(...\) pairs, the comment delimiter text is held to begin
>> at the place matched by the close of the first pair.
>> 
>> 
>> However, I have a language with two comment syntaxes, one of which
>> depends on leading context and the other doesn't.  How in the world can
>> I set this variable properly?  The context must be within the first
>> group, and it cannot be :-(

Since you haven't provided any hard data, I'll give you a sample solution to
another problem:

   (set (make-local-variable 'comment-start-skip)
        "#+[ \t]*\\|\\(uglyprefix +\\)--+[ \t]*")

Now maybe you problem can't be solved in the same way, of course.
The group-1 convention doesn't cover all cases.


        Stefan

outrageous comment syntax

[Ian Zimmerman]

comment-start-skip's value is 
"\\(\\(^\\|[^\\\\\n]\\)\\(\\\\\\\\\\)*\\);+ *"
Local in buffer simple-haskell.el; global value is nil

Documentation:
*Regexp to match the start of a comment plus everything up to its body.
If there are any \(...\) pairs, the comment delimiter text is held to begin
at the place matched by the close of the first pair.


However, I have a language with two comment syntaxes, one of which
depends on leading context and the other doesn't.  How in the world can
I set this variable properly?  The context must be within the first
group, and it cannot be :-(

You can actually guess the language, it's not completely obscure.
Prize: a virtual wine.

-- 
"It's not true or not."  A reality show producer (real quote)