Skip to content

[5.0] Reconsider org-gtd-areas-of-focus--set helper function #268

@Trevoke

Description

@Trevoke

Background

From discussion in #259, the org-gtd-areas-of-focus--set function was originally intended as both a helper and an aide to understanding how to configure the system when reading the documentation.

Current Behavior

The function skips setting area-of-focus for:

  • trash (archived directly)
  • quick-action (archived directly)
  • knowledge
  • project-task (inherits from project heading via view DSL)
(defun org-gtd-areas-of-focus--set ()
  "Use as a hook when decorating items after clarifying them."
  (unless (org-gtd-organize-type-member-p '(project-task trash knowledge quick-action))
    (org-gtd-area-of-focus-set-on-item-at-point)))

Concern

With the documentation now being "very large", users may set the organize hook without finding the documentation section explaining this specific hook's behavior. This could lead to confusion when the area-of-focus prompt doesn't appear for certain item types.

Consideration for 5.0

Evaluate whether this helper function has become counterproductive to the user experience, and consider:

  1. Removing the helper entirely
  2. Making the behavior more explicit/discoverable
  3. Improving documentation discoverability

Reference

Original discussion: #259 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions