From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 57907-done@debbugs.gnu.org
Subject: bug#57907: 29.0.50; Using keywords with cl-loop
Date: Mon, 19 Sep 2022 14:52:44 +0200 [thread overview]
Message-ID: <87r107ttk3.fsf@gnus.org> (raw)
In-Reply-To: <874jx3fz3k.fsf@posteo.net> (Philip Kaludercic's message of "Mon, 19 Sep 2022 10:16:47 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> While it might have had been an accident initially, I don't think it has
> to be considered such. As I said, there are reasons like syntax
> highlighting for preferring keyword-symbols. But if you don't think
> this is a good idea, I'll go ahead and close the issue.
I think we could probably get better syntax highlighting without
keywords if somebody took that on.
My general lack of enthusiasm for this is that this offers syntactical
variation without any practical advantages either way. This means that
some people will choose one syntax, and others will choose the other,
and we get code churn when people "correct" the code from one to
another.
next prev parent reply other threads:[~2022-09-19 12:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 12:03 bug#57907: 29.0.50; Using keywords with cl-loop Philip Kaludercic
2022-09-18 12:20 ` Lars Ingebrigtsen
2022-09-18 12:28 ` Philip Kaludercic
2022-09-18 12:37 ` Lars Ingebrigtsen
2022-09-18 12:46 ` Philip Kaludercic
2022-09-19 8:06 ` Lars Ingebrigtsen
2022-09-19 10:16 ` Philip Kaludercic
2022-09-19 12:52 ` Lars Ingebrigtsen [this message]
[not found] ` <handler.57907.B.166350264228653.ack@debbugs.gnu.org>
2022-09-18 12:26 ` bug#57907: Acknowledgement (29.0.50; Using keywords with cl-loop) Philip Kaludercic
2022-09-18 20:12 ` Philip Kaludercic
2022-09-18 12:38 ` bug#57907: 29.0.50; Using keywords with cl-loop Gerd Möllmann
2022-09-18 12:52 ` Philip Kaludercic
2022-09-18 13:01 ` Gerd Möllmann
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=87r107ttk3.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57907-done@debbugs.gnu.org \
--cc=philipk@posteo.net \
/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).