From: Michael Brand <email@example.com>
To: Org Mode <firstname.lastname@example.org>
Subject: Re: No dot in datepicker dialog
Date: Tue, 23 Apr 2013 18:04:28 +0200 [thread overview]
Message-ID: <CALn3zohFzW=-oOFwCzDeJf1roq5xGzCoHua+pcyePYN55XL=Sg@mail.gmail.com> (raw)
On Thu, Apr 4, 2013 at 3:18 PM, Karl Voit <email@example.com> wrote:
> AFAIR I was able to use "." (to jump to $today) *and*
> type "31.12." (without C-q . or similar) before.
> So in my opinion, it is not interfering at all: It can be solved by
> interpreting "." (as goto-today) *only* if nothing else has been
> written into the minibuffer.
> This way, "." jumps to today *and* the user is able to enter
> "31.12." in the minibuffer in order to jump to the last day of
On Thu, Apr 4, 2013 at 4:19 PM, Gregor Zattler <firstname.lastname@example.org> wrote:
> Or: would it help to restrict the special meaning of `.' as a
> reference for `today' only for the first character of the date
> picker input?
Yes, this is how it worked and I was used to before too, very convenient.
And regarding the _echo_ of ".": I find the current behavior of not
echoing the "." confusing, as if it would be ignored when typed after
"3 1". There and also when "." is typed in the first place to jump to
today it was echoed in the prompt which I appreciated as a visual
feedback for what has actually been typed.
In other words:
- "C-c . ." _echoed_ and did what
"C-c . C-q ." _echoes_ and does now (goto today)
- "C-c . 3 1 . 1 2 ." echoed and did what
"C-c . 3 1 C-q . 1 2 C-q ." echoes and does now (goto Dec 31)
Reduced to these simple use cases applied on an existing past/future
timestamp the changes in Org seem strange.
next prev parent reply other threads:[~2013-04-23 16:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 19:49 No dot in datepicker dialog Karl Voit
2013-04-04 12:53 ` Bastien
2013-04-04 13:18 ` Karl Voit
2013-04-04 14:19 ` Gregor Zattler
2013-04-23 16:04 ` Michael Brand [this message]
2013-04-24 8:06 ` Bastien
2013-04-24 8:23 ` Carsten Dominik
2013-04-24 8:31 ` Bastien
2013-04-24 8:43 ` Michael Brand
2013-04-24 8:51 ` Bastien
2013-04-24 9:13 ` Michael Brand
2013-04-24 8:52 ` Michael Brand
2013-04-24 9:12 ` Carsten Dominik
2013-04-24 9:38 ` Bastien
2013-04-24 9:40 ` Carsten Dominik
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 \
* 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).