From: Lars Ingebrigtsen <larsi@gnus.org>
To: Christophe TROESTLER <Christophe.TROESTLER@umons.ac.be>
Cc: 38545@debbugs.gnu.org
Subject: bug#38545: 26.1; comment-multi-line doesn't work in c-mode
Date: Fri, 30 Oct 2020 16:33:01 +0100 [thread overview]
Message-ID: <87v9erenki.fsf@gnus.org> (raw)
In-Reply-To: <87pngxadkv.fsf@poincare.umons.ac.be> (Christophe TROESTLER's message of "Mon, 9 Dec 2019 12:27:45 +0000")
Christophe TROESTLER <Christophe.TROESTLER@umons.ac.be> writes:
> Setting comment-multi-line to `t', commenting a region should “inserts no new terminator or starter.” However, it is not the case. For example, selecting two lines in
>
> int main()
> {
> int a;
> int b;
> return(0);
> }
>
> /* Local Variables: */
> /* comment-style: multi-line */
> /* comment-multi-line: t */
> /* End: */
>
> yields
>
> /* int a;
> * int b; */
>
> while it should be
>
> /* int a;
> int b; */
I've stared at that for a while, and I can't see that comment-region has
inserted a new "terminator or starter". It's inserted a "*" at the
start of the second line, but that's neither of those things.
So I think it's behaving as documented?
However, poking around for two minutes doesn't reveal any obvious way to
get c-mode to stop behaving like this; for instance, setting
comment-continue to something else than what it is just makes it create
single-line comments, confusingly enough.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-30 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 12:27 bug#38545: 26.1; comment-multi-line doesn't work Christophe TROESTLER
2020-10-30 15:33 ` Lars Ingebrigtsen [this message]
2020-10-30 16:17 ` Andreas Schwab
2021-08-22 21:28 ` bug#38545: comment-multi-line doesn't work in c-mode Christophe Troestler
2021-08-25 9:04 ` Christophe Troestler
2021-08-25 11:12 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9erenki.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=38545@debbugs.gnu.org \
--cc=Christophe.TROESTLER@umons.ac.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.