emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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, 08 May 2024 12:12:38 +0000	[thread overview]
Message-ID: <8734qssds9.fsf@localhost> (raw)
In-Reply-To: <87jzlgt3hj.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

>> FWIW, I'd be inclined to leave the task for future action, perhaps 
>> changing it to a WAITING keyword with a state-change note explaining the 
>> status (that's what I use in my system, anyway).  But if you disagree, I 
>> won't argue.
> I do not mind. I can also add a link to my email there.

See the updated https://orgmode.org/worg/org-maintenance.html#org2ba9ee1

> I just looked into changing this TODO into inlinetask and that would
> require adding a style for inlinetasks.

Now done. And I converted the maintenance "FIXME" notes to inlinetasks.

> ... While looking, I noticed a
> commented section in worg-editing.org:
> In particular, BeginWarningBox (see
> https://orgmode.org/worg/org-tutorials/images-and-xhtml-export.html)
> might be a basis of inlinetask css.

Exactly what I used.
I also changed these macros to use CSS styles, which automatically
allows properly named special blocks.
See https://orgmode.org/worg/worg-editing.html#org366cb9a
and https://orgmode.org/worg/org-tutorials/images-and-xhtml-export.html
for examples of the new info/warning box styles.

> Also, the above macros may be one existing way to provide highlighting
> we discussed earlier.

See how I implemented highlighting in

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>

      parent reply	other threads:[~2024-05-08 12:12 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
2024-05-08 12:12         ` Ihor Radchenko [this message]

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:

  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=8734qssds9.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=adam@alphapapa.net \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).