From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: 44554@debbugs.gnu.org
Subject: bug#44554: 27.1; Feature request: SRFI-62 style comments for Emacs Lisp.
Date: Tue, 10 Nov 2020 23:18:39 +0000 [thread overview]
Message-ID: <87blg4ztps.fsf@gnus.jao.io> (raw)
In-Reply-To: <87sg9hwbo8.fsf@delllaptop.lockywolf.net>
since people are voting, here's my +1 for sexp (#;) comments. i've been
programming in languages that have them almost daily for the last ten
years, and find them invaluable, and better than block comments.
for me, their main advantages are that i commonly have my point at the
beginning of the sexp and don't need to move around to comment it out,
and that they can nest very easily (by that i mean that #;#; would
comment out the next 2 sexps, and so on).
sexp comments also combine nicely with the fact that most of my
movements over lispy code are sexp-based, and help me not commenting out
by mistake closing parens.
in the much fewer occasions i need a block comment, it's normally easy
to use comment-region, and packages like paredit help there.
(of course if we end up having only block comments, it's trivial writing
an emacs command commenting out the next n sexps using them (or, heck,
even /not/ using them) so i'm fine either way at the end of the day.)
cheers,
jao
--
And what should they know of England who only England know? - Kipling
next prev parent reply other threads:[~2020-11-10 23:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 14:04 bug#44554: 27.1; Feature request: SRFI-62 style comments for Emacs Lisp Vladimir Nikishkin
2020-11-10 14:57 ` Lars Ingebrigtsen
2020-11-10 15:11 ` Vladimir Nikishkin
2020-11-10 17:17 ` Drew Adams
2020-11-13 18:32 ` João Távora
2020-11-10 19:31 ` Jean Louis
2020-11-11 5:40 ` Richard Stallman
2020-11-11 5:48 ` Jean Louis
2020-11-11 8:18 ` Vladimir Nikishkin
2020-11-11 8:25 ` Jean Louis
2020-11-11 14:18 ` Vladimir Nikishkin
2020-11-12 23:55 ` Eduardo Ochs
2020-11-11 8:29 ` Andreas Schwab
2020-11-11 22:50 ` Jose A. Ortega Ruiz
2020-11-10 17:17 ` Francesco Potortì
2020-11-10 23:18 ` Jose A. Ortega Ruiz [this message]
2020-11-11 16:10 ` Mattias Engdegård
2020-11-11 16:14 ` Vladimir Nikishkin
2020-11-11 16:25 ` Mattias Engdegård
2020-11-12 12:50 ` Lars Ingebrigtsen
2020-11-12 18:16 ` Drew Adams
2020-11-12 20:11 ` Juri Linkov
2020-11-12 20:44 ` Drew Adams
2020-11-13 0:38 ` Stefan Kangas
2020-11-13 13:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-13 13:47 ` Stefan Kangas
2020-11-13 14:07 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-13 21:03 ` Tassilo Horn
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=87blg4ztps.fsf@gnus.jao.io \
--to=jao@gnu.org \
--cc=44554@debbugs.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 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.