emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Startup option to separate macros arguments with an alternative string
Date: Thu, 22 Apr 2021 14:55:16 +0200	[thread overview]
Message-ID: <87v98e4gy3.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <875z0fzkww.fsf@posteo.net> ("Juan Manuel Macías"'s message of "Wed, 21 Apr 2021 16:01:35 +0000")


Juan Manuel Macías <maciaschain@posteo.net> writes:

> I think it's a very interesting idea. I've made this sketch (at least
> as a proof of concept), what do you think of the approach?

I think there are a few things to fix. For example, the separator may
need to be stored in the properties of the macro. Otherwise,
interpreting data back would return to comma-separated arguments, which
may not be desirable, although correct.

Also, I would limit separator to a single character. You also need to
exclude space characters.

> Example (and code below):
> #+macro: foo (eval (format "%s and %s" $1 $2))
> {{{foo(xxx,zzz\, yyy)}}}
> {{{foo|(xxx|zzz, aaa)}}}
> {{{foo@(xxx@zzz, sss)}}}
> {{{foo|(xxx|zzz\| aaa)}}}
> {{{foo@(xxx@zzz\@ sss)}}}

This change will need to be tested extensively in "test-org-element.el"
and "test-org-macro.el".

However, as a start, I suggest starting a new thread about a suggested
change in the syntax, with a clear title, examples, and code. Then we
can leave time for users to react to it.

Do you want to take care of it?

Nicolas Goaziou

  reply	other threads:[~2021-04-22 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 16:33 [PATCH] Startup option to separate macros arguments with an alternative string Juan Manuel Macías
2021-04-19  9:19 ` Nicolas Goaziou
2021-04-20 13:56   ` Juan Manuel Macías
2021-04-21 16:01   ` Juan Manuel Macías
2021-04-22 12:55     ` Nicolas Goaziou [this message]
2021-04-22 13:46       ` Juan Manuel Macías
2021-04-25  3:46         ` Timothy

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v98e4gy3.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=maciaschain@posteo.net \


* 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


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).