From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-timestamp-up/down broken in tip
Date: Fri, 22 Jul 2011 08:55:13 +0200 [thread overview]
Message-ID: <80sjpyhkj2.fsf@somewhere.org> (raw)
In-Reply-To: 87vcuvyxmk.wl%max@openchat.com
Hi Max,
Max Mikhanosha wrote:
> With latest git I can only press S-up or S-down on the time part of
> the timestamp once, after changing the time it moves point to the
> closing bracket, and doing another S-up or S-down changes the date
> part instead of time.
>
> Example: with point on the "05" at the timestamp [2011-07-21 Thu
> 19:05] doing Shift-Up results in time correctly changed to 19:10, but
> point moves to the closing bracket. Next time you press S-Up it
> changes date, not time.
>
> Reverting following commit fixes the problem for me:
>
> commit fd0f8e10d1d3a339da9460d6c71283e85897c455
> Author: Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date: Thu Jul 21 11:48:35 2011 +0200
>
> Fix bug with TODO states changes modifying scheduling of next headline
>
> * lisp/org.el (org-timestamp-change): some locales don't use the same
> length for date abbreviations. Set a marker at origin in case length
> of new timestamp is different.
I don't know which commit broke it, but I confirm the symptom you've spotted.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-07-22 6:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 0:20 org-timestamp-up/down broken in tip Max Mikhanosha
2011-07-22 6:55 ` Sebastien Vauban [this message]
2011-07-22 7:17 ` Bastien
2011-07-22 7:27 ` Bastien
2011-07-22 7:53 ` Bastien
2011-07-22 8:47 ` Nicolas Goaziou
2011-07-22 20:11 ` Nicolas Goaziou
2011-07-24 19:10 ` Bastien
2011-07-25 10:01 ` Nicolas Goaziou
2011-07-25 13:57 ` 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=80sjpyhkj2.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).