Dynamically add files to `org_agenda_files`

[gzagatti]

Does this feature exist in Emacs orgmode core?

N/A

Orgmode link

No response

Feature value

I usually take project notes using org, and I will keep those notes in the project folder.

It would be useful to add or drop a particular folder from org_agenda_files whenever needed. That way we do not bloat the amount of notes parsed by the plugin and allow the user to focus on the notes she/he needs at the moment.

Additional context

My guess would be to create a lua function (maybe in my init.lua) that would:

1. change org_agenda_files
2. call Config:get_all_files
3. call File:reload().

Is that the way to go? Would I be missing something important?

[kristijanhusak]

If you keep your projects in some specific folder, you could just do this:

org_agenda_files = { '~/main-org-files/**/*', '~/projects/**/*' }

This can be potentially slow if you have a lot of projects with lots of files, and if you don't ignore some vendor folders like node_modules and such. For that, make sure to use wildignore (see :help 'wildignore')

Another potential solution (haven't tried it, might have some issues), is to have a project specific setup (see :help exrc), and just call the setup for each project:

require('orgmode').setup({
  org_agenda_files = {'/path/to/this/project/**/*.org'}
})

[aareman]

Would relative files work for you? In a project I have a readme.org or to do.org, I haven't tried it, but a relative path would mean your main agenda could be parsed and all local ones in the cwd

…

________________________________ From: Kristijan Husak ***@***.***> Sent: Wednesday, July 13, 2022 11:51:02 AM To: nvim-orgmode/orgmode ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [nvim-orgmode/orgmode] Dynamically add files to `org_agenda_files` (Issue #365) If you keep your projects in some specific folder, you could just do this: org_agenda_files = { '~/main-org-files/**/*', '~/projects/**/*' } This can be potentially slow if you have a lot of projects with lots of files, and if you don't ignore some vendor folders like node_modules and such. For that, make sure to use wildignore (see :help 'wildignore') Another potential solution (haven't tried it, might have some issues), is to have a project specific setup (see :help exrc), and just call the setup for each project: require('orgmode').setup({ org_agenda_files = {'/path/to/this/project/**/*.org'} }) — Reply to this email directly, view it on GitHub<#365 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACQDVVYSMYZNMHGZNGMHCQDVT3QWNANCNFSM53PECZUQ>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[gzagatti]

Thanks for the suggestions.

I have tried adding the ~/projects/**/* to the table, but I find that it just gets too messy when looking for files. Maybe I just need a better organization system.

I have also tried with relative paths, but then when I open vim from my home directory it just takes forever to load everything.

Anyway, I will explore further with the options above and maybe write a custom function. Once I have a solution that works for me, I will report back.

[kristijanhusak]

If you are opening nvim from the project folder (I do that 99.9% of the time), you can update your orgmode setup to this:

require('orgmode').setup({
  org_agenda_files = {'~/main-orgfiles', ('%s/*.org'):format(vim.fn.getcwd()) }
})

When you open up Neovim, it will additionally load all org files from the root project folder. If you need it nested, replace *.org with **/*.org, but that might cause some slowness, since it potentially goes through a lot of files.