From: Damien Cassou <damien@cassou.me>
To: sebastien.miquel@posteo.eu
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Need for dedicated kinds of paragraphs
Date: Mon, 17 Oct 2022 20:44:25 +0200 [thread overview]
Message-ID: <87edv61e9i.fsf@cassou.me> (raw)
In-Reply-To: <ab4f30bb-190c-36e9-e3d1-61c0768f22e4@posteo.eu>
Hi all,
thank you very much for your answers:
Sébastien Miquel <sebastien.miquel@posteo.eu> writes:
> I think special blocks are a good fit for this purpose.
"Fraga, Eric" <e.fraga@ucl.ac.uk> writes:
> Have you tried /special blocks/, as in […]
following this idea (also suggested by yantar92 on IRC) I tried this
approach but failed because of:
https://lists.gnu.org/archive/html/emacs-orgmode/2022-10/msg00565.html
I could have introduced several kinds of boxes instead of just one with
parameters but I felt that was a bit heavyweight.
Ihor Radchenko <yantar92@posteo.net> writes:
> Note that #+BOX is not a valid affiliated keyword. Only keywords from
> org-element-affiliated-keywords + #+ATTR_X keywords are considered
> affiliated.
that's also what I understood after reading the code some more.
> Something like
>
> #+ATTR_BACKEND: :style attention
> This text will appear with a red background
Max Nikulin <manikulin@gmail.com> writes:
> If you have derived your export backend from ox-odt then you may use
> something like
>
> #+attr_odt: :type attention
> or perhaps even
> #+attr_linuxmag: :type attention
This is exactly what I finally decided to use.
Thank you very much all of you!
--
Damien Cassou
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
next prev parent reply other threads:[~2022-10-17 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 6:52 Need for dedicated kinds of paragraphs Damien Cassou
2022-10-17 7:25 ` Sébastien Miquel
2022-10-17 18:44 ` Damien Cassou [this message]
2022-10-17 8:16 ` Fraga, Eric
2022-10-17 11:33 ` Ihor Radchenko
2022-10-17 11:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edv61e9i.fsf@cassou.me \
--to=damien@cassou.me \
--cc=emacs-orgmode@gnu.org \
--cc=sebastien.miquel@posteo.eu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.