From: Vladimir Nikishkin <lockywolf@gmail.com>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Richard Stallman <rms@gnu.org>,
44554@debbugs.gnu.org
Subject: bug#44554: 27.1; Feature request: SRFI-62 style comments for Emacs Lisp.
Date: Thu, 12 Nov 2020 00:14:00 +0800 [thread overview]
Message-ID: <CA+A2iZYWqv+EC4HAtpwkw2t9RY81erzyAWM4RkhMZta3y00TxA@mail.gmail.com> (raw)
In-Reply-To: <4282B0B6-7580-4066-9BAD-369EAD238E2C@acm.org>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
Well, if your parsers and fontifiers recognize #'symbol constructions,
wouldn't they recognise #; in almost the same way?
--
Yours sincerely, Vladimir Nikishkin
(Sent with Google mail mobile.)
Mattias Engdegård <mattiase@acm.org> 于 2020年11月12日周四 00:11写道：
> mark-sexp (C-M-SPC) followed by comment-region already works, doesn't it?
> Not obvious that SRFI-62 comments would be substantially better.
>
> I would very much like not having to update code that parses, lexes,
> searches, matches, pretty-prints, fontifies, navigates in, browses, indexes
> or otherwise recognises elisp surface syntax, that I have written over the
> years in various places -- at least not without a really good reason.
> Likely I'm not alone.
>
> Sorry about the downbeat tone! I really don't mind syntax improvements,
> but here it seems unclear that the benefits would outweigh the costs.
>
>
[-- Attachment #2: Type: text/html, Size: 1237 bytes --]
next prev parent reply other threads:[~2020-11-11 16:14 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
2020-11-11 16:10 ` Mattias Engdegård
2020-11-11 16:14 ` Vladimir Nikishkin [this message]
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=CA+A2iZYWqv+EC4HAtpwkw2t9RY81erzyAWM4RkhMZta3y00TxA@mail.gmail.com \
--to=lockywolf@gmail.com \
--cc=44554@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=rms@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.