From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Multiline Comments
Date: Mon, 9 Nov 2020 13:14:56 +0100 [thread overview]
Message-ID: <trinity-b4e04c1a-6104-4957-96f3-f3b00dc9bb70-1604924095668@3c-app-mailcom-bs13> (raw)
In-Reply-To: <87zh3qu9g0.fsf@web.de>
> Sent: Monday, November 09, 2020 at 11:10 AM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Multiline Comments
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > Have included the following macro for writing multiline comments
> >
> > (defmacro multic (&rest _) nil)
> >
> >
> > But the thing complains when writing
> >
> > (multic
> >
> > #+STARTUP: content
> > * Adds Directories to load-path and the Melpa Package Archives)
>
> Yes indeed, such a macro will only allow to "comment" `read'able
> symbolic Elisp expressions.
>
> Even then it has another downside: even though the arguments are
> ignored, the macro expression will still be evaluated and return
> something (nil), so it may change the semantics of a surrounding form.
>
> Why do you want to avoid commenting with ";" btw?
Because I want to pass the file through Org-Mode and Rec-Utils, which
require Org and Rec Commands to start at the beginning of the line.
My workaround has been to include the commands within Double Quotes.
(multic "
#+STARTUP: content
* Adds Directories to load-path and the Melpa Package Archives")
But it would help if we can think of an improvement to multic, thus
looking for ideas I can try.
>
> Regards,
>
> Michael.
>
>
>
next prev parent reply other threads:[~2020-11-09 12:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 20:47 Multiline Comments Christopher Dimech
2020-11-09 9:28 ` Jean Louis
2020-11-09 13:01 ` Michael Heerdegen
2020-11-09 13:18 ` Christopher Dimech
2020-11-09 13:33 ` Joost Kremers
2020-11-09 13:55 ` Christopher Dimech
2020-11-09 14:37 ` Joost Kremers
2020-11-09 15:08 ` Christopher Dimech
2020-11-09 15:23 ` Joost Kremers
2020-11-09 15:35 ` Christopher Dimech
2020-11-09 19:01 ` Joost Kremers
2020-11-10 0:13 ` Robert Thorpe
2020-11-10 0:36 ` Joost Kremers
2020-11-09 17:51 ` Christopher Dimech
2020-11-09 10:10 ` Michael Heerdegen
2020-11-09 12:14 ` Christopher Dimech [this message]
2020-11-09 13:29 ` Joost Kremers
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=trinity-b4e04c1a-6104-4957-96f3-f3b00dc9bb70-1604924095668@3c-app-mailcom-bs13 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).