Categories

[MattCantor]

First off, the new agenda custom commands are great. I'm wondering if we can configure the categories in the agenda view by designating a #+CATEGORY property, per this part of the orgmode spec?

[kristijanhusak]

Yes, you can filter by categories in all available views like this. You can either use org_agenda_category_filter_preset on all views, or you can pass it differently. Here's an example custom agenda command that will show only specific category in all views:

org_agenda_custom_commands = {
  m = {
    description= 'My agenda',
    types = {
      {
         type = 'agenda',
         org_agenda_category_filter_preset = 'mycategory'
      },
      {
         type = 'tags',
         org_agenda_category_filter_preset = 'mycategory'
      },
      {
         type = 'tags_todo',
		 -- alternative way to match category, only available in tags and tags_todo types
         match = 'CATEGORY="mycategory"'
      },
    }
  }
}

[MattCantor]

This functionality is great and I appreciate you taking the time to provide the example.

My question is about how the agenda items appear in the agenda view, rather than filtering. Specifically whether we can configure what is shown in the far left "category" column by including a #+category property. Rather than that column being populated based on the name of the file in which the agenda items appear resides.

[kristijanhusak]

Yes, you can configure category on file or headline level:
For example:

Or for headline:

#+category: filecategory

* TODO default task

* TODO my task
    :PROPERTIES:
    :CATEGORY: mycategory
    :END:

In this example, default task will appear with category filecategory, while my task will appear with mycategory.

[MattCantor]

Awesome. My problem was that I was creating categories with improper syntax.

Thank you!

[iordanisg]

Piggybacking on this, since I'm also struggling to understand how to leverage categories. If a headline has for example the following property set:

  :PROPERTIES:
  :CATEGORY: concert
  :END:

how can I match or filter it?

@kristijanhusak I can't reproduce the matching/filtering behaviour with the custom command you mentioned above.

[kristijanhusak]

Scheduled or deadline date should not have any effect for the tags_todo view.
Does your task appear in the regular agenda view?
Also, does it appear in the tags todo view when you match it (<leader>oa + M + Match: CATEGORY="concert") ?

[iordanisg]

Somehow it does for me 🤷!

In the regular agenda view, the task appears with a category inferred from the filename, i.e. it looks like orgmode ignores the category property I set for the task headline. Same thing happens when I try to match it. As soon as I remove the scheduled date or deadline, the category appears in the agenda view and I can then use it for matching.

[iordanisg]

OK, I think I managed to solve the mystery :)

So what happens is that when I capture a task with the default capture template, orgmode adds the timestamp. If I add the property drawer UNDER the timestamp, then the behaviour is what I described above. However, if I add the property drawer BEFORE the timestamp, everything works as expected!

[kristijanhusak]

Yes, I assumed you have incorrect syntax in your file. This is the order of things it needs to be:

1. Headline, for example: * TODO Headline
2. Deadline and/or scheduled date, for example: DEADLINE: <2025-01-20 Mon>
3. Properties drawer

If there are no deadline or scheduled date, property drawer needs to go on 2nd line.

[iordanisg]

Everything is clear now, thanks a lot @kristijanhusak! You've done a fantastic job with the plugin by the way!