How do I setup up my workflow? #40
-
So, I'm new to orgmode, as well as Currently I have the following local org_path = function(path)
local org_directory = '~/self'
return ('%s/%s'):format(org_directory, path)
end
local orgmode_config = {
org_agenda_files = org_path '**/*',
org_default_notes_file = org_path 'refile.org',
org_hide_emphasis_markers = true,
org_agenda_text_search_extra_files = { 'agenda-archives' },
org_agenda_start_on_weekday = false,
org_startup_indented = true,
org_log_into_drawer = 'LOGBOOK',
org_todo_keywords = { 'TODO(t)', 'PROGRESS(p)', '|', 'DONE(d)', 'REJECTED(r)' },
org_capture_templates = {
t = {
description = 'Refile',
template = '* TODO %?\nDEADLINE: %T',
},
w = {
description = 'Todo',
template = '* TODO %?\nDEADLINE: %T',
target = org_path 'todos.org',
},
j = {
description = 'Journal',
template = '* %?',
target = org_path 'journal.org',
datetree = { reversed = true },
},
},
mappings = {
prefix = '<leader>n',
},
}
return {
'nvim-orgmode/orgmode',
event = 'VeryLazy',
dependencies = {
{ 'nvim-orgmode/org-bullets.nvim' },
},
ft = { 'org', 'orgagenda' },
config = function()
require('orgmode').setup(orgmode_config)
end,
} However this is quite different from
Thank you for this cool project! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Hey there! The dailies extension makes use of separate files named by date. So if you want date functionality with org roam then you'd need to switch to its structure. However, the standard org roam nodes can be placed at file or heading level. So, you could leverage capture to create your journal entries, and add a properties drawer underneath with an ID. Then roam would be able to treat them as nodes.
Keep in mind calendar features or anything from dailies wouldn't work here. |
Beta Was this translation helpful? Give feedback.
Hey there! The dailies extension makes use of separate files named by date. So if you want date functionality with org roam then you'd need to switch to its structure.
However, the standard org roam nodes can be placed at file or heading level. So, you could leverage capture to create your journal entries, and add a properties drawer underneath with an ID. Then roam would be able to treat them as nodes.
Keep in mind calendar features or anything from dailies wouldn't work here.