unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Multiline Comments
Date: Mon, 9 Nov 2020 16:35:51 +0100	[thread overview]
Message-ID: <trinity-22da9aef-1b1a-4bb6-9975-d32841d78957-1604936151509@3c-app-mailcom-bs07> (raw)
In-Reply-To: <87r1p2mu5b.fsf@fastmail.fm>


> Sent: Monday, November 09, 2020 at 4:23 PM
> From: "Joost Kremers" <joostkremers@fastmail.fm>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Multiline Comments
>
>
> On Mon, Nov 09 2020, Christopher Dimech wrote:
> >> > I would then think you would use a function or a variable?
> >>
> >> Not sure what you mean by that. Use where? For what purpose?
> >
> > To define a variable or a function to avoid some of the problems that occur with multic.
>
> Unfortunately, no. There's simply no way to do what you want. That's why I
> suggested you look at source blocks in Org mode and/or lentic.

Org Source Blocks won't work as the files are Elisp Files for customising Emacs.
Got to look at Lentic, see what's that about.

Many Thanks Joost

> --
> Joost Kremers
> Life has its moments
>
>



  reply	other threads:[~2020-11-09 15:35 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 [this message]
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
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-22da9aef-1b1a-4bb6-9975-d32841d78957-1604936151509@3c-app-mailcom-bs07 \
    --to=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=joostkremers@fastmail.fm \
    /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).