From: Max Nikulin <manikulin@gmail.com>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: inline-special-block: export rules
Date: Tue, 26 Mar 2024 23:56:01 +0700 [thread overview]
Message-ID: <4a731b41-c587-4b87-a2d8-ee2b0b2ff392@gmail.com> (raw)
In-Reply-To: <877chvvq1b.fsf_-_@posteo.net>
On 21/03/2024 17:26, Juan Manuel Macías wrote:
> Max Nikulin writes:
>
>> I am afraid that :export will cause confusion with :exports for source
>> code blocks. Its name differs by just "s" but possible values have
>> nothing common.
>
> I agree. At the moment two alternative names come to mind: :backends or
> :export-rules
I find :export-rules too abstract. Unless a better name is proposed, I
prefer :backends.
> :export [or whatever new name we give it] ==> normal behavior, overwrites the values
> :export+ ==> adds the new values to the values defined in the alias
Vim for options allowing list of values has several options
:set opt=value1,value2 " assign new value
:set opt+=value " add to list
:set opt-=value " remove from list if it is there
:set opt& " reset to default value
I am unsure whether all variants should be implemented.
> This syntax could also be extended to other cases. Perhaps we want
> attributes like :prelatex, :postlatex, or :html to support accumulating
> values.
Certainly :export (:backends) is not the only property that should
accumulate values.
next prev parent reply other threads:[~2024-03-26 16:56 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 20:34 Experimental public branch for inline special blocks Juan Manuel Macías
2024-03-02 8:29 ` Stefan Nobis
2024-03-02 10:57 ` Juan Manuel Macías
2024-03-03 20:29 ` Juan Manuel Macías
2024-03-10 2:08 ` `:export' attribute?: " Juan Manuel Macías
2024-03-10 13:54 ` Juan Manuel Macías
2024-03-11 10:27 ` Max Nikulin
2024-03-11 13:59 ` Juan Manuel Macías
2024-03-11 17:01 ` Max Nikulin
2024-03-11 20:19 ` Juan Manuel Macías
2024-03-12 8:32 ` Stefan Nobis
2024-03-12 13:45 ` Juan Manuel Macías
2024-03-12 16:20 ` Max Nikulin
2024-03-12 17:41 ` Juan Manuel Macías
2024-03-13 16:08 ` Max Nikulin
2024-03-13 16:48 ` Juan Manuel Macías
2024-03-13 17:16 ` Juan Manuel Macías
2024-03-15 2:19 ` Juan Manuel Macías
2024-03-15 10:52 ` Max Nikulin
2024-03-15 13:10 ` Juan Manuel Macías
2024-03-15 17:21 ` Max Nikulin
2024-03-15 14:00 ` Ihor Radchenko
2024-03-15 11:11 ` Max Nikulin
2024-03-15 14:19 ` Ihor Radchenko
2024-03-15 16:26 ` Juan Manuel Macías
2024-03-16 14:07 ` Max Nikulin
2024-03-18 19:42 ` Juan Manuel Macías
2024-03-19 14:54 ` Max Nikulin
2024-03-19 17:47 ` Juan Manuel Macías
2024-03-21 10:26 ` inline-special-block: export rules (was: `:export' attribute?: Re: Experimental public branch for inline special blocks) Juan Manuel Macías
2024-03-26 16:56 ` Max Nikulin [this message]
2024-03-04 17:13 ` naming: Re: Experimental public branch for inline special blocks Max Nikulin
2024-03-04 17:29 ` Ihor Radchenko
2024-03-04 17:49 ` Juan Manuel Macías
2024-03-05 10:53 ` Max Nikulin
2024-03-05 11:04 ` Ihor Radchenko
2024-03-05 15:16 ` Suhail Singh
2024-03-05 15:23 ` Suhail Singh
2024-03-05 15:16 ` Juan Manuel Macías
2024-03-06 10:42 ` Max Nikulin
2024-03-06 10:56 ` Ihor Radchenko
2024-03-07 10:34 ` Max Nikulin
2024-03-07 14:12 ` Ihor Radchenko
2024-03-08 5:26 ` Samuel Wales
2024-03-08 16:32 ` Max Nikulin
2024-03-08 16:41 ` Ihor Radchenko
2024-03-04 18:07 ` Juan Manuel Macías
2024-03-04 22:17 ` Samuel Wales
2024-03-04 22:18 ` Samuel Wales
2024-03-05 16:47 ` smallcaps: " Max Nikulin
2024-03-05 17:28 ` Juan Manuel Macías
2024-03-06 10:55 ` Max Nikulin
2024-03-06 15:21 ` Juan Manuel Macías
2024-03-06 16:53 ` To avoid zero width space: " Max Nikulin
2024-03-06 18:27 ` Juan Manuel Macías
2024-03-06 21:13 ` Juan Manuel Macías
2024-03-07 10:57 ` false positives: " Max Nikulin
2024-03-07 11:06 ` Juan Manuel Macías
2024-03-07 11:18 ` Ihor Radchenko
2024-03-07 11:19 ` Juan Manuel Macías
2024-03-07 15:53 ` Juan Manuel Macías
2024-03-07 16:09 ` Ihor Radchenko
2024-03-07 16:57 ` Juan Manuel Macías
2024-03-07 18:21 ` Juan Manuel Macías
2024-03-08 13:58 ` Max Nikulin
2024-03-08 15:44 ` Juan Manuel Macías
2024-03-08 16:04 ` Max Nikulin
2024-03-08 16:15 ` Ihor Radchenko
2024-03-08 18:44 ` Juan Manuel Macías
2024-03-08 18:57 ` Juan Manuel Macías
2024-03-09 11:10 ` Max Nikulin
2024-03-09 11:48 ` Juan Manuel Macías
2024-03-09 15:24 ` Juan Manuel Macías
2024-03-10 7:11 ` Max Nikulin
2024-04-09 8:52 ` Ihor Radchenko
2024-04-09 10:51 ` Max Nikulin
2024-04-09 14:05 ` Ihor Radchenko
2024-04-10 23:00 ` Juan Manuel Macías
2024-04-11 12:26 ` Ihor Radchenko
2024-04-11 13:47 ` Juan Manuel Macías
2024-07-18 6:55 ` Ihor Radchenko
2024-07-18 21:04 ` Juan Manuel Macías
2024-07-19 13:06 ` Ihor Radchenko
2024-04-14 15:59 ` Attributes on images (was:: Experimental public branch for inline special blocks) Rick Lupton
2024-04-14 19:26 ` Ihor Radchenko
2024-04-11 11:06 ` Experimental public branch for inline special blocks Max Nikulin
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=4a731b41-c587-4b87-a2d8-ee2b0b2ff392@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
/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).