emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: gautier@gautierponsinet.xyz
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: New face: org-agenda-calendar-timerange
Date: Wed, 18 Jan 2023 16:41:27 +0100	[thread overview]
Message-ID: <bcbbae8e9098b49016529bb64e216e15@gautierponsinet.xyz> (raw)
In-Reply-To: <87v8l46tos.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> <2023-01-01 Sun 10:00>--<2023-01-01 Sun 15:00>
> and
> <2023-01-01 Sun 10:00-15:00>
> 
> are equivalent.
> 
> I'd say that it will make sense to apply `org-agenda-calendar-event'
> face and `org-agenda-timerange-leaders' to <2023-01-01 Sun 10:00-15:00>
> as well. What do you think about this approach?

So, the current situation is the following:

| Type of entry                                                          
     | Face                      | Use `org-agenda-timerange-leaders' |
|----------------------------------------------------------------------------+---------------------------+------------------------------------|
| simple date: <2023-01-01 Sun>                                          
     | org-agenda-calendar-event | no                                 |
| simple date with hour range: <2023-01-01 Sun 10:00-15:00>              
     | org-agenda-calendar-event | no                                 |
| timerange (same day): <2023-01-01 Sun 10:00>--<2023-01-01 Sun 15:00>   
     | default                   | yes                                |
| timerange (different days): <2023-01-01 Sun 10:00>--<2023-01-18 Wed 
15:00> | default                   | yes                                
|

and you say it would be better like this:

| Type of entry                                                          
     | Face                                      | Use 
`org-agenda-timerange-leaders' |
|----------------------------------------------------------------------------+-------------------------------------------+------------------------------------|
| simple date: <2023-01-01 Sun>                                          
     | org-agenda-calendar-event                 | no                     
             |
| simple date with hour range: <2023-01-01 Sun 10:00-15:00>              
     | org-agenda-calendar-event                 | yes                    
             |
| timerange (same day): <2023-01-01 Sun 10:00>--<2023-01-01 Sun 15:00>   
     | org-agenda-calendar-event                 | yes                    
             |
| timerange (different days): <2023-01-01 Sun 10:00>--<2023-01-18 Wed 
15:00> | new face (org-agenda-calendar-daterange?) | yes                 
                |

Is that correct?

This would be nice. However, this requires more complexes changes. I
don't know if I am capable of preparing such a patch, but I can give it
a try.

By the way, the entries "simple date with hour range" and "timerange (on
the same day)" are also presented differently in the agenda view, the
first ones look like:
   agenda:     10:00-15:00 Test simple date with hour range
while the second ones look like:
   agenda:     10:00 ┄┄┄┄┄ Test timerange (on the same day)

Should this change as well?


  reply	other threads:[~2023-01-18 15:42 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 [this message]
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.
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=bcbbae8e9098b49016529bb64e216e15@gautierponsinet.xyz \
    --to=gautier@gautierponsinet.xyz \
    --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).