emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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
Date: Sun, 26 Jan 2020 18:49:55 +0100	[thread overview]
Message-ID: <20200126184955.544b07ad@linux-h0yu.plc.hootoo.com> (raw)
In-Reply-To: <87wo9eb0ni.fsf@gnu.org>

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


> 
> Thanks,
> 

  reply	other threads:[~2020-01-26 17:50 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 [this message]
2020-01-26 18:03     ` Jude DaShiell
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=20200126184955.544b07ad@linux-h0yu.plc.hootoo.com \
    --to=steuer@hsu-hh.de \
    --cc=bzg@gnu.org \
    --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).