From: Adam Porter <adam@alphapapa.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org, Bastien <bzg@gnu.org>
Subject: Re: [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements
Date: Tue, 2 Apr 2024 18:01:32 -0500 [thread overview]
Message-ID: <0f35e14b-1961-4e62-b9ba-b1161e67afad@alphapapa.net> (raw)
In-Reply-To: <87jzlgt3hj.fsf@localhost>
On 4/2/24 06:20, Ihor Radchenko wrote:
> I just looked into changing this TODO into inlinetask and that would
> require adding a style for inlinetasks. While looking, I noticed a
> commented section in worg-editing.org:
>
> ...
>
> Also, the above macros may we one existing way to provide
> highlighting we discussed earlier.
>
> WDYT?
A few thoughts:
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.
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.
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.
--Adam
next prev parent reply other threads:[~2024-04-02 23:07 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 [this message]
2024-04-03 0:39 ` Samuel Wales
2024-04-03 12:20 ` Ihor Radchenko
2024-04-03 12:18 ` Ihor Radchenko
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
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=0f35e14b-1961-4e62-b9ba-b1161e67afad@alphapapa.net \
--to=adam@alphapapa.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).