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

Double entry in Agenda view for calendar entry. #198

Open
grizzz1y opened this issue Jan 19, 2024 · 3 comments
Open

Double entry in Agenda view for calendar entry. #198

grizzz1y opened this issue Jan 19, 2024 · 3 comments

Comments

@grizzz1y
Copy link

The agenda view picks up both the timestamps in the entry. The timestamp that is used for the org_gtd_timestamp in the calendar entry should be an inactive timestamp. That would prevent the double entry in the agenda view.

@Jousimies
Copy link

same problem

@Trevoke
Copy link
Owner

Trevoke commented Jan 22, 2024

Would you both by chance be using doom emacs? If I recall correctly, there seems to be a configuration in there, or maybe a separate package, or.. Something.. That breaks this. If you're not using doom emacs, what is your org-mode / org-gtd configuration?

The duplicate timestamp should be ignored, see this particular configuration: https://github.com/Trevoke/org-gtd.el/blob/master/org-gtd-agenda.el#L64

The duplicate timestamps are unfortunately required for orgzly compatibility. See:

@garid3000
Copy link

Time to time (after I updating my packages), I get this double-entry-in-agenda. And sometimes this disappears. Currently I was having this issue.

But, after manually setting value of org-agenda-skip-additional-timestamps-same-entry (@Trevoke mentioned) manually to t (and reload org-gtd-mode), the double entries are resolved.

I might add following line into my init.el. Anyways thanks @Trevoke.

(setq org-agenda-skip-additional-timestamps-same-entry t)

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

No branches or pull requests

4 participants