Open jooert opened 6 years ago
I would like to have this feature to.
Does this have any priority in development? It's quite easy to get around, but would leave my files a bit more organized.
Does this have any priority in development?
I wasn't planning to work on it soon. If someone wants to take a shot though, we can go though that's needed.
I'd like to take a shot somewhere at the beginning of july, but I don't have any Java experience ;). If you give me some pointers on where else you parse global settings I think I could try to hack something together.
There's only TITLE
now and it's in OrgFileSettings.
I guess steps would be:
FILETAGS
in OrgFileSettings
tags
to books tablebook_tags
book_tags
(same as it's done for inherited_tags
)On Orgzly side #+FILETAGS is kinda covered by b.bookname Orgzly agenda queries. But on org-mode side, the #+FILETAGS remains one of easiest ways of quickly excluding agenda files from the scope of org-mode's org-agenda by simply putting #+FILETAGS into beginning of agenda files and then quickly filtering out by tags in org-agenda.
Good news Orgzly seem to preserve the existing #+FILETAGS records in org files.
Not being big priority, this is still a use case for this feature - when Orgzly user also uses synched org-mode and wants convenience with org-agenda tags filtering.
It would be great!
@sokolgeo Could you clarify what you mean by:
On Orgzly side #+FILETAGS is kinda covered by b.bookname Orgzly agenda queries.
We can have multiple filetags, right? But b.BOOKNAME
only matches the notebook name (unless I am mistaken), so the b
filter is more like searching for the #+CATEGORY
property of an Org file, which defaults to the filename (minus extension).
The work-around I used is to list all files with the FILETAGS in a search alongside the tag itself woth OR. This is a bit of extra work. But this way I can find the tasks in the specific files or other files, but with the tag. It's not quite convenient, but if your file structure is changing rarely, it'll work.
It would be great if Orgzly would respect the
#+FILETAGS:
setting as described in The Org Manual.