emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: [BUG] Use of period in org-read-date broken
Date: Fri, 23 Oct 2015 09:41:11 -0500	[thread overview]
Message-ID: <87a8r97im0.fsf@fastmail.fm> (raw)

The commit e802936f4b39f8b1e56cc015f34aa655565afe7f broke the use of the
period at the beginning of the minibuffer as a means to jump to the
current day.

Steps to replicate:

1. Evaluate (org-read-date)

2. Use Shift-Left to go to the previous date.

3. Type a period at beginning of minibuffer prompt.

Expected behavior:

The calendar should jump to the current day and no period should be
inserted in the minibuffer. That is the behavior that always worked in
the past and the behavior that is intended in lines 16772 to 16777 of
org.el.

Actual behavior:

A period is inserted in the minibuffer and the calendar does not jump to
the current day.

Here is the problematic commit:

--8<---------------cut here---------------start------------->8---
commit e802936f4b39f8b1e56cc015f34aa655565afe7f
Author: Kyle Meyer <kyle@kyleam.com>
Date:   Sun Sep 27 12:27:52 2015 -0400

    Pass LIMIT argument to org-looking-back
    
    * lisp/org-mouse.el (org-mouse-insert-item):
    (org-mouse-context-menu):
    * lisp/org-pcomplete.el (org-thing-at-point):
    * lisp/org.el (org-read-date-minibuffer-local-map):
    (org-timestamp-change): Provide LIMIT argument to org-looking-back.
    * lisp/org.el (org-read-date-minibuffer-local-map):
    (org-insert-heading): Replace looking-back with org-looking-back.
    
    As of Emacs 25, the LIMIT argument to looking-back is advertised as a
    required argument.
--8<---------------cut here---------------end--------------->8---

Thanks,
Matt

             reply	other threads:[~2015-10-23 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 14:41 Matt Lundin [this message]
2015-10-23 15:26 ` [BUG] Use of period in org-read-date broken Kyle Meyer

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=87a8r97im0.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --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).