Skip to content
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

Add vim help documentation #48

Closed
wants to merge 1 commit into from
Closed

Conversation

michaelavila
Copy link

I figure, based on #13, that this might be a long shot, but I'm trying anyway. I'm integrating vim-gnupg into a particular aspect of my workflow and I am needing to look at the documentation often. This is made difficult by the fact that vim-gnupg does not have traditional documentation.

All I've done here is make a doc/gnupg.txt file that contains the same information as the Documentation section of the file plugin/gnpug.vim, only organized as a vim help document.

@jamessan
Copy link
Owner

Isn't this just duplicating the work already done in #13? I intend to merge that, but I've been letting the tail wag the dog some, as I need to fix another tool to better handle changes in an addon's file structure.

@michaelavila
Copy link
Author

Basically, that's why I said it might be a long shot. I needed the doc file so I created it without realizing there was a PR out. Checking #13 (and the date on #13), I figured that pushing up a branch with just the doc file might be an easier change to merge in. If it's not useful, it's not useful. I figured I'd PR just so you had access to commits that were relevant to the project, in the event that you needed them. Take care.

@jamessan jamessan modified the milestone: 2.7 Apr 24, 2016
@sukima
Copy link

sukima commented Dec 12, 2018

@jamessan I think at this point (almost five years) we can claim that—

I intend to merge that, but I've been letting the tail wag the dog some

—is officially inaccurate! PR #13 started in 2014 it is now almost 2019!

Is this project dead?

@jamessan
Copy link
Owner

Is this project dead?

The project is clearly not dead. I just haven't done anything in regard to this particular request, due to the exact reasoning I've already explained.

@jamessan
Copy link
Owner

jamessan commented Apr 9, 2019

#13 was merged, so I'm closing this.

@jamessan jamessan closed this Apr 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants