restore inbox-current-tags-alist from inbox buffer to WIP clarifying buffer

[douo]

When using org-gtd-process-inbox, org-gtd creates a new buffer for each item but does not bring the heading metadata from inbox.org. This causes org-mode to be unable to find tags from the current buffer. This PR resolved #145 in my situation.

[Trevoke]

Hi @douo , thank you for looking into this!

Part of the intent with the upgrade to v3 is to stop depending as much on the hardcoded values in those files -- your tags are yours, and they are not required to make org-gtd work (the only exception is this default value for the organize-hooks, and maybe that's a bad default value).

The reason this decision was made is because I thought that your tags would always be your own, and therefore that you would just want to use org-mode to set the tags with org-tags-alist - as described in here https://orgmode.org/manual/Setting-Tags.html

If I made the wrong decision, and you have tags which you don't want to see in org-gtd, then we should create a customizable variable org-gtd-tags-alist instead. The reason for that is because the inbox should not be the home of your behavior-based settings - I did this in earlier versions of org-gtd because I did not know enough about how org-mode worked, but I have since learned a lot.

Eventually, while I would love to see folks who use org-gtd for years because it works very well for them, I also want to make it possible / seamless for people to move away from org-gtd to their own system, if they discover they have different needs.

So: is it possible for you to start using org-tags-alist in your configuration, or should we create org-gtd-tags-alist instead?

[douo]

Hi @Trevoke, org-current-tags-alist is not a personal use variable of mine. It is an org-mode defined variable assigned to all tags belonging to the current buffer. If this variable dose not sync to clarify buffer. org-set-tags-command can not work properly.

...
;; Version: 9.6.6
....
defvar-local org-current-tag-alist nil
  "Alist of all tag groups in current buffer.
This variable takes into consideration `org-tag-alist',
`org-tag-persistent-alist' and TAGS keywords in the buffer.")

I completely concur that this PR appears to be somewhat hardcoded. The primary issue at hand is that the tags defined in the inbox file, using the following syntax, are not being properly brought into WIP Clarifying buffer.

#+TAGS:

[Trevoke]

Hi @douo , sorry, let me write fewer words.

Org-GTD does not want you to use #+TAGS:.

Org-GTD wants you to use org-tag-alist.

Are you able to move your tags from #+TAGS: to (setq org-tag-alist ....) ?

If not, I have a better solution than this PR.

[douo]

Forcing the use of org-tag-alist may not be a good idea, as I use Org not only for GTD but also for my writing system. These two systems require different tag sets.

[Trevoke]

Okay. Then I have to think about it a little bit more. The main problem we're going to run into is that when we do a one-off clarification, the inbox may not be the buffer we come from, so you're going to run into more problems. Obviously we could fix that by always opening the inbox and taking the tags from that buffer, and maybe that's the simplest answer.

…

On Wed, May 17, 2023 at 10:29 AM Tiou Lims ***@***.***> wrote: Forcing the use of org-tag-alist may not be a good idea, as I use Org not only for GTD but also for my writing system. These two systems require different tag sets. — Reply to this email directly, view it on GitHub <#151 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAQSSP4AIKEMKTJMGY3VZDXGTOFJANCNFSM6AAAAAAYE2S57Q> . You are receiving this because you were mentioned.Message ID: ***@***.***>