-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Allow different cfg_{editor|pager}
config options for Markdown notes
#120
Comments
@pataquets I don't think this is necessary, because sncli is supposed create a tempfile with a filename extension depending on the type (.mkd for markdown and .txt for plain text). So your editor should automatically pick up the filetype=markdown for markdown notes, or you can run an autocmd based on the extension However I do notice there's a bug(?) where sncli will set the filetype based on |
@pataquets #122 may address your request, albeit in a slightly different way. Would you like to test it out? :) |
@swalladge : I didn't noticed the bug, as I was using the pager most of the time. But opening with However, I've noticed the extension I've stumbled on this, since I'm using bat as my pager, and it's not detecting |
Thanks. :)
I 100% agree. I just have a minor concern about backwards compatibility - I don't know how many users have scripts and such that depend on the |
Oops, meant to add: would you mind adding your comment to the PR just for records sake? Just so I'm not merging a new PR with no reviews or comments 😬 |
[...]
Me too. A PR open for a while seems like a nice compromise. |
@pataquets #123 :) |
Markdown notes may benefit from specific, customized pager and editor command, eg:
vim +'set ft=markdown'
. Somecfg_editor_markdown
configuration setting (with fallback tocfg_editor
if not present) might do.Alternatively, passing note flags as command-line parameters (as done with
{fname}
) would enable writing a script to solve this.The text was updated successfully, but these errors were encountered: