From: Carsten Dominik <carsten.dominik@gmail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: bug#9695: allowed date range
Date: Thu, 13 Oct 2011 10:02:10 +0200 [thread overview]
Message-ID: <009531D7-6FAF-4B1C-80D5-90787542F016@gmail.com> (raw)
In-Reply-To: <87ipntjpbv.fsf@thinkpad.tsdh.de>
On 13.10.2011, at 09:57, Tassilo Horn wrote:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
> Hi Eric,
>
>>> Oh, now I see what's wrong. All time stamps consist of the date and
>>> then the day's name abbreviation, which is missing with your example.
>>> Correct would be
>>>
>>> <2011-10-17 Mon>--<2011-10-30 Sun>
>>
>> Although the day is optional according to the regexp. I would
>> definitely like to have the regexp with the space optional as well as
>> there are cases where I want to type the date in directly (not in org
>> mode for whatever reason). In those cases, it is easy to type
>> 2011-01-01 or whatever but it's not necessarily trivial to determine
>> the day of the week...
>
> Yes, I agree, although you can use org-time-stamp everywhere (in emacs).
> And you can actually insert timestamps simply by writing
>
> <2011-10-13 >
>
> with the whitespace to make it a valid timestamp. That will be shown as
> day entry in the agenda, and you might have typed it in using some
> non-emacs text editor on you phone.
>
> Now, back in org-mode, simply S-<up> and S-<down> on any number, and et
> voila, the missing day name abbrev is added automatically.
>
>> Actually, interesting thought experiment: does org actually do any
>> consistency checks, comparing the date and the day of the week?
>
> No, I don't think so. Manipulating and creating timestamps using the
> provided commands ensures their correctness, but for actual calculation
> the day names are ignored. It's just for humans.
Just to confirm, this is correct.
- Carsten
next prev parent reply other threads:[~2011-10-13 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ty7kd8oh.fsf@kanis.fr>
2011-10-12 6:53 ` bug#9695: allowed date range Ivan Kanis
2011-10-13 7:28 ` Tassilo Horn
2011-10-13 7:48 ` Eric S Fraga
2011-10-13 7:57 ` Tassilo Horn
2011-10-13 8:02 ` Carsten Dominik [this message]
2011-10-13 10:15 ` Eric S Fraga
2011-10-13 8:27 ` Carsten Dominik
2011-10-13 10:14 ` Eric S Fraga
2011-10-13 13:04 ` Tassilo Horn
2011-10-16 13:45 ` Michael Brand
2011-11-09 18:18 ` Carsten Dominik
2011-11-09 21:32 ` Michael Brand
2011-11-03 17:22 ` Michael Brand
[not found] ` <87ehyiitv7.fsf@googlemail.com>
2012-03-23 1:30 ` Glenn Morris
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=009531D7-6FAF-4B1C-80D5-90787542F016@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tassilo@member.fsf.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).