Instead of using a global variable to check for a existing capture,
leverage the :org-roam plist property of the buffer-local variable
`org-roam-capture-current-plist`.
This prevents a lockout if the capture buffer is killed
Split functionality related to the org-roam-buffer into its own
feature/file.
Introduce `org-roam-buffer-prepare-hook' to allow customizations of the
org-roam-buffer content.
Co-authored-by: Jethro Kuan <jethrokuan95@gmail.com>
Change function name org-roam--setup-buffer org-roam--set-up-buffer.
Warn user and default to 'right when org-roam-buffer-position is
an invalid position.
Make better use of pcase to avoid repeating code.
org-roam-graph-node-extra-config is an alist containing additional node
configuration options, as per
https://graphviz.gitlab.io/_pages/doc/info/attrs.html
This also deprecates org-roam-graph-node-shape, which is a special case
of the node options
* Allow placement of the sidebar on top or on bottom
* Add "let_sidebar_be_on_top_or_bottom" to the changelog
* Remove an unnecessary progn and replace an if with a pcase
As requested by jethrokuan in https://github.com/jethrokuan/org-roam/pull/380
comments.
This is a hotfix for #369. Currently, calling `org-roam-capture` sets
`org-roam-capture--in-process` to `t`, but cancelling the capture
process does not reset it to `nil`, causing false errors. The whole
nested org-capture processes workaround is brittle, this change moves it
as far back as possible, but the whole thing needs to be redesigned.
This change makes `org-roam-open-at-point` non-interactive and adds it to
`org-open-at-point-functions`. As a consequence, `org-open-at-point` will try
to visit an Org-roam link or preview text, before falling back to the default
behavior of Org mode.
Fixes#312.
* ensure "%?" is present in the template string
- addresses #298
- fixes `org-capture-place-plain-text` throwing 'invalid search bound'
when both :unnarowed t and "%?" is missing from the template string
* ensure "%?" is present in the template string
- if "%?" is missing, add it at the end of the template
Removing hooks in a loop should be easier to extend/maintain.
More "DRY" than repeating calls to `remove-hook'.
Co-authored-by: Jethro Kuan <jethrokuan95@gmail.com>
