From: Ihor Radchenko <yantar92@posteo.net>
To: Detlef Steuer <steuer@hsu-hh.de>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: surprising(?) interaction between agenda grid and default-duration
Date: Tue, 18 Oct 2022 07:30:19 +0000 [thread overview]
Message-ID: <87edv5fv1w.fsf@localhost> (raw)
In-Reply-To: <20211119135325.7f3f85a9@hsu-hh.de>
Detlef Steuer <steuer@hsu-hh.de> writes:
> I you specify a default duration of an event, say,
>
> (setq org-agenda-default-appointment-duration 60)
>
> and specify a time grid, say
>
> (setq org-agenda-time-grid '((today remove-match)
> (800 1000 1200 1400 1600 1800 2000)
> "......" "----------------" ))
>
> Then setting the default duration overrides the grid appearance.
> ...
> 13:40-14:40 now - - - - - - - - - - - - - - - - - - - - - - - - -
> 14:00-15:00 ----------------
> 16:00-17:00 ----------------
> 18:00-19:00 ----------------
> 20:00-21:00 ----------------
>
> caught me by surprise. Even the 2 hour block length setting is overridden.
>
> If this should be considered a bug, I don't know. But maybe the manual
> should mention and describe the relationship between these settings?
>
> As the description of org-agenda-default-appointment-duration does not
> mention the grid at all, I would think the logical improvement would be
> to let the grid alone and use the default duration as advertised only.
Confirmed.
--
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>
next prev parent reply other threads:[~2022-10-18 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 12:53 surprising(?) interaction between agenda grid and default-duration Detlef Steuer
2022-10-18 7:30 ` Ihor Radchenko [this message]
2024-01-17 14:41 ` 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=87edv5fv1w.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=steuer@hsu-hh.de \
/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).