From: Nick Dokos <nicholas.dokos@hp.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: nicholas.dokos@hp.com,
Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: dates before 1970
Date: Fri, 11 Mar 2011 11:16:08 -0500 [thread overview]
Message-ID: <3861.1299860168@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Eric S Fraga <e.fraga@ucl.ac.uk> of "Fri, 11 Mar 2011 08:47:58 GMT." <87ei6ehwld.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> > So I'd guess raising an exception might be the simplest way to deal with
> > this. Here's a patch to try out:
>
> This seems to work fine. Thanks.
>
Maybe not - see Bastien's mail.
> I am glad, however, that I can enter any date and then use the S-<down>
> etc. keys to get the date I want. Of course, I am not sure if anything
> else in org breaks as a result... org-sparse-tree with very old
> scheduled dates seems to work. Haven't tried much else and I would
> guess few would notice?
>
That's the problem: one does not know whether the way from one
date to another passes through the quicksand of internal emacs time.
And as you say, any effects might escape notice.
Nick
prev parent reply other threads:[~2011-03-11 16:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 21:00 dates before 1970 Eric S Fraga
2011-03-10 23:06 ` Nick Dokos
2011-03-11 8:31 ` Bastien
2011-03-11 8:52 ` Carsten Dominik
2011-03-13 7:39 ` Carsten Dominik
2011-03-13 20:08 ` Eric S Fraga
2011-03-14 7:40 ` Carsten Dominik
2011-03-14 9:58 ` Bastien
2011-03-11 8:47 ` Eric S Fraga
2011-03-11 11:36 ` Carsten Dominik
2011-03-11 12:00 ` Eric S Fraga
2011-03-11 15:28 ` Carsten Dominik
2011-03-11 17:56 ` Gregor Zattler
2011-03-12 22:38 ` Robert Horn
2011-03-11 16:30 ` Nick Dokos
2011-03-14 10:21 ` Carsten Dominik
2011-03-14 15:11 ` Nick Dokos
2011-03-14 17:02 ` Carsten Dominik
2011-03-14 17:13 ` Nick Dokos
2011-03-14 18:12 ` Achim Gratz
2011-03-15 7:24 ` Carsten Dominik
2011-03-11 16:16 ` Nick Dokos [this message]
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=3861.1299860168@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=e.fraga@ucl.ac.uk \
--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).