From: Olivier Certner <ocert.dev@free.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63286@debbugs.gnu.org, Alan Mackenzie <acm@muc.de>
Subject: bug#63286: 30.0.50; CC Mode: New `c-for-clauses-as-arglist' style variable
Date: Sat, 06 May 2023 23:49:52 +0200 [thread overview]
Message-ID: <3052411.uu7Bfa8gCG@ravel> (raw)
In-Reply-To: <83sfcbjryb.fsf@gnu.org>
Hello Eli,
> I don't think I understand the feature you are proposing. Can you
> elaborate, perhaps with examples?
Sure. Please see my reply to Alan.
> This uses @ref incorrectly. The original text also uses it
> incorrectly. Alan, please fix that when you have time: those should
> be @xref, not @ref. The latter is not appropriate at the beginning of
> a sentence.
>
> "for" should be quoted here, to make this sentence more clear.
>
> Defcustoms should have the :version tag.
Indeed. I'm taking note. But all these are minutiae that are less pressing
than more high-level issues that might change the submission significantly, so
I'll wait for the appropriate moment to actually do the changes if there are
still applicable then.
> I don't understand what "argument lists" have to do with 'for'. Or
> maybe I don't understand what you mean by "for clauses".
Then you should definitely read my answer to Alan.
> Finally, would it be possible to have tests for this feature?
Of course. But again, this is not the most pressing issue right now.
Regards.
--
Olivier Certner
next prev parent reply other threads:[~2023-05-06 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 22:19 bug#63286: 30.0.50; CC Mode: New `c-for-clauses-as-arglist' style variable Olivier Certner
2023-05-04 22:22 ` Olivier Certner
2023-05-05 4:57 ` Eli Zaretskii
2023-05-06 21:49 ` Olivier Certner [this message]
2023-05-05 11:14 ` Alan Mackenzie
2023-05-06 21:41 ` Olivier Certner
2023-05-08 15:02 ` Alan Mackenzie
2023-05-09 10:08 ` Olivier Certner
2023-05-09 15:11 ` Alan Mackenzie
2023-05-10 13:20 ` Olivier Certner
2023-05-10 14:26 ` Eli Zaretskii
2023-09-11 18:14 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3052411.uu7Bfa8gCG@ravel \
--to=ocert.dev@free.fr \
--cc=63286@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).