From: Bastien Guerry <bzg@gnu.org>
To: Tim Cross <theophilusx@gmail.com>
Cc: Ihor Radchenko <yantar92@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] worg-setup.org is outdated
Date: Mon, 13 Jun 2022 16:21:04 +0200 [thread overview]
Message-ID: <8735g8pru7.fsf@gnu.org> (raw)
In-Reply-To: <87leu1un4h.fsf@gmail.com> (Tim Cross's message of "Mon, 13 Jun 2022 15:44:38 +1000")
Hi Tim,
Tim Cross <theophilusx@gmail.com> writes:
> A 'refresh' of the look probably isn't a bad thing. However, getting it
> right and consistent is likely non-trivial. Not sure if my css skills
> are up to it, but willing to have a look at it anyway.
Thanks in advance for looking into this!
--
Bastien
next prev parent reply other threads:[~2022-06-13 14:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 21:51 [accessibility] worg obscures text Samuel Wales
2022-06-12 19:35 ` Rudolf Adamkovič
2022-06-13 0:22 ` Tim Cross
2022-06-13 0:34 ` Ihor Radchenko
2022-06-13 2:16 ` Tim Cross
2022-06-13 5:30 ` [BUG] worg-setup.org is outdated (was: [accessibility] worg obscures text) Ihor Radchenko
2022-06-13 5:44 ` Tim Cross
2022-06-13 6:14 ` Timothy
2022-06-13 14:21 ` Bastien Guerry [this message]
2022-06-13 14:21 ` [BUG] worg-setup.org is outdated Bastien Guerry
2022-06-13 22:32 ` Tim Cross
2022-06-14 0:57 ` Ihor Radchenko
2022-06-14 1:08 ` Tim Cross
2022-06-14 1:37 ` Ihor Radchenko
2022-06-14 1:51 ` Tim Cross
2022-06-14 2:18 ` Ihor Radchenko
2022-06-14 2:46 ` Tim Cross
2022-06-14 2:59 ` Ihor Radchenko
2023-01-02 10:40 ` Ihor Radchenko
2023-01-02 20:03 ` Tim Cross
2023-01-03 11:01 ` Ihor Radchenko
2023-01-04 10:21 ` [TASK] Enhance Worg HTML styling (was: [BUG] worg-setup.org is outdated) Bastien Guerry
2023-01-04 10:50 ` Alain.Cochard
2023-01-04 22:43 ` Tim Cross
2023-01-05 14:07 ` Alain.Cochard
2023-01-05 15:41 ` Tim Cross
2023-01-05 20:18 ` [TASK] Enhance Worg HTML styling Leo Butler
2023-01-06 1:23 ` Tim Cross
2022-06-13 5:37 ` [accessibility] worg obscures text Max Nikulin
2022-06-16 3:22 ` Tim Cross
2022-06-16 23:30 ` Samuel Wales
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=8735g8pru7.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@gmail.com \
--cc=yantar92@gmail.com \
/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).