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

Showing the section name for an empty section? #236

Closed
PaddyPatPat opened this issue Dec 14, 2022 · 9 comments
Closed

Showing the section name for an empty section? #236

PaddyPatPat opened this issue Dec 14, 2022 · 9 comments
Assignees
Labels
Milestone

Comments

@PaddyPatPat
Copy link

Hi there,
The past issues have dealt a few times with hiding empty sections/groups. I am wondering if the opposite is possible?

I have grouped NEXT actions for each of my projects, with each project displayed in its own section. Where I see an empty section (no NEXT action) I know that I need to go select a TODO to make into a NEXT action. However at the moment empty sections do not show their name.

I see that there is org-super-agenda-hide-empty-groups which I thought might help but that this is off by default.

Is there a way that I can have org-super-agenda display the name of an empty section even if it is empty?

@alphapapa
Copy link
Owner

However at the moment empty sections do not show their name.

I see that there is org-super-agenda-hide-empty-groups which I thought might help but that this is off by default.

Well, you can see where that option was added in fd08d0b, discussed in #56 and #77. If the option is disabled but empty groups aren't being shown, that would seem like a bug, and I would guess that something has changed in a newer version of Org that you may be using, so please share that information. Maybe @cslux will be able to help debug it. Thanks.

@alphapapa alphapapa added the bug label Dec 15, 2022
@alphapapa alphapapa added this to the 1.3 milestone Dec 15, 2022
@PaddyPatPat
Copy link
Author

Ah yes of course. Thank you @alphapapa (and @cslux).

To answer your question:
Org mode version 9.6 ( @ /Users/patrick/.emacs.d/elpa/org-9.6/)
GNU Emacs 28.2 (build 1, x86_64-apple-darwin21.6.0, NS appkit-2113.60 Version 12.6 (Build 21G115)) of 2022-09-25

@casch-at
Copy link
Contributor

I'll try to create a PR with a fix ( 🤞🏽 ) for it in the next couple days.

casch-at pushed a commit to casch-at/org-super-agenda that referenced this issue Dec 24, 2022
casch-at added a commit to casch-at/org-super-agenda that referenced this issue Dec 24, 2022
casch-at added a commit to casch-at/org-super-agenda that referenced this issue Dec 24, 2022
casch-at added a commit to casch-at/org-super-agenda that referenced this issue Dec 26, 2022
@casch-at
Copy link
Contributor

@PaddyPatPat Changing the value of org-super-agenda-header-properties to '(org-super-agenda-header t org-agenda-structural-header t) should fix it. Worked for me! Better solution would be, of course, to always set this "required" property. See #237 @alphapapa

@alphapapa alphapapa self-assigned this Sep 23, 2023
@alphapapa
Copy link
Owner

Finally fixed. Thanks to all.

@Martinsos
Copy link

Apologies if I got something wrong, but is it possible that this issue is back?

I have org 9.8-pre 1c98731d5, org-super-agenda 1.4-pre c07e354, emacs 29.4., vanilla config, and by default org-super-agenda-hide-empty-groups is set to nil, however empty groups are not shown (their title is not shown, it is as if that group never existed).

@alphapapa
Copy link
Owner

@Martinsos Sure, it's possible, especially if you're using a pre-release version of Org. You should probably check its commit history for commits related to the agenda and text properties. If you can find the problem, you can either propose a change upstream, or here, depending on the details.

@Martinsos
Copy link

@Martinsos Sure, it's possible, especially if you're using a pre-release version of Org. You should probably check its commit history for commits related to the agenda and text properties. If you can find the problem, you can either propose a change upstream, or here, depending on the details.

Thanks @alphapapa ! I have to admit I didn't opt-in to using pre-release version conciously -> I started using Elpaca recently and I am still lacking somewhat in knowledge both on its details + also emacs package management in general. I guess it just pulls in the latest release regardless of it being pre-release or "stable" release hm, I might want to make sure it doesn't do that. And thanks for the advice regarding commits, that is probably what I should do. Awesome, thanks again!

@casch-at
Copy link
Contributor

@Martinsos This issue returned indeed, see #254

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

No branches or pull requests

4 participants