You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Obsidian uses the .obsidian directory to store configuration values as JSON files.
Many of the configuration options in obsidian.nvim are sourceable from these configuration files. Some examples:
daily_notes table can be filled in from .obsidian/daily-notes.json. In my setup I see the folder and template keys at least.
new_notes_location is defined by newFileLocation in .obsidian/app.json (value of folder seems to correspond to notes_subdir), as well as notes_subdir which corresponds to newFileFolderPath.
templates table can be filled in from .obsidian/templates.json. E.g. the folder key can be set from the folder property in the JSON file.
It would be incredible to be able to fill these in with the configuration that Obsidian uses since then one would not need to redefine these settings twice, once for the plugin and another time for Obsidian itself.
In order to not be too intrusive, this could potentially be an option enabled per-workspace, something such as read_config_from_obsidian = true for each item in workspaces.
Alternatives
The alternative is to duplicate these configurations on both the obsidian settings side as well as obsidian.nvim configurations, which this feature request aims to avoid.
Additional context
No response
The text was updated successfully, but these errors were encountered:
🚀 The feature, motivation and pitch
Obsidian uses the
.obsidian
directory to store configuration values as JSON files.Many of the configuration options in
obsidian.nvim
are sourceable from these configuration files. Some examples:daily_notes
table can be filled in from.obsidian/daily-notes.json
. In my setup I see thefolder
andtemplate
keys at least.new_notes_location
is defined bynewFileLocation
in.obsidian/app.json
(value offolder
seems to correspond tonotes_subdir
), as well asnotes_subdir
which corresponds tonewFileFolderPath
.templates
table can be filled in from.obsidian/templates.json
. E.g. thefolder
key can be set from thefolder
property in the JSON file.It would be incredible to be able to fill these in with the configuration that Obsidian uses since then one would not need to redefine these settings twice, once for the plugin and another time for Obsidian itself.
In order to not be too intrusive, this could potentially be an option enabled per-workspace, something such as
read_config_from_obsidian = true
for each item inworkspaces
.Alternatives
The alternative is to duplicate these configurations on both the obsidian settings side as well as
obsidian.nvim
configurations, which this feature request aims to avoid.Additional context
No response
The text was updated successfully, but these errors were encountered: