search

fmoralesc / vim-tutor-mode

interactive tutorials for vim
84 stars 4 forks source link

[WIP] tutor#FollowHelp in favor of 'keywordprg' and K #23

Closed ghost closed 9 years ago

ghost commented 9 years ago

Some links are still broken, hence the WIP.

fmoralesc commented 9 years ago

So, @Pyrohh what was still missing from this? I'm feeling like this could be merged already. I plan to improve the tutor syntax this week, make it more similar to markdown's.

ghost commented 9 years ago

Some links are "broken", because they depended on the []() syntax, which K doesn't recognize. I fix later ok ok.

ghost commented 9 years ago

I plan to improve the tutor syntax this week, make it more similar to markdown's.

:+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1:

edit: :+1:

fmoralesc commented 9 years ago

I merged this into the devel branch, so we can have a release branch, the old master (I intend to open a PR for neovim to include the version in that branch) and a merging development one (devel).

ghost commented 9 years ago

Thanks bruv.

I merged this into the devel branch, so we can have a release branch, the old master (I intend to open a PR for neovim to include the version in that branch) and a merging development one (devel).

So you plan on doing development of tutor-mode in the neovim branch devel, which would periodically be merged into master? Not sure.

fmoralesc commented 9 years ago

The idea is to develop it here in the devel branch, and then periodically merge it into our master branch, which would then be merged into the neovim runtime. I want to consolidate the master branch here before we include the recent changes to the tutorials, basically, so I'd prefer to have this two step mechanism. Do you think it is a bad idea?

On Sat, May 9, 2015 at 4:39 PM, Michael Reed notifications@github.com wrote:

Thanks bruv.

I merged this into the devel branch, so we can have a release branch, the old master (I intend to open a PR for neovim to include the version in that branch) and a merging development one (devel).

So you plan on doing development of tutor-mode in the neovim branch devel, which would periodically be merged into master? Not sure.

— Reply to this email directly or view it on GitHub https://github.com/fmoralesc/vim-tutor-mode/pull/23#issuecomment-100535531 .

ghost commented 9 years ago

Ah I see. I think that's a good idea.

On May 9, 2015 3:52:10 PM EDT, Felipe Morales notifications@github.com wrote:

The idea is to develop it here in the devel branch, and then periodically merge it into our master branch, which would then be merged into the neovim runtime. I want to consolidate the master branch here before we include the recent changes to the tutorials, basically, so I'd prefer to have this two step mechanism. Do you think it is a bad idea?

On Sat, May 9, 2015 at 4:39 PM, Michael Reed notifications@github.com wrote:

Thanks bruv.

I merged this into the devel branch, so we can have a release branch, the old master (I intend to open a PR for neovim to include the version in that branch) and a merging development one (devel).

So you plan on doing development of tutor-mode in the neovim branch devel, which would periodically be merged into master? Not sure.

— Reply to this email directly or view it on GitHub

https://github.com/fmoralesc/vim-tutor-mode/pull/23#issuecomment-100535531 .

Reply to this email directly or view it on GitHub: https://github.com/fmoralesc/vim-tutor-mode/pull/23#issuecomment-100538540