emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Fabian Kurmann <fabian.kurmann@uni-duesseldorf.de>,
	Jens Schmidt <jschmidt4gnu@vodafonemail.de>
Cc: emacs-orgmode@gnu.org, public@protesilaos.com
Subject: Re: Fwd: [BUG] Sparse tree does not work on properties with dashes
Date: Thu, 18 Jan 2024 15:44:53 +0000	[thread overview]
Message-ID: <87v87qprwq.fsf@localhost> (raw)
In-Reply-To: <87jzv67k3p.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

>> Expected behaviour: produce a sparse tree.
>>
>> Actual result: no sparse tree.
>
> Thanks for reporting!
> Confirmed.
>
> This is because `org-sparse-tree' will produce the following matcher:
>
>      TEST-HELLO="one"
>
> Which is interpreted as: Has tag "TEST" and does not have property
> "HELLO" set to "one".

`org-make-tags-matcher' is now supposed to handle \-escaped dashes in
properties. However, it does not seem to work:

(org-make-tags-matcher "TEST\-HELLO=\"one\"" t) yields

(progn
   (setq org-cached-props nil)
   (or
    (and
     (not (string= (or (org-cached-entry-get nil \"HELLO\") \"\") \"one\"))
     (member \"TEST\" tags-list))))

Jens, do you have any ideas?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-01-18 15:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87v8etfaw3.fsf@protesilaos.com>
2023-07-09 13:58 ` Fwd: [BUG] Sparse tree does not work on properties with dashes Fabian Kurmann
2023-07-11 11:39   ` Ihor Radchenko
2024-01-18 15:44     ` Ihor Radchenko [this message]
2024-03-19 14:03       ` Ihor Radchenko
2024-03-20  5:03         ` Protesilaos Stavrou

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=87v87qprwq.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=fabian.kurmann@uni-duesseldorf.de \
    --cc=jschmidt4gnu@vodafonemail.de \
    --cc=public@protesilaos.com \
    /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).