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
I like url-open better in that regard, because it works for opening HTTP URLs in all files.
But from follow-md-links I miss being also able to jump in the editor between the linked files e.g. [a relative path file](./../relative_path_file.md) using the same key as opening the browser HTTP URLs.
Considering url-open already handles MD HTTP URL pattern, would you be interested to implement switching in editor between the linked files functionality in url-open?
Or maybe facilitate some way for url-open and follow-md-links to work via the same keyboard shortcut?
The text was updated successfully, but these errors were encountered:
andis-sprinkis
changed the title
Feature: Following MD file path links
Feature: Following MD file path links (switching editor between the linked files)
Dec 17, 2023
It occurred to me that such functionality may be similar to vim.lsp.buf.definition method, which in editor jumps to the definition file of a symbol and similarly vim.lsp.buf.declaration. (The former works with the code module imports for example.) That's something to note if there is a wish to scale the pattern to other linked file types.
I previously used jghauser/follow-md-links.nvim plugin to open HTTP URLs in MD files.
I like
url-open
better in that regard, because it works for opening HTTP URLs in all files.But from
follow-md-links
I miss being also able to jump in the editor between the linked files e.g.[a relative path file](./../relative_path_file.md)
using the same key as opening the browser HTTP URLs.Considering
url-open
already handles MD HTTP URL pattern, would you be interested to implement switching in editor between the linked files functionality inurl-open
?Or maybe facilitate some way for
url-open
andfollow-md-links
to work via the same keyboard shortcut?The text was updated successfully, but these errors were encountered: