all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	Vladimir Nikishkin <lockywolf@gmail.com>,
	44554@debbugs.gnu.org
Subject: bug#44554: 27.1; Feature request: SRFI-62 style comments for Emacs Lisp.
Date: Fri, 13 Nov 2020 18:32:17 +0000	[thread overview]
Message-ID: <CALDnm504spgzbT7-4t-V8Hw40Tw7RnWBbqh5_ZJNNoDEWb3S3A@mail.gmail.com> (raw)
In-Reply-To: <6184e820-23e1-4324-807f-6f8a5feaa26c@default>

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On Tue, Nov 10, 2020, 17:22 Drew Adams <drew.adams@oracle.com> wrote:

> > I wonder whether comment blocks would be even more useful
> > (if we have to prioritise):
> >
> > #| this is
> > a comment |#
> >
> > The advantage is that you don't have to have syntactically valid things
> > in comment blocks, while #; requires that you do.  #; also looks like
> > slightly hard to read if you do stuff like
> >
> > (foo #;(foobar
> >         ...
> >         1)
> >      zot)
>
> +1 for Common-Lisp block comments.
>

+1. Let's not stray away from existing solutions.

(And for reader macros, FWIW...)
>

+2 Yep, just make a programmable reader.

Even without such a thing, reader conditionals are just what's requested
here.

João

>

[-- Attachment #2: Type: text/html, Size: 1711 bytes --]

  reply	other threads:[~2020-11-13 18:32 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 [this message]
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
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=CALDnm504spgzbT7-4t-V8Hw40Tw7RnWBbqh5_ZJNNoDEWb3S3A@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=44554@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.org \
    --cc=lockywolf@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.