really nice site! will read through..thanks!
On Tue, Apr 8, 2014 at 3:57 AM, Marc Weber marco-owe...@gmx.de wrote:
I've already said that most wolk reasonably well for most common use
cases.
Smaller differences are documented here (maybe this is incomplete):
I've already said that most wolk reasonably well for most common use
cases.
Smaller differences are documented here (maybe this is incomplete):
http://vim-wiki.mawercer.de/wiki/index.html
Try them all, and help keeping that page up to date.
Marc Weber
--
--
You received this message from the
forks:
any conclusions/progress about the discussion?
I just got a new PC and I'd like to try one of the plugin manager way to
start my vim journey on it.
previously I only did that manually in years.
On Thu, Mar 27, 2014 at 11:43 AM, Nikolay Pavlov zyx@gmail.com wrote:
On Mar 27, 2014
I meant folks...:)
On Mon, Apr 7, 2014 at 2:54 PM, ping song songpingem...@gmail.com wrote:
forks:
any conclusions/progress about the discussion?
I just got a new PC and I'd like to try one of the plugin manager way to
start my vim journey on it.
previously I only did that manually in
Excerpts from Steve Litt's message of Tue Mar 25 21:40:51 + 2014:
The VimOutliner project is basing their next installer on Pathogen, so
as a VimOutliner user, I'd love to see greater Vim support for Pathogen.
Why can't we collect those requirements and allow plugin managers to
implement
Excerpts from Nikolay Pavlov's message of Tue Mar 25 20:32:13 + 2014:
With VAM you can ask to update specific plugin only. Action update all
plugins for which there is a newer version available is exactly what VAM
does if you disallow using VCS sources (otherwise it may switch source
types
On Mar 27, 2014 7:31 PM, Marc Weber marco-owe...@gmx.de wrote:
Excerpts from Nikolay Pavlov's message of Tue Mar 25 20:32:13 + 2014:
With VAM you can ask to update specific plugin only. Action update all
plugins for which there is a newer version available is exactly what
VAM
does if
On Sunday, March 23, 2014 4:34:19 PM UTC+1, Bram Moolenaar wrote:
At some point Vim started supporting plugins. At that time it was fine
to add a plugin manually, it was a one-time thing. But now that there
are so many plugins and they get updated often, manually updating
plugins has become
Hi Marc,
On Tuesday, March 25, 2014 1:58:52 AM UTC+1, MarcWeber wrote:
Eg massive downvoting happend on the vam vim.sf.net plugin page for
whatever reason (drchip removed his plugins form vim.sf.net for a
similar reason). This is just a reminder for those who missed the
happenings in the
Ben Fritz wrote:
I think simple and easy runtime path management like Pathogen offers would
be a great addition to Vim and would not be very controversial. I
understand that all the other plugin managers build on top of something
like this to allow easier
Currently, the official 'canonical plugin source' is the scripts site on
vim.org. If you listen to the community, you will hear that some good
people avoid vim.org because it isn't up to standards. And I think
they're right. I am very sympathetic to vim.org being the canonical
source for
On Mar 25, 2014 2:27 PM, BPJ b...@melroch.se wrote:
Ben Fritz wrote:
I think simple and easy runtime path management like Pathogen offers
would be a great addition to Vim and would not be very controversial. I
understand that all the other plugin managers
dowvoting due to textfile
The main issue is lack of interaction. Getting down votings for unkown
reason is bad for everybody. So this hurts a lot IMHO. issue trackers
are a lot better, because they create a soft force improving /
documenting the issues.
The text file contains:
linux:
On Tuesday, March 25, 2014 1:05:03 PM UTC+1, MarcWeber wrote:
dowvoting due to textfile
The main issue is lack of interaction. Getting down votings for unkown
reason is bad for everybody. So this hurts a lot IMHO. issue trackers
are a lot better, because they create a soft force improving /
On 25 March 2014, Marc Weber marco-owe...@gmx.de wrote:
[...]
About github vs vim.sf.net: The best thing would be allowing @
vim.sf.net to just register a github url *and be done*. vim.sf.net
could then just forward to github generating a .zip file for download.
Simple change, but huge
@David me saying you're wrong: You're right. Thanks for facing me.
About APIs:
The main problem is that you cannot just access the gitub api, because
accessing the internet from PHP scripts is not allowed. Code like this
fails: echo file_get_contents('http://google.de');
from #sourceforge its
2014-03-25 11:33, Nikolay Pavlov skrev:
Please point where anybody said a word about automatic updating. VAM and
Vundle do not do this for sure.
Well excuse me for getting the impression from statements like
this from Ben in the mail I quoted:
Vundle and the rest take too much config for my
On Mar 25, 2014 10:07 PM, BPJ b...@melroch.se wrote:
2014-03-25 11:33, Nikolay Pavlov skrev:
Please point where anybody said a word about automatic updating. VAM and
Vundle do not do this for sure.
Well excuse me for getting the impression from statements like
this from Ben in the mail I
On Tue, 25 Mar 2014 11:27:19 +0100
BPJ b...@melroch.se wrote:
Ben Fritz wrote:
I think simple and easy runtime path management like Pathogen offers
would be a great addition to Vim and would not be very controversial.
The VimOutliner project is basing their
On 23 March 2014, ZyX zyx@gmail.com wrote:
[...]
A list of things I would expect from a plugin manager:
1. Installing plugins in a FHS-compatible fashion (i.e. in
/usr/share/vimfiles/…). Target directory must be configurable. Reason: to
respect package maintainers from various
To sum up:
If people would have known about this page this thread would have been
shorter:
http://vim-wiki.mawercer.de/wiki/topic/vim%20plugin%20managment.html
(just add your own comments if you think the article is incomplete, you can
edit without registering)
I'd like to remind that I posted
On Mar 24, 2014 11:08 AM, LCD 47 lcd...@gmail.com wrote:
On 23 March 2014, ZyX zyx@gmail.com wrote:
[...]
A list of things I would expect from a plugin manager:
1. Installing plugins in a FHS-compatible fashion (i.e. in
/usr/share/vimfiles/...). Target directory must be
On 24.03.14 10:17, Marc Weber wrote:
Anyway situation is as is - which is why I at least thought we could try to
provide a common interface so that at least install instructions could be
shared
https://bitbucket.org/vimcommunity/vim-pi/issue/91/common-interface-for-most-plugin-managers
That
Vundle appears to be popular
Regarding vundle: I'm no vundle user but I recently stumbled over this blog
entry while googling for something else:
http://gmarik.info/blog/2014/02/04/why-i-stopped-contributing-to-vundle
Given the commits list though, it seems vundle is still alive and kicking:
On 2014-03-24, Nikolay Pavlov wrote:
On Mar 24, 2014 11:08 AM, LCD 47 wrote:
On 23 March 2014, ZyX wrote:
13. Ability to list and remove unused plugins. Reason: it is just
convenient.
Low priority.
That would imply keeping stats about when each plugin is actually
On 24 March 2014, Gary Johnson garyj...@spocom.com wrote:
On 2014-03-24, Nikolay Pavlov wrote:
On Mar 24, 2014 11:08 AM, LCD 47 wrote:
On 23 March 2014, ZyX wrote:
13. Ability to list and remove unused plugins. Reason: it is
just convenient. Low priority.
That would
On Mar 24, 2014 10:19 PM, Gary Johnson garyj...@spocom.com wrote:
On 2014-03-24, Nikolay Pavlov wrote:
On Mar 24, 2014 11:08 AM, LCD 47 wrote:
On 23 March 2014, ZyX wrote:
13. Ability to list and remove unused plugins. Reason: it is just
convenient.
Low priority.
On 24 March 2014, Nikolay Pavlov zyx@gmail.com wrote:
On Mar 24, 2014 11:08 AM, LCD 47 lcd...@gmail.com wrote:
On 23 March 2014, ZyX zyx@gmail.com wrote:
[...]
13. Ability to list and remove unused plugins. Reason: it is just
convenient. Low priority.
That would imply
On Mar 24, 2014 10:53 PM, LCD 47 lcd...@gmail.com wrote:
On 24 March 2014, Nikolay Pavlov zyx@gmail.com wrote:
On Mar 24, 2014 11:08 AM, LCD 47 lcd...@gmail.com wrote:
On 23 March 2014, ZyX zyx@gmail.com wrote:
[...]
13. Ability to list and remove unused plugins. Reason: it is
On Mar 24, 2014 10:50 PM, LCD 47 lcd...@gmail.com wrote:
On 24 March 2014, Gary Johnson garyj...@spocom.com wrote:
On 2014-03-24, Nikolay Pavlov wrote:
On Mar 24, 2014 11:08 AM, LCD 47 wrote:
On 23 March 2014, ZyX wrote:
13. Ability to list and remove unused plugins.
On 2014-03-24, LCD 47 wrote:
On 24 March 2014, Gary Johnson wrote:
On 2014-03-24, Nikolay Pavlov wrote:
On Mar 24, 2014 11:08 AM, LCD 47 wrote:
On 23 March 2014, ZyX wrote:
13. Ability to list and remove unused plugins. Reason: it is
just convenient. Low priority.
On Mar 24, 2014 11:22 PM, Gary Johnson garyj...@spocom.com wrote:
On 2014-03-24, LCD 47 wrote:
On 24 March 2014, Gary Johnson wrote:
On 2014-03-24, Nikolay Pavlov wrote:
On Mar 24, 2014 11:08 AM, LCD 47 wrote:
On 23 March 2014, ZyX wrote:
13. Ability to list and
On Sunday, March 23, 2014 10:34:19 AM UTC-5, Bram Moolenaar wrote:
At some point Vim started supporting plugins. At that time it was fine
to add a plugin manually, it was a one-time thing. But now that there
are so many plugins and they get updated often, manually updating
plugins has
Excerpts from Gary Johnson's message of Mon Mar 24 18:19:54 + 2014:
How do you know whether or not a plugin is actually used?
VAM calls the command:
VAMUninstallNotLoadedPlugins (old name: UninstallNotLoadedAddons)
Thus VAM cannot and does not know - well - even VAM has an alternative
At some point Vim started supporting plugins. At that time it was fine
to add a plugin manually, it was a one-time thing. But now that there
are so many plugins and they get updated often, manually updating
plugins has become tedious.
I am wondering what Vim users like about plugin managers.
On Mar 23, 2014, at 11:34 AM, Bram Moolenaar b...@moolenaar.net wrote:
At some point Vim started supporting plugins. At that time it was fine
to add a plugin manually, it was a one-time thing. But now that there
are so many plugins and they get updated often, manually updating
plugins
I agree with this. It comes down to freedom of choice really. I see no
reason to continue Pathogen, it too depends on git and NeoBundle does
such a better job. The others have their own places though.
On 23/03/14 16:15, Michael Hernandez wrote:
On Mar 23, 2014, at 11:34 AM, Bram Moolenaar
I think it's best to have a vim built-in standardized/official plugin
manager.
for an ordinary user it's often confusing to choose between many options -
so better to have an official one (better have most features
centralized/integrated) to start with ...
On Sun, Mar 23, 2014 at 12:47 PM, ed
On Sun, Mar 23, 2014 at 8:47 AM, ed jones spong...@gmail.com wrote:
I see no reason to continue Pathogen, it too depends on git
How so?
c
--
Chris Lott ch...@chrislott.org
--
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are
Indirectly, I guess. There's still no reason to continue it.
On 23/03/14 17:04, Chris Lott wrote:
On Sun, Mar 23, 2014 at 8:47 AM, ed jones spong...@gmail.com wrote:
I see no reason to continue Pathogen, it too depends on git
How so?
c
--
Chris Lott ch...@chrislott.org
--
--
You received
Is it fine to have a choice of plugin managers, or is this causing a
headache (for users and/or for plugin writers). If yes, then we should
pick one plugin manager and retire the others.
I'm glad you picked this topic up.
I personally use simple shell scripts to keep the git repos up to
On 23 March 2014, ed jones spong...@gmail.com wrote:
On 23/03/14 17:04, Chris Lott wrote:
On Sun, Mar 23, 2014 at 8:47 AM, ed jones spong...@gmail.com wrote:
I see no reason to continue Pathogen, it too depends on git
How so?
Indirectly, I guess. There's still no reason to continue it.
On 23 March 2014 15:34, Bram Moolenaar b...@moolenaar.net wrote:
At some point Vim started supporting plugins. At that time it was fine
to add a plugin manually, it was a one-time thing. But now that there
are so many plugins and they get updated often, manually updating
plugins has become
On Sunday, March 23, 2014 7:34:19 PM UTC+4, Bram Moolenaar wrote:
At some point Vim started supporting plugins. At that time it was fine
to add a plugin manually, it was a one-time thing. But now that there
are so many plugins and they get updated often, manually updating
plugins has become
Hi Bram, et al.,
On Sun, Mar 23, 2014 at 08:34 AM PDT, Bram Moolenaar wrote:
BM
BM At some point Vim started supporting plugins. At that time it was fine
BM to add a plugin manually, it was a one-time thing. But now that there
BM are so many plugins and they get updated often, manually
On 3/23/14, 11:34 AM, Bram Moolenaar wrote:
At some point Vim started supporting plugins. At that time it was fine
to add a plugin manually, it was a one-time thing. But now that there
are so many plugins and they get updated often, manually updating
plugins has become tedious.
I am
On Mar 24, 2014 3:50 AM, Israel Chauca israelvar...@fastmail.fm wrote:
On 3/23/14, 11:34 AM, Bram Moolenaar wrote:
At some point Vim started supporting plugins. At that time it was fine
to add a plugin manually, it was a one-time thing. But now that there
are so many plugins and they get
47 matches
Mail list logo
