Bug: org-agenda-get-sexps and erroneous agenda tag filtering. [8.2.6 (8.2.6-dist @ /home/rberger/Emacs/share/emacs/site-lisp/org/)]

Bug: org-agenda-get-sexps and erroneous agenda tag filtering. [8.2.6 (8.2.6-dist @ /home/rberger/Emacs/share/emacs/site-lisp/org/)]

[Raimund Berger]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

     http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.
------------------------------------------------------------------------

Hi there,

there seems to be an error in org-agenda-get-sexps, in the way tags are
stored for sexp diary entries. I noticed that when trying to filter in
the agenda, for diary entries that inherited a file wide PERSONAL tag.
The sexp entries just vanished when the filter was applied, while normal
diary entries in the diary tree were displayed as expected.

For each normal entry in the diary, the inherited tag was stored in
lower case as an agenda text property of the specific entry, so the tag
read "personal". Except for sexps, where the tag was stored "as is" in
upper case, namely PERSONAL.

By comparing with other functions, I noticed that deleting the 
  'tags tags
part in code portion
	    (org-add-props txt props 'org-marker marker
			   'org-category category 'date date 'todo-state todo-state
			   'org-category-position category-pos 'tags tags
			   'level level
			   'type "sexp" 'warntime warntime)

of function
  org-agenda-get-sexps

fixed the issue. Apparantly, the tags are aleady dealt with by the
"org-add-props txt" call, and correctly so (in lower case).

Regards, R.


Emacs  : GNU Emacs 24.3.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10)
 of 2014-05-18 on gigli
Package: Org-mode version 8.2.6 (8.2.6-dist @ /home/rberger/Emacs/share/emacs/site-lisp/org/)

Re: Bug: org-agenda-get-sexps and erroneous agenda tag filtering. [8.2.6 (8.2.6-dist @ /home/rberger/Emacs/share/emacs/site-lisp/org/)]

[Bastien]

Hi Raimund,

this is now fixed, thanks and sorry for the delay.

Would be good if you can confirm if the issue is gone for you.

Thanks,

-- 
 Bastien