From: Ihor Radchenko <yantar92@posteo.net>
To: Cletip Cletip <clement020302@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Inactive interval is not correctly displayed in agenda view (was: [BUG?] Org-agenda doesn't work with this error : Search failed: "\<SCHEDULED: *<\([^>]+\)>")
Date: Wed, 11 Oct 2023 09:04:47 +0000 [thread overview]
Message-ID: <87cyxl8r80.fsf@localhost> (raw)
In-Reply-To: <87jzru8mjt.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
>> if I have the following heading :
>>
>> * A test
>> [2023-10-10 Tue 17:25]--[2023-10-10 Tue 17:30]
>> <2023-10-10 Tue 17:25>--<2023-10-10 Tue 17:30>
>>
>> The "org interval" are not respected for the inactive timestamp. See what
>> is the result in org-agenda :
>>
>> 17:25-17:30 A test
>> 17:25-17:25 [ A test
>> 17:30-17:30 [ A test
>>
>> The first line is what I want : a beginning hour, with a end. But, the two
>> other are not normal : it must be the same line.
>
> I can reproduce. Indeed looks odd.
> I will look closer at this problem later.
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=e1569918c
--
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:[~2023-10-11 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 15:14 [BUG?] Org-agenda doesn't work with this error : Search failed: "\<SCHEDULED: *<\([^>]+\)>" Cletip Cletip
2023-10-10 15:48 ` Ihor Radchenko
2023-10-10 16:03 ` Cletip Cletip
2023-10-10 16:20 ` Ihor Radchenko
2023-10-10 16:33 ` [BUG] Inactive interval is not correctly displayed in agenda view (was: [BUG?] Org-agenda doesn't work with this error : Search failed: "\<SCHEDULED: *<\([^>]+\)>") Ihor Radchenko
2023-10-10 16:38 ` Cletip Cletip
2023-10-11 9:04 ` Ihor Radchenko [this message]
2023-10-14 10:04 ` Cletip Cletip
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=87cyxl8r80.fsf@localhost \
--to=yantar92@posteo.net \
--cc=clement020302@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).