From: Ruijie Yu via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: gautier@gautierponsinet.xyz
Cc: Ihor Radchenko <yantar92@posteo.net>, Bastien <bzg@gnu.org>,
emacs-orgmode@gnu.org
Subject: Re: New face: org-agenda-calendar-timerange
Date: Fri, 20 Jan 2023 12:24:37 +0800 [thread overview]
Message-ID: <sdvzgadbzhz.fsf@fw.net.yu> (raw)
In-Reply-To: <sdv4jsldeii.fsf@fw.net.yu>
Ruijie Yu <ruijie@netyu.xyz> writes:
> [...]
> The patch applies cleanly on current main branch (52f29d4da), and all
> tests from `make test` passed. However, I don't see any effects on a
> test org buffer (see attached) -- in particular, I don't see the
> `org-agenda-calendar-daterange' face being shown anywhere on the buffer.
> According to `C-u C-x =' (`what-cursor-position'), all three date ranges
> use `org-date' face.
>
> $ git am this.patch
> $ make test
> $ emacs -Q -L lisp -l org agenda.org
> (type `C-u C-x =' on each date range to see `org-date')
>
> Thoughts? Will do the same on the original main branch to ensure I
> didn't misunderstand something.
Took another look at the previous mails and at the variable name, and I
realized that this change is for things under org-agenda, in which case
all three types of ranges are under their respective, correct faces.
Best,
RY
next prev parent reply other threads:[~2023-01-20 4:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 16:56 New face: org-agenda-calendar-timerange Gautier Ponsinet
2023-01-17 11:20 ` Ihor Radchenko
2023-01-17 22:25 ` gautier
2023-01-18 10:08 ` Ihor Radchenko
2023-01-18 15:41 ` gautier
2023-01-18 16:01 ` gautier
2023-01-19 11:00 ` Ihor Radchenko
2023-01-19 21:58 ` gautier
2023-01-20 3:32 ` Ruijie Yu via General discussions about Org-mode.
2023-01-20 4:24 ` Ruijie Yu via General discussions about Org-mode. [this message]
2023-01-20 11:24 ` Ihor Radchenko
2023-01-20 11:36 ` Bastien Guerry
2023-01-21 8:27 ` Ihor Radchenko
2023-01-21 8:29 ` Ihor Radchenko
2023-01-21 22:44 ` Gautier Ponsinet
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=sdvzgadbzhz.fsf@fw.net.yu \
--to=emacs-orgmode@gnu.org \
--cc=bzg@gnu.org \
--cc=gautier@gautierponsinet.xyz \
--cc=ruijie@netyu.xyz \
--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).