emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: thunk2@arcor.de (Thomas Plass)
To: emacs-orgmode@gnu.org
Subject: [PATCH] make 'org-at-date-range-p work like org-at-timestamp-p
Date: Fri, 15 Mar 2019 22:13:24 +0100	[thread overview]
Message-ID: <23692.5492.62319.323977@AGAME7.local> (raw)

Hello maintainers,

it's counter-intuitive that 'org-at-date-range-p doesn't work like
'org-at-timestamp-p when point is on the leading bracket of a range.
Witness (^ = point)

<2019-12-30 Mo 12:00>
^ (org-at-timestamp-p)                            => t

<2019-12-30 Mo 12:00>--<2019-12-31 Di 09:00>
^ (org-at-timestamp-p)                            => t
 ^ (org-at-date-range-p)                          => t
^ (org-at-date-range-p)                           => nil

Is the attached patch OK?

Regards,

Thomas


From 11424a8a8f975148a6914ba324b7e34218fed30d Mon Sep 17 00:00:00 2001
From: Thomas Plass <thunk2@arcor.de>
Date: Fri, 15 Mar 2019 22:56:01 +0200
Subject: [PATCH] * make 'org-at-date-range-p work like org-at-timestamp-p  
 when point is on starting bracket

---
 lisp/org.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/org.el b/lisp/org.el
index 24e1549a2..2053ae6b7 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -10651,7 +10651,7 @@ on INACTIVE-OK."
   (save-excursion
     (catch 'exit
       (let ((pos (point)))
-	(skip-chars-backward "^[<\r\n")
+	(or (looking-at-p "[<[]") (skip-chars-backward "^[<\r\n"))
 	(skip-chars-backward "<[")
 	(and (looking-at (if inactive-ok org-tr-regexp-both org-tr-regexp))
 	     (>= (match-end 0) pos)
-- 
2.13.1.windows.2

             reply	other threads:[~2019-03-15 21:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 21:13 Thomas Plass [this message]
2019-03-18 21:43 ` [PATCH] make 'org-at-date-range-p work like org-at-timestamp-p Nicolas Goaziou
2019-03-19 19:46   ` Thomas Plass
2019-03-19 19:49   ` Thomas Plass
2019-03-19 20:28     ` Nicolas Goaziou

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=23692.5492.62319.323977@AGAME7.local \
    --to=thunk2@arcor.de \
    --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).