unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Vladimir Nikishkin <lockywolf@gmail.com>
To: Jean Louis <bugs@gnu.support>
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: Wed, 11 Nov 2020 16:18:17 +0800	[thread overview]
Message-ID: <CA+A2iZZFgYYSFwqWaXpT-otn3b+ooEwk4NQpKLLso81JNfptew@mail.gmail.com> (raw)
In-Reply-To: <X6t7OEoPtvYFh6P5@protected.rcdrun.com>

Just to clarify,

I am not asking that exactly the syntax of srfi-62 as it is be added.
(Although Emacs Lisp already uses #'symbol as a reader-syntax switch,
so I suspect that it is possible)
I am asking for _some_ syntax to comment out valid sexps, whichever
fits Emacs Lisp most.

Vlad

On Wed, 11 Nov 2020 at 15:46, Jean Louis <bugs@gnu.support> wrote:
>
> * Richard Stallman <rms@gnu.org> [2020-11-11 08:42]:
> > [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> > [[[ whether defending the US Constitution against all enemies,     ]]]
> > [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> >
> >   > > #| this is
> >   > > a comment |#
> >
> >   > Voting for CL comment blocks.
> >
> > Before deciding to add any syntax to Emacs Lisp, we must make sure
> > that all the Lisp-parsing commands can handle them.
> >
> > If some other Lisp mode handles them already, that suggests it won't
> > be hard; but we have to verify it works in the context of Emacs Lisp
> > mode before making the decision to add that synatx to EMacs Lisp.
>
> Oh, yes! Thank you, it is understandable. In addition it would cause
> many compatibility problems with outside packages and previous
> versions of Emacs.
>


-- 
Yours sincerely, Vladimir Nikishkin
(Sent from GMail web interface.)





  reply	other threads:[~2020-11-11  8: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 [this message]
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

  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=CA+A2iZZFgYYSFwqWaXpT-otn3b+ooEwk4NQpKLLso81JNfptew@mail.gmail.com \
    --to=lockywolf@gmail.com \
    --cc=44554@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    --cc=larsi@gnus.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 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).