From: Ihor Radchenko <yantar92@posteo.net>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org, Bastien <bzg@gnu.org>
Subject: Re: [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements
Date: Wed, 03 Apr 2024 12:18:37 +0000 [thread overview]
Message-ID: <878r1uprky.fsf@localhost> (raw)
In-Reply-To: <0f35e14b-1961-4e62-b9ba-b1161e67afad@alphapapa.net>
Adam Porter <adam@alphapapa.net> writes:
> 1. Having to use separate BEGIN and END macros is less convenient than
> more Lispy constructs, like a macro call with a string argument. But I
> guess, to wrap Org elements, like a TODO heading or inline task, it
> would be necessary. A macro call with the text as an argument wouldn't
> be a task in Org syntax, which would make it less useful outside of
> rendered HTML.
Not for inlinetasks. For everything but heading, we can actually use
special blocks.
For headings, there is also :HTML_HEADLINE_CLASS property.
> 2. Those macros, or one much like them, could be useful for the use
> case of centering text to stand out, as discussed in the other thread.
Yes, but they are currently rather plain (other than having an image):
.org-info-box {
clear:both;
margin-left:auto;
margin-right:auto;
padding:0.7em;
}
.org-info-box img {
float:left;
margin:0em 0.5em 0em 0em;
}
.org-info-box p {
margin:0em;
padding:0em;
}
Wondering if we should add some background.
> 3. For cases that don't potentially involve wrapping Org elements,
> having a simple macro with the text as its argument might be preferable
> to having separate BEGIN and END macros. I wonder if we could have
> non-begin-end equivalents of the begin-and-end macros listed there.
.org-info-box is certainly not suitable for inline highlights.
Do we need such highlights though? Isn't the classic
italic/bold/underline enough?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-04-03 12:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 12:35 [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements Ihor Radchenko
2024-03-24 17:55 ` Bastien Guerry
2024-03-24 18:26 ` Ihor Radchenko
2024-03-25 8:17 ` Bastien Guerry
2024-03-25 14:17 ` Adam Porter
2024-03-26 14:59 ` Ihor Radchenko
2024-03-27 3:23 ` Adam Porter
2024-03-28 12:01 ` Ihor Radchenko
2024-03-28 12:49 ` Adam Porter
2024-03-28 13:11 ` Ihor Radchenko
2024-03-29 18:17 ` Bastien Guerry
2024-03-30 11:08 ` Ihor Radchenko
2024-03-31 15:46 ` Adam Porter
2024-04-02 11:20 ` Ihor Radchenko
2024-04-02 23:01 ` Adam Porter
2024-04-03 0:39 ` Samuel Wales
2024-04-03 12:20 ` Ihor Radchenko
2024-04-03 12:18 ` Ihor Radchenko [this message]
2024-05-08 12:12 ` Ihor Radchenko
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=878r1uprky.fsf@localhost \
--to=yantar92@posteo.net \
--cc=adam@alphapapa.net \
--cc=bzg@gnu.org \
--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 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.