emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Detlef Steuer <steuer@hsu-hh.de>
To: emacs-orgmode@gnu.org
Subject: Bug? Multi day event with times
Date: Thu, 16 Jan 2020 14:54:02 +0100	[thread overview]
Message-ID: <20200116145402.37faae44@gaia> (raw)


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

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?


             reply	other threads:[~2020-01-16 13:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 13:54 Detlef Steuer [this message]
2020-01-26 17:14 ` Bug? Multi day event with times Bastien
2020-01-26 17:49   ` Detlef Steuer
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:

  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=20200116145402.37faae44@gaia \
    --to=steuer@hsu-hh.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).