From: Jude DaShiell <jdashiel@panix.com>
To: Detlef Steuer <steuer@hsu-hh.de>, emacs-orgmode@gnu.org
Cc: Bastien <bzg@gnu.org>
Subject: Re: Bug? Multi day event with times
Date: Sun, 26 Jan 2020 13:03:51 -0500 [thread overview]
Message-ID: <alpine.NEB.2.21.2001261301450.18808@panix1.panix.com> (raw)
In-Reply-To: <20200126184955.544b07ad@linux-h0yu.plc.hootoo.com>
On Sun, 26 Jan 2020, Detlef Steuer wrote:
> Date: Sun, 26 Jan 2020 12:49:55
> From: Detlef Steuer <steuer@hsu-hh.de>
> To: emacs-orgmode@gnu.org
> Cc: Bastien <bzg@gnu.org>
> Subject: Re: Bug? Multi day event with times
>
> Am Sun, 26 Jan 2020 18:14:25 +0100
> schrieb Bastien <bzg@gnu.org>:
>
> > Hi Detlef,
> >
> > Detlef Steuer <steuer@hsu-hh.de> writes:
> >
> > > Stumbled upon this:
> > >
> > > ( emacs 26.3, org-contrib-plus 20191118, linux)
> > >
> > > In my orgfile I have:
> > > ** some travel
> > > <2020-01-30 Do 10:00>-<2020-02-01 Sa 16:00>
> > >
> > > In the agenda that is shown as:
> > > Donnerstag 30 January 2020
> > > unsorted: 10:00-11:00 (1/3): some travel
> > > Freitag 31 January 2020
> > > unsorted: (2/3): some travel
> > > Samstag 1 February 2020
> > > unsorted: 16:00-17:00 (3/3): some travel
> >
> > I'm not sure what's not working as expected here.
> >
> > Can you restate it again?
>
> Hi Bastien,
>
> the travel has a *time range*, but both times are used as *time stamps*
> with default length 1h, only the date part is used as a range.
>
> In the original case I tried to put the leaving times of my booked
> railway connections into the range hoping to see:
>
> Donnerstag 30 January 2020
> unsorted: 10:00 (1/3): some travel
> Freitag 31 January 2020
> unsorted: (2/3): some travel
> Samstag 1 February 2020
> unsorted: 16:00 (3/3): some travel
>
> I understand, why is shown what is shown.
> But maybe there is room for improvement.
>
> May be:
> Donnerstag 30 January 2020
> unsorted: 10:00-23:59 (1/3): some travel
> Freitag 31 January 2020
> unsorted: (2/3): some travel
> Samstag 1 February 2020
> unsorted: 00:00-16:00 (3/3): some travel
>
> Or
> Donnerstag 30 January 2020
> unsorted: 10:00- (1/3): some travel
> Freitag 31 January 2020
> unsorted: (2/3): some travel
> Samstag 1 February 2020
> unsorted: -16:00 (3/3): some travel
>
> Is there a way to achieve one of the above?
>
> Thanks
> Detlef
>
There's a duration command in orgmode, but it handles at most 24 hours or
less. If that duration could cross midnight, I think you could use that
and solve this problem.
> > >
> > Thanks,
> >
>
>
>
--
next prev parent reply other threads:[~2020-01-26 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 13:54 Bug? Multi day event with times Detlef Steuer
2020-01-26 17:14 ` Bastien
2020-01-26 17:49 ` Detlef Steuer
2020-01-26 18:03 ` Jude DaShiell [this message]
2020-02-11 23:14 ` Bastien
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=alpine.NEB.2.21.2001261301450.18808@panix1.panix.com \
--to=jdashiel@panix.com \
--cc=bzg@gnu.org \
--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).