Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename org-gtd-agenda.el to org-gtd-engage.el #167

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

doolio
Copy link
Contributor

@doolio doolio commented May 22, 2023

This renaming aligns it with the name for step 5 of the GTD methodology. Command org-gtd-show-all-next renamed to org-gtd-engage-next as well.

Resolves: #165

@doolio doolio force-pushed the resolve-issue-165 branch 2 times, most recently from 4114080 to f6730ac Compare May 22, 2023 20:55
This renaming aligns it with the name for step 5 of the GTD methodology.
Command org-gtd-show-all-next renamed to org-gtd-engage-next as well.

Resolves: Trevoke#165
@doolio doolio force-pushed the resolve-issue-165 branch from f6730ac to 5083df7 Compare May 22, 2023 20:58
@doolio
Copy link
Contributor Author

doolio commented May 24, 2023

I believe the order of functions is how you expect to see them so no changes required in that regard. I'm curious why bothdefun org-gtd-engage and the now renamed defun org-gtd-engage-next exist? Would users not always want to see their scheduled tasks and NEXT tasks in the same view? Otherwise, don't they risk missing a scheduled task if they get into the habit of only invoking org-gtd-engage-next?

(Aside: I assume there is no issue with the command org-gtd-engage having the same name as the file it is in?)

org-gtd-engage.el Outdated Show resolved Hide resolved
Node: Finding lost tasks56265
Node: Projects without a NEXT item56795
Node: I can't create a project when clarifying an inbox item!57266
Ref: Relevant commands with new names25224
Copy link
Contributor Author

@doolio doolio May 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unsure where these diffs and the others like it come from. A result of regenerating the docs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

org-gtd-agenda.el should be renamed org-gtd-engage.el
1 participant