From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@Nexgo.DE>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ox-publish] handling of white space in arguments of macros, named arguments?
Date: Thu, 28 Mar 2013 17:22:27 +0100 [thread overview]
Message-ID: <87ehezxzng.fsf@gmail.com> (raw)
In-Reply-To: <kj0pnd$r9s$1@ger.gmane.org> (Achim Gratz's message of "Thu, 28 Mar 2013 07:59:38 +0100")
Hello,
Achim Gratz <Stromeko@Nexgo.DE> writes:
> Am 27.03.2013 17:26, schrieb Nicolas Goaziou:
>> I think all newline characters should be replaced with a whitespace
>> character in macro arguments. Indeed, macro templates are only one line
>> long but unwanted "\n" could be inserted by paragraph filling in
>> arguments.
>
> I'm not sure about that, it would mean that there'd need to be
> additional syntax to insert linebreaks.
My point is that macro templates have to fit in a single line, no
newline character allowed. As a consequence, macro arguments are
implicitly expected to fit in a single line. So a newline character in
an argument is probably wrong.
>> I also don't mind trimming arguments again, provided this is added as an
>> explicit behaviour and there is no opposition to it.
>
> How about making trimming explicit during the expansion of macro
> arguments? It seems that there are a few possibilities of what
> trimming could mean, so this would be an opportunity to allow them all
> (n is the argument number):
>
> $:n - remove whitespace and linebreaks before argument
> $.n - remove whitespace and linebreaks after argument
> $n - same as $:.n
> $+n - replace whitespace and linebreaks inside arguments
> with a single space
> $*n - same as $:+.n
> $~n - literal argument (no trimming)
The current trend for macros is to be really simple so that advanced
(and not-so advanced) tasks are done with Babel instead. IOW, macros are
only useful if they are simpler than the simplest form of Babel usage.
In every other case, Babel is a superior choice.
Your suggestion is interesting, but I think it would go backwards wrt
this.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-03-28 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 20:08 [ox-publish] handling of white space in arguments of macros, named arguments? Stefan Vollmar
2013-03-27 16:26 ` Nicolas Goaziou
2013-03-28 6:59 ` Achim Gratz
2013-03-28 16:22 ` Nicolas Goaziou [this message]
2013-03-28 17:44 ` Achim Gratz
2013-03-28 9:18 ` Stefan Vollmar
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ehezxzng.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=Stromeko@Nexgo.DE \
--cc=emacs-orgmode@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/org-mode.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).