From: "Juan Manuel Macías" <maciaschain@posteo.net> To: Nicolas Goaziou <mail@nicolasgoaziou.fr> Cc: orgmode <emacs-orgmode@gnu.org> Subject: Re: [PATCH] Startup option to separate macros arguments with an alternative string Date: Tue, 20 Apr 2021 13:56:55 +0000 [thread overview] Message-ID: <87v98hqct4.fsf@posteo.net> (raw) In-Reply-To: <87o8ead42u.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 19 Apr 2021 11:19:21 +0200") Hi Nicolas Nicolas Goaziou writes: > Even though Org syntax partly is, I don't think parameterizable syntax > is a way to go. I'd rather have less variables controlling it. (I'm > looking at you `org-list-allow-alphabetical', and > `org-plain-list-ordered-item-terminator'.) Thanks for your explanations. I understand that the use of variables here is perhaps not the happiest solution. Naturally, I speak of 'solution' assuming there is a 'problem', the choice of the comma as an argument separator; but I also assume that what is a problem for me, it doesn't have to be for other users, as here everything is subjective. Anyway, I couldn't think of another way to respect the original comma (and backward compatibility), but leaving the user some freedom to choose a different separator. I also understand that implementing that can lead to confusion. >> Rationale for this patch: There are many contexts where the comma character can be >> inappropriate as an argument separator, since it has to be escaped >> many times. > > That's true. But I wonder if you're hitting a limit of replacement > macros use case. IMO, macros are good for short text. For bigger ones, > you may want to use some Babel code, in the language of your choice. > WDYT? I think replacement macros have huge potential, that I often explore in my daily work and (I admit) wearing the things to the limit, which means struggling with resistance to the material ;-) Perhaps that emerging potential was not originally foreseen ... Of course, the scenario is always in short texts, I agree. But even in those scenarios, the comma as an argument separator is somewhat uncomfortable and confusing. That is, macros have great potential (IMHO) in contrast to an "ugly" syntax. But at this point it has a difficult solution... A typical use case for macros (for me) can be to export to LaTeX with the command \foreignlanguage{lang}{short text} in multilingual documents (see this screenshot: https://gnutas.juanmanuelmacias.com/images/macros-sample.png). I can't think of another way to do (easily) something like that (with the plus of being able to evaluate some Elisp in there and add a conditional for the backend, etc.). Best regards, Juan Manuel
next prev parent reply other threads:[~2021-04-20 13:57 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-18 16:33 Juan Manuel Macías 2021-04-19 9:19 ` Nicolas Goaziou 2021-04-20 13:56 ` Juan Manuel Macías [this message] 2021-04-21 16:01 ` Juan Manuel Macías 2021-04-22 12:55 ` Nicolas Goaziou 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: 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=87v98hqct4.fsf@posteo.net \ --to=maciaschain@posteo.net \ --cc=emacs-orgmode@gnu.org \ --cc=mail@nicolasgoaziou.fr \ --subject='Re: [PATCH] Startup option to separate macros arguments with an alternative string' \ /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
Code repositories for project(s) associated with this 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).