Task management with org-roam Vol. 2: Categories - org-agenda fails to get category name #172
Replies: 2 comments 10 replies
-
|
hey @DominikMendel I have a very busy day so will not be able to look into this, but from a quick glance I can say that "for some reason" seems like your configuration. The
Do you have non-org-mode files in your |
Beta Was this translation helpful? Give feedback.
-
|
P.S. I moved this to discussions as it has no connection to vulpea library. Also renamed it to avoid confusion (at least my own when I skim through issues/discussions). |
Beta Was this translation helpful? Give feedback.
-
|
Yes, thank you for pointing this out. And correct, I think this solution is from one of your blog posts. So I'm curious as to what changed potentially in org or Org-Agenda where this is an issue now. If you don't mind assisting, I'm not sure the best way to solve this. The code snippet is as follows: ;; Vulpea functions to help with naming view
(setq org-agenda-prefix-format
'((agenda . " %i %(vulpea-agenda-category 20)%?-20t% s")
(todo . " %i %(vulpea-agenda-category 20) ")
(tags . " %i %(vulpea-agenda-category 20) ")
(search . " %i %(vulpea-agenda-category 20) ")))
(defun vulpea-agenda-category (&optional len)
"Get category of item at point for agenda.
Category is defined by one of the following items:
- CATEGORY property
- TITLE keyword
- TITLE property
- filename without directory and extension
When LEN is a number, resulting string is padded right with
spaces and then truncated with ... on the right if result is
longer than LEN.
Usage example:
(setq org-agenda-prefix-format
'((agenda . \" %(vulpea-agenda-category) %?-12t %12s\")))
Refer to `org-agenda-prefix-format' for more information."
(let* ((file-name (when buffer-file-name
(file-name-sans-extension
(file-name-nondirectory buffer-file-name))))
(title (vulpea-buffer-prop-get "title"))
(category (org-get-category))
(result
(or (if (and
title
(string-equal category file-name))
title
category)
"")))
(if (numberp len)
(s-truncate len (s-pad-right len " " result))
result)))Where the problem is in I've confirmed that all of my The error message above is strange as it's complaining about the |
Beta Was this translation helpful? Give feedback.
-
|
Apologies for slow response. Busy days. And of course I don't mind helping.
If you click on 3 dots you should see full error by the way. But it still looks like it's trying to say you are not in org-mode buffer. So one of the ideas I have in mind is to actually hook into Anyways, this is the code I am thinking about. I haven't actually tested it, but it should work. (defun my-error-logging-hook (orig-fun &rest args)
"A function that logs errors and the current buffer."
(condition-case err
(apply orig-fun args)
(error
(message "Error in %s: %s\nCurrent buffer: %s"
(symbol-name orig-fun)
(error-message-string err)
(buffer-name (current-buffer)))
(signal (car err) (cdr err)))))
;; Hook the target function with the error-logging hook
(advice-add 'org-get-category :around 'my-error-logging-hook) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the suggestion and the time @d12frosted. I ran the suggest error-logging code and got this in my message buffer: I'm not sure if that means there is something wrong with the advice'd function, or something wrong within my org itself. Since I don't see the |
Beta Was this translation helpful? Give feedback.
-
|
Ah, my bad. I forgot that (defun my-error-logging-hook (orig-fun &rest args)
"A function that logs errors and the current buffer."
(condition-case err
(apply orig-fun args)
(error
(message "Error in %s\nError: %s"
(buffer-name (current-buffer))
(error-message-string err))
(signal (car err) (cdr err)))))You will still see the same error, but in the messages buffer it should tell you where the error originated. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for that @d12frosted! That got it properly working. The error found though.. is strange.. It looks like org is wrestling with itself and it's not an issue with my I think this might be an issue in org. The only thing I can could find online was this https://www.mail-archive.com/[email protected]/msg102743.html which seems to be recent. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, this commit is recently, that's why I didn't see the error when I was inspecting Org sources on my machine. And to be honest, it doesn't look like this commit introduces the issue. This commit simply reveals the fact that there is an issue. Where? That's a good question. And I don't know 😸 I will upgrade my Org to see if I can reproduce and debug. Meanwhile you can try disabling some bits of your configurations to see if it makes any difference. For example, |
Beta Was this translation helpful? Give feedback.
-
|
This suggestion did help. It looks like it was an issue internal to This isn't my exact issue, just strange this popped up with your blog functions. But seems close enough. |
Beta Was this translation helpful? Give feedback.
-
|
The issue will pop even if you remove code taken from my blog post. Usually (and by default) people display category inside their agenda, which requires |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I see. Then I'm wondering what the best solution is for me now. (category (org-get-category))to (category (if (c-major-mode-is 'org-mode) (org-get-category) nil))This kinda patches the bug for me, and my org-agenda view is broken or looking bad. But like you said, at any point something else can fail with this related issue. I've now even seen some other errors being logged when using org-ref-captures. I'm not sure if this is the best way to fix this. Or if using |
Beta Was this translation helpful? Give feedback.
-
|
If you want to check which major-mode is enabled, there a variable named The thread you linked actually provided a good workaround - stick to Org 9.4 if you wish to use super agenda. I don't use that package and I am not familiar with it so I have zero insights on what else can be broken by using it together with 9.5. |
Beta Was this translation helpful? Give feedback.
-
I'll post my stack trace below.
This only occurs with my Org-Agenda "today" view, and no other views. The error from org is
org-element-at-point: 'org-element-at-point' cannot be used in non-Org buffer #<buffer *Org Agenda*> (org-agenda-mode)I'm using Vulpea like to update my org-agenda-files list.
You can see my config at https://github.com/DominikMendel/Doom-Emacs
It's a mess at the moment in some spots, and a little outdated from what I'll running. I'll make sure it's up to date tonight, but the Vulpea logic and Org-Agenda logic hasn't changed.
Stack trace
Beta Was this translation helpful? Give feedback.
All reactions