From: Maxim Nikulin <firstname.lastname@example.org> To: email@example.com Subject: Re: [PATCH] Possibility of using alternative separators in macros Date: Sun, 16 May 2021 23:48:09 +0700 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 16/05/2021 19:17, Bastien wrote: > > Juan Manuel Macías writes: > >> (On the other hand, maybe better than an alternate separator, some kind of >> warning for unescaped commas might be more useful, as Maxim commented >> here: https://firstname.lastname@example.org/) > > Yes, probably -- feel free to propose a patch for this. Thanks! Such warnings should be property of particular macros. Sometimes ignoring of arguments may be handy. So no patch is required. The trick could be documented somewhere, but I am unsure concerning proper place. Actually, I do not think, fatal error is user-friendly behavior. I am not aware if export already have convenient facilities to report warnings. Currently I do not feel I am ready to implement such feature if it does not exist yet. However the point of that message was that extra commas may be made "transparent" for macros by introducing additional substitution, e.g. "$_" that expands into "rest" arguments. I consider "$@" or "$*" as worse variant since it rather mean "all arguments", so it is less flexible. For "eval" lisp macros, it is just replacing "_" by "$_" in argument list. Simple text macros require a bit more work but it is still comparable with documenting the feature. We need a decision if "rest arguments" feature should be introduced. Once added, it will be harder to discard it due to compatibility issues.
prev parent reply other threads:[~2021-05-16 16:48 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-30 13:26 Juan Manuel Macías 2021-05-01 8:30 ` Bastien 2021-05-01 10:04 ` Nicolas Goaziou 2021-05-01 10:17 ` Bastien 2021-05-01 10:18 ` Bastien 2021-05-01 21:50 ` Juan Manuel Macías 2021-05-02 21:08 ` Christian Moe 2021-05-12 11:49 ` Maxim Nikulin 2021-05-16 19:21 ` Christian Moe 2021-05-17 17:03 ` Maxim Nikulin 2021-05-17 18:51 ` Christian Moe 2021-05-02 12:13 ` Eric S Fraga 2021-05-11 11:01 ` Eric S Fraga 2021-05-11 16:12 ` Juan Manuel Macías [not found] ` <email@example.com> 2021-05-11 18:25 ` Juan Manuel Macías 2021-05-15 13:29 ` Bastien 2021-05-15 20:14 ` Juan Manuel Macías 2021-05-15 20:25 ` Bastien 2021-05-15 21:05 ` Juan Manuel Macías 2021-05-16 12:17 ` Bastien 2021-05-16 16:48 ` Maxim Nikulin [this message]
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://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org' \ --email@example.com \ --firstname.lastname@example.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
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ email@example.com public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git