From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: 59251@debbugs.gnu.org, theo@thornhill.no
Subject: bug#59251: Acknowledgement (29.0.50; Fix-some-inconsistencies-in-ts-modes)
Date: Mon, 14 Nov 2022 21:02:39 +0200 [thread overview]
Message-ID: <8335aljr5c.fsf@gnu.org> (raw)
In-Reply-To: <6C5721BF-2FA2-45A4-A970-483D662A6414@gmail.com> (message from Yuan Fu on Sun, 13 Nov 2022 16:51:52 -0800)
> Cc: 59251@debbugs.gnu.org
> From: Yuan Fu <casouri@gmail.com>
> Date: Sun, 13 Nov 2022 16:51:52 -0800
>
> + (setq-local comment-style c-ts-mode-comment-style)
>
> Why don’t we let users set comment style themselves? Does cc-mode have a similar variable?
It's a minor mode there, see "C-c C-k" (c-toggle-comment-style).
next prev parent reply other threads:[~2022-11-14 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 20:42 bug#59251: 29.0.50; Fix-some-inconsistencies-in-ts-modes Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <handler.59251.B.16683721605982.ack@debbugs.gnu.org>
2022-11-13 22:16 ` bug#59251: Acknowledgement (29.0.50; Fix-some-inconsistencies-in-ts-modes) Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-13 23:01 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-14 0:51 ` Yuan Fu
2022-11-14 7:06 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-14 9:25 ` Yuan Fu
2022-11-15 12:22 ` Eli Zaretskii
2022-11-15 14:22 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-14 19:02 ` Eli Zaretskii [this message]
2022-11-14 18:59 ` bug#59251: 29.0.50; Fix-some-inconsistencies-in-ts-modes Eli Zaretskii
2022-11-14 19:12 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=8335aljr5c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59251@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=theo@thornhill.no \
/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.