Closed michaelavila closed 5 years ago
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.
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 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?
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.
I figure, based on https://github.com/jamessan/vim-gnupg/pull/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 thatvim-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 fileplugin/gnpug.vim
, only organized as a vim help document.