[elpa] externals/org 9f4f7338d7 1/4: org-element-timestamp-parser: Fix regexp

[ELPA Syncer]

branch: externals/org
commit 9f4f7338d7b4d27438fa6c9eb241726a87dc16ed
Author: Ihor Radchenko <yantar92@posteo.net>
Commit: Ihor Radchenko <yantar92@posteo.net>

    org-element-timestamp-parser: Fix regexp
    
    * lisp/org-element.el (org-element--timestamp-regexp): Do not match
    malformed timestamps like:
    
    <202-07-10 .+1d>
    
    `org-ts-regexp-both' already covers the removed part of the regexp.
    It appears that the problematic regexp is coming from a copy-paste from
    `org-agenda-get-timestamps' where the inaccurate regexp is used to
    search timestamps with repeaters in conjunction to searching for exact
    agenda dates.  In `org-agenda-get-timestamps', inaccuracy is not a
    problem because proper matching against `org-ts-regexp-both' is
    performed later, simply skipping non-timestamps.
    
    Reported-by: Platon Pronko <platon7pronko@gmail.com>
    Link: 
https://orgmode.org/list/6000e3bf-f95f-44fd-b321-cf44acd5c485@gmail.com
---
 lisp/org-element.el | 2 --
 1 file changed, 2 deletions(-)

diff --git a/lisp/org-element.el b/lisp/org-element.el
index 191bb5698d..fe914a964f 100644
--- a/lisp/org-element.el
+++ b/lisp/org-element.el
@@ -4279,8 +4279,6 @@ Assume point is at the target."
 
 (defconst org-element--timestamp-regexp
   (concat org-ts-regexp-both
-         "\\|"
-         "\\(?:<[0-9]+-[0-9]+-[0-9]+[^>\n]+?\\+[0-9]+[dwmy]>\\)"
          "\\|"
          "\\(?:<%%\\(?:([^>\n]+)\\)\\([^\n>]*\\)>\\)")
   "Regexp matching any timestamp type object.")