emacs-devel
[Top][All Lists]
Advanced

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

Re: [ELPA] New package: arm-mode


From: Stefan Monnier
Subject: Re: [ELPA] New package: arm-mode
Date: Tue, 20 Aug 2019 04:55:14 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

> In Arm "@" is equivilent to ";" in lisp, and "/* */" is equivilent to ";;" in 
> lisp.
> I don't understand how comment-dwim knows to put ";;" when on an empty line
> and only ";" for in-line comments but I'm looking for a similar
> functionality. This how I got it to work for me.

Oh, you mean you want comment-dwim to use @-comments for "end of line
comments", but to use /*...*/-comments for whole-line comments?

The ;-vs-;; difference is obtained via the `comment-add` variable, but
indeed it doesn't cover your use case.

Could you `M-x report-emacs-bug` to request this as a new feature?
[ And please send me the resulting bug-number.  ]


        Stefan


> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Monday, August 19, 2019 3:53 PM, Stefan Monnier <address@hidden> wrote:
>
>> > Thank you for the code review Stefan. I have implemented most of the
>> > fixed you suggested. Following is what I have a few questions about.
>> > I need that M-; key binding because a /* */ style comment should be
>> > inserted if on an empty line. To my understanding comment-dwim would
>> > only insert @ style comments.
>>
>> Hmm... comment-dwim doesn't care, AFAIK, it just inserts whatever you
>> have set for comment-start and comment-end, so it can definitely insert
>> /.../. But I suspect you know that, so most likely I'm
>> misunderstanding something.
>>
>> > The reason that (modify-syntax-entry ?_ "w" st) is there is actually define
>> > a help define what a word is for the \< and \> regexp. If it is left out
>> > then registers names or anything else used in labels will be highlighted in
>> > their own color.
>>
>> Ah, I see. You can probably solve this by using \< and \> which match
>> symbol-boundaries instead of word-boundaries.
>>
>> Stefan




reply via email to

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