From: Eli Zaretskii <eliz@gnu.org>
To: Vincenzo Pupillo <v.pupillo@gmail.com>
Cc: casouri@gmail.com, 72814-done@debbugs.gnu.org, 72814@debbugs.gnu.org
Subject: bug#72814: 31.0.50; Add a variable controlling doxygen support in C/C++/Java?
Date: Sat, 21 Sep 2024 12:43:40 +0300 [thread overview]
Message-ID: <86ikup4a0j.fsf@gnu.org> (raw)
In-Reply-To: <26625715.1r3eYUQgxm@fedora> (message from Vincenzo Pupillo on Sat, 14 Sep 2024 19:26:07 +0200)
> From: Vincenzo Pupillo <v.pupillo@gmail.com>
> Cc: bug-gnu-emacs@gnu.org, 72814@debbugs.gnu.org
> Date: Sat, 14 Sep 2024 19:26:07 +0200
>
> > > Another idea: use tertiary value for c-ts-mode-enable-doxygen, t for
> > > enable (and issue warning if doxygen isn’t present), nil for enable if
> > > doxygen exists but don’t issue any warning, ‘disabled for disable. (I
> > > don’t think there’s a convention for the three values of tertiary toggle,
> > > is that right Eli?)
> > That could also be OK, but I prefer something that does TRT by
> > default.
>
> Ciao,
> in this new version of the patch, as default, the *-ts-mode-enable-doxygen are
> set to nil, and issue a diagnostic (one per session) when Not-nil and if the
> grammar isn't present. It is OK?
Thanks, installed on master, and closing the bug.
next prev parent reply other threads:[~2024-09-21 9:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D6CB8DB6-0D4A-496D-8EFF-4C03BFCC6858@gmail.com>
2024-08-27 3:13 ` bug#72814: 31.0.50; Add a variable controlling doxygen support in C/C++/Java? Yuan Fu
2024-08-27 7:36 ` Vincenzo Pupillo
2024-08-27 12:22 ` Eli Zaretskii
2024-09-09 9:50 ` Vincenzo Pupillo
2024-09-11 4:53 ` Yuan Fu
2024-09-11 9:40 ` Vincenzo Pupillo
2024-09-11 12:05 ` Eli Zaretskii
2024-09-12 7:51 ` Yuan Fu
2024-09-12 8:31 ` Eli Zaretskii
2024-09-14 17:26 ` Vincenzo Pupillo
2024-09-21 9:43 ` Eli Zaretskii [this message]
2024-09-22 6:45 ` Yuan Fu
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=86ikup4a0j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72814-done@debbugs.gnu.org \
--cc=72814@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=v.pupillo@gmail.com \
/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.