Re: Bug? Multi day event with times

2020-02-11 Thread Bastien
Hi Detlef,

Detlef Steuer  writes:

> My travel starts at 10am on Thurday and stretches till Sunday 4pm.

I would use

** some travel
   <2020-01-30 Do 10:00-16:00>-<2020-02-01 Sa 10:00-16:00>

which should, with a recent Org, display times every three day
in the agenda view.

Not ideal, but closest to what's true: you start at 10 one day,
you finish at 4pm the last day, and things inbetween probably
happen between 10am and 4pm :)

-- 
 Bastien



Re: Bug? Multi day event with times

2020-01-26 Thread Jude DaShiell
On Sun, 26 Jan 2020, Detlef Steuer wrote:

> Date: Sun, 26 Jan 2020 12:49:55
> From: Detlef Steuer 
> To: emacs-orgmode@gnu.org
> Cc: Bastien 
> Subject: Re: Bug? Multi day event with times
>
> Am Sun, 26 Jan 2020 18:14:25 +0100
> schrieb Bastien :
>
> > Hi Detlef,
> >
> > Detlef Steuer  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
> > > Freitag31 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
> Freitag31 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
> Freitag31 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
> Freitag31 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,
> >
>
>
>

-- 




Re: Bug? Multi day event with times

2020-01-26 Thread Detlef Steuer
Am Sun, 26 Jan 2020 18:14:25 +0100
schrieb Bastien :

> Hi Detlef,
> 
> Detlef Steuer  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
> > Freitag31 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 
Freitag31 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 
Freitag31 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 
Freitag31 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,
> 




Re: Bug? Multi day event with times

2020-01-26 Thread Bastien
Hi Detlef,

Detlef Steuer  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
> Freitag31 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?

Thanks,

-- 
 Bastien



Bug? Multi day event with times

2020-01-16 Thread Detlef Steuer
Hi!

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
Freitag31 January 2020
  unsorted:   (2/3):  some travel
Samstag 1 February 2020
  unsorted:   16:00-17:00 (3/3):  some travel

Not sure I want to call it a real bug as I can understand why
it happens that way, but it's not what I expected.

My travel starts at 10am on Thurday and stretches till Sunday 4pm.

Any hint how to enter such an event besides splitting in three
and losing the 2/3 information on Friday?

Detlef