-
Notifications
You must be signed in to change notification settings - Fork 644
Add support for Markdown link extensions #529
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
Conversation
Merging this would finally make it possible to view and edit vimwiki in an android app (markor). For anyone who wants to migrate here are two unreadable sed scripts:
This may eat your data, don't use it if you don't understand it and don't blame me. Should be executed in the
|
I've been using this for some time. It has really helped with my iOS workflow. However, I think it can't be merged until other functions are changed as well. I haven't tried many, but |
It's fairly rare that I use the support functions directly - do you have an
idea of what else needs to change? I'm happy to amend the commit.
…On Thu, Oct 11, 2018 at 1:15 PM elliottw ***@***.***> wrote:
I've been using this for some time. It has really helped with my iOS
workflow. However, I think it can't be merged until other functions are
changed as well. I haven't tried many, but VimwikiGenerateLinks still
produces old style links that do not have extensions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#529 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFtLiIfkqdR3gmRVqI06NUINYlHBF2RIks5uj4qxgaJpZM4VM5ll>
.
|
It's rare that I use them too. I'm just hypothesizing that these changes couldn't be merged if they produce links that are inconsistent with the links that support functions create. I'm not sure what other functions would need changes, probably a search for all functions that create links would be a good start. |
@sstallion Did you ever look into which functions need modifed such as |
Hey Rane - I haven't. I'll try and take a look this weekend and see if I
can nail down what needs to change.
…On Mon, Mar 11, 2019 at 4:56 PM Rane Brown ***@***.***> wrote:
@sstallion <https://github.com/sstallion> Did you ever look into which
functions need modifed such as VimwikiGenerateLinks
I've been added as a maintainer and I'm looking into getting this merged
in.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#529 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFtLiFHnOrHyZ3DqV3mP7sMHNjocGKFNks5vVtEXgaJpZM4VM5ll>
.
|
So I think there are 3 issues that need addressed:
Let me know if you see anything else when you get a chance to look at it. |
@sstallion when you get a chance to work on this some more please make the pull request against the \ 'markdown_link_ext': {'type': type(0), 'default': 0, 'min': 0, 'max': 1}, We are working to make the contributing guidelines more accessible and clear but for now they are only stored on the |
@ranebrown PR should be ready to go - this should cover the cases mentioned. I wasn't able to come up with anything else, but I'm happy to take a look if any issues are reported. |
@sstallion I just tried to test your changes and things aren't working as expected. Following links does not seem to work correctly and the TOC is broken. I haven't had time to look at the code yet. Are all the commands and general behavior working as expected for you? |
That's strange. Which syntax are you using?
…On Tue, Mar 19, 2019 at 9:23 AM Rane Brown ***@***.***> wrote:
@sstallion <https://github.com/sstallion> I just tried to test your
changes and things aren't working as expected. Following links does not
seem to work correctly and the TOC is broken. I haven't had time to look at
the code yet.
Are all the commands and general behavior working as expected for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#529 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFtLiIzQkP3xg2D0uaztZYLrtqkn73Tfks5vYPLvgaJpZM4VM5ll>
.
|
Scratch that. You're absolutely right, TOC's are broken. I must have
botched that in a later change. I'll submit a fix shortly.
…On Tue, Mar 19, 2019 at 8:43 AM Steven Stallion ***@***.***> wrote:
That's strange. Which syntax are you using?
On Tue, Mar 19, 2019 at 9:23 AM Rane Brown ***@***.***>
wrote:
> @sstallion <https://github.com/sstallion> I just tried to test your
> changes and things aren't working as expected. Following links does not
> seem to work correctly and the TOC is broken. I haven't had time to look at
> the code yet.
>
> Are all the commands and general behavior working as expected for you?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#529 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AFtLiIzQkP3xg2D0uaztZYLrtqkn73Tfks5vYPLvgaJpZM4VM5ll>
> .
>
|
No worries. I think some other things besides the TOC had issues as well such as the diary links. Try to test with different variations such as spaces in the link/header name etc. |
@ranebrown Give this a shot - it looks like I was a bit overzealous with checking links in the last changeset. I double checked VimwikiTOC, VimwikiCheckLinks, diaries, and link navigation - all seems to be working correctly. |
Seems good now! I'm going to spend a bit more time looking this over tonight and get it merged if I don't see any other issues. |
SGTM. Thanks!
…On Tue, Mar 19, 2019 at 4:23 PM Rane Brown ***@***.***> wrote:
Seems good now! I'm going to spend a bit more time looking this over
tonight and get it merged if I don't see any other issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#529 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFtLiOx9kN06ex2LgMXJVrjJnBFeUvVMks5vYVVggaJpZM4VM5ll>
.
|
As of commit 7d82c75, vimwiki adds extensions to links created by vimwiki. This is important for use with other programs, such as Markor. See vimwiki/vimwiki#529
Does anybody know when this can be expected to make it into the master branch? |
For those trying to use this you need: let g:vimwiki_markdown_link_ext = 1 in your .vimrc |
This is awesome. Thank you! |
This PR is an updated version of #204, which adds support for appending file extensions in Markdown links. This is needed to view wiki files using Markdown viewers such as Gollum and MDwiki. By default, existing behavior is preserved.