Hello, I am surprised by the interaction between org-agenda-files and customization behaviour.
- org-agenda-files can be directories, which are scanned for org files. This is set in my init.el config. - when another org file is added with org-agenda-file-to-front (C-c [) the directories in org-agenda-files are expanded to a list of files in in the customisation/custom.el file. - when later an org file is added to the directory it is not clear why it is not picked up, since it is now missing from the expanded list. Expected behaviour: a new org file added to a directory specified in org-agenda-files should be picked up by the agenda without needing to use org-agenda-file-to-front. But org-agenda-file-to-front should still be available for files not in that directory. I use this workaround instead of setq: (customize-save-variable 'org-agenda-files (cons bob-capture-directory bob-org-directories)) Maybe my workflow can be improved. A discussion of that is also appreciated. Best regards Robert
