Closed oldenough closed 5 years ago
It's impossible for org-super-agenda
to cause this issue, because all it does is filter the result of org-agenda-finalize-entries
.
That is a lot of code to debug. Since it's not an issue with this package, please post it to somewhere like reddit.com/r/emacs or reddit.com/r/orgmode or the org-mode mailing list for help.
A day's worth of testing later, in a very limited init file the following line is where the windows set-up breaks.
(let ((org-super-agenda-groups
'((:auto-category t))))
(org-agenda-list))
And removing that line from a very large init file and everything is fine. I'm not even sure that that line is necessary and may just be a historic artifact, but it will take more testing to be sure that I haven't lost something with that line removed.
Then this line alone would cause it:
(org-agenda-list)
That function causes the agenda to be displayed. So every time you start Emacs, you're displaying the agenda somewhere, which is creating an agenda buffer, which probably alters the behavior of subsequent agenda invocations. It's nothing to do with org-super-agenda
.
Note this note from the readme:
Note: In order for groups to be automatically, persistently applied to all agenda buffers, the variable org-super-agenda-groups must be set in the global scope (e.g. with setq in your init file, or using the customization interface). Alternatively, it can be let-bound in lisp code that calls org-agenda commands, but in that case, the setting will not persist across agenda commands (so after refreshing an agenda buffer by pressing g, there will be no groups).
It appears that you copied the example let
form into your config, which is only intended as an example for testing this package's behavior, rather than setting the org-super-agenda-groups
variable with setq
. This is a common mistake by users who aren't as familiar with Lisp, which I've had to answer here many times, and I don't know how to solve it. Emacs and Org sometimes require some minimal Lisp knowledge to configure properly.
Since the problematic code appears right at the top of my org-super-agenda customization it was possibly part of some of my first experiments with the package (maybe 4 years ago?), which is the most important org package I use. That's why I think it's existence here is probably a historical artifact in my init file. I do use setq and org-super-agenda-groups clumsily but correctly a bit further down. The only time I do use Lisp is when I have to work on my init file, but I have been using org-mode for such a long time, I have learned to understand it a bit.
I am using Emacs 26.3 and org-super-agenda 20190925.958, although the problem applies to older versions of each. I am running Windows 10.
I wanted to open emacs full screen with two windows, showing my todo.org on the left and my Agenda on the right. The following code in the init file accomplishes that.
If I only add:
(use-package org-super-agenda :config (org-super-agenda-mode))
to the init file the windows definition code continues to work correctly.However, once I add in the code for the custom commands and formatting which I will include at the bottom of this, the windows definition code breaks and I wind up with the super-agenda view at the top, reaching across the entire Emacs window, and with two windows below that, divided vertically. Both of those windows show the todo.org file.
I set up the super-agenda formatting several years ago, and most of it is from the documentation examples although I'm not great at writing the stuff myself and wouldn't be surprised if I have added errors or non-functional items.
The question is what, in either super-agenda, or the formatting of it included in my init file, is breaking the setting up of the emacs windows and opening views, and is there anything that I can do about it?
Formatting code from init file. I have x'ed out some names and tags that contain personal information.