Being a Vim user and having just moved to Arch I noticed that most (all?) packages for Vim plugins install system wide. This may not be desirable since it means all users get all the plugins, and not using pacman for plugins puts the burden of keeping up-to-date on the individual users.
So, inspired by Debian's vim-additions-manager, I came up with a (fairly) light-weight solution: vim-scripts-mgr[1]. It looks for available Vim plugins in `/usr/share/vim-scripts` (one directory per plugin) and can install and uninstall individual plugins by adding symbolic links in ~/.vim for a user.
I've already uploaded two Vim plugins that make use of it, Align[2] and haskellmode[3].
I'd be thrilled if others who package Vim plugins would consider using it.
/M
[1]: http://aur.archlinux.org/packages.php?ID=26318 [2]: http://aur.archlinux.org/packages.php?ID=26319 [3]: http://aur.archlinux.org/packages.php?ID=26343
Sounds like a nifty idea.
-AT
On Sun, May 10, 2009 at 3:04 AM, Magnus Therning magnus@therning.org wrote:
Being a Vim user and having just moved to Arch I noticed that most (all?) packages for Vim plugins install system wide. This may not be desirable since it means all users get all the plugins, and not using pacman for plugins puts the burden of keeping up-to-date on the individual users.
So, inspired by Debian's vim-additions-manager, I came up with a (fairly) light-weight solution: vim-scripts-mgr[1]. It looks for available Vim plugins in `/usr/share/vim-scripts` (one directory per plugin) and can install and uninstall individual plugins by adding symbolic links in ~/.vim for a user.
I've already uploaded two Vim plugins that make use of it, Align[2] and haskellmode[3].
I'd be thrilled if others who package Vim plugins would consider using it.
/M
-- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe
On 05/10/2009 11:31 AM, Andrei Thorp wrote:
Sounds like a nifty idea.
-AT
On Sun, May 10, 2009 at 3:04 AM, Magnus Therning magnus@therning.org wrote:
Being a Vim user and having just moved to Arch I noticed that most (all?) packages for Vim plugins install system wide. This may not be desirable since it means all users get all the plugins, and not using pacman for plugins puts the burden of keeping up-to-date on the individual users.
So, inspired by Debian's vim-additions-manager, I came up with a (fairly) light-weight solution: vim-scripts-mgr[1]. It looks for available Vim plugins in `/usr/share/vim-scripts` (one directory per plugin) and can install and uninstall individual plugins by adding symbolic links in ~/.vim for a user.
I've already uploaded two Vim plugins that make use of it, Align[2] and haskellmode[3].
I'd be thrilled if others who package Vim plugins would consider using it.
/M
-- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe
What the hell... what's with the crazy font??
Daniel J Griffiths wrote:
On 05/10/2009 11:31 AM, Andrei Thorp wrote:
Sounds like a nifty idea.
[..]
What the hell... what's with the crazy font??
I hope you aren't referring to my font :-)
Andrei's font struck me as weird as well, but then I've seen worse working in a M$ shop so I didn't reflect too much over it :-)
/M
Uh... what are you people on about? I'm sending these e-mails in plain text via gmail (no HTML formatting or anything afaik.) I also don't see any strange fonts.
-AT
On Sun, May 10, 2009 at 4:23 PM, Magnus Therning magnus@therning.org wrote:
Daniel J Griffiths wrote:
On 05/10/2009 11:31 AM, Andrei Thorp wrote:
Sounds like a nifty idea.
[..]
What the hell... what's with the crazy font??
I hope you aren't referring to my font :-)
Andrei's font struck me as weird as well, but then I've seen worse working in a M$ shop so I didn't reflect too much over it :-)
/M
-- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe
On Mon, 11 May 2009 08:38, Andrei Thorp wrote:
Uh... what are you people on about? I'm sending these e-mails in plain text via gmail (no HTML formatting or anything afaik.) I also don't see any strange fonts.
-AT
I guess it's because your emails are being encoded with iso-2022-jp, instead of us-ascii or utf-8. That might mess with the font selected by GTK.
Either way, mutt displays everything just fine. :P
Regards, -- Ricardo Martins * ricardomartins.cc * GPG key: 0x1308F1B4
Ah, I see. I've changed the setting in gmail to always use UTF-8. Guess that should take care of it.
(Fyi, I use mutt et al at work, but I find it too convenient to have a well maintained online mailbox that I can access in many places)
-AT
On Mon, May 11, 2009 at 9:38 AM, Ricardo Martins ricardo@scarybox.net wrote:
On Mon, 11 May 2009 08:38, Andrei Thorp wrote:
Uh... what are you people on about? I'm sending these e-mails in plain text via gmail (no HTML formatting or anything afaik.) I also don't see any strange fonts.
-AT
I guess it's because your emails are being encoded with iso-2022-jp, instead of us-ascii or utf-8. That might mess with the font selected by GTK.
Either way, mutt displays everything just fine. :P
Regards,
Ricardo Martins * ricardomartins.cc * GPG key: 0x1308F1B4
On Mon, 11 May 2009 10:05, Andrei Thorp wrote:
Ah, I see. I've changed the setting in gmail to always use UTF-8. Guess that should take care of it.
(Fyi, I use mutt et al at work, but I find it too convenient to have a well maintained online mailbox that I can access in many places)
-AT
What's wrong with mutt + offlineimap? That's what I use with my google apps mail account (this one). This way I can use both mutt and the webinterface. :)
Regards, -- Ricardo Martins * ricardomartins.cc * GPG key: 0x1308F1B4
Andrei Thorp wrote:
Ah, I see. I've changed the setting in gmail to always use UTF-8. Guess that should take care of it.
It does indeed :-)
/M
On Sun, May 10, 2009 at 5:04 AM, Magnus Therning magnus@therning.org wrote:
Being a Vim user and having just moved to Arch I noticed that most (all?) packages for Vim plugins install system wide. This may not be desirable since it means all users get all the plugins, and not using pacman for plugins puts the burden of keeping up-to-date on the individual users.
So, inspired by Debian's vim-additions-manager, I came up with a (fairly) light-weight solution: vim-scripts-mgr[1]. It looks for available Vim plugins in `/usr/share/vim-scripts` (one directory per plugin) and can install and uninstall individual plugins by adding symbolic links in ~/.vim for a user.
I've already uploaded two Vim plugins that make use of it, Align[2] and haskellmode[3].
I'd be thrilled if others who package Vim plugins would consider using it.
/M
This seems overly complicated if you ask me. Management of scripts in your home dir should be up to you (or some script), but system-wide stuff should install system-wide. I really hate the Debian idea of needing N steps to install software, instead of just 1 step.
If you ask me, a script that will manually download and install scripts from vim.org to your home dir is FAR superior to requiring additional steps beyond simply installing a package
On Mon, May 11, 2009 at 14:59, Aaron Griffin aaronmgriffin@gmail.com wrote:
This seems overly complicated if you ask me. Management of scripts in your home dir should be up to you (or some script), but system-wide stuff should install system-wide. I really hate the Debian idea of needing N steps to install software, instead of just 1 step.
If you ask me, a script that will manually download and install scripts from vim.org to your home dir is FAR superior to requiring additional steps beyond simply installing a package
Big +1 on this from me. KISS
Daenyth Blank wrote:
On Mon, May 11, 2009 at 14:59, Aaron Griffin aaronmgriffin@gmail.com wrote:
This seems overly complicated if you ask me. Management of scripts in your home dir should be up to you (or some script), but system-wide stuff should install system-wide. I really hate the Debian idea of needing N steps to install software, instead of just 1 step.
If you ask me, a script that will manually download and install scripts from vim.org to your home dir is FAR superior to requiring additional steps beyond simply installing a package
Big +1 on this from me. KISS
Sure, but KISS in what respect and for whom?
/M
Yeah, I guess it is more work for you :)
Anyway, so what don't you like about Mr. Griffin's proposal?
-AT
Andrei Thorp wrote:
Yeah, I guess it is more work for you :)
For me, in what role? As a vim user on an Arch system, or as a maintainer of packages for vim plugins?
For the 2nd I would of course not mind if other provide PKGBUILDs that install plugins so that vim-scripts-mgr picks them up.
Anyway, so what don't you like about Mr. Griffin's proposal?
His proposal is great, except that there is no running code :-)
I'd love to have vim go out and check for updates to plugins, similar to how firefox/thunderbird does, or have a package manager for vim, that I as a user can run to get updates or install new plugins. However, AFAIK neither exists at the moment, and I'm not the one to write either.
/M
Yeah, I guess it is more work for you :)
For me, in what role? As a vim user on an Arch system, or as a maintainer of packages for vim plugins?
In that I guess the idea was for you as the guy who wants to write a script that makes installation of vim plugins easy for users. You wanted input on your script, and the input was "would be better if it didn't rely on pacman".
-AT
Andrei Thorp wrote:
Yeah, I guess it is more work for you :)
For me, in what role? As a vim user on an Arch system, or as a maintainer of packages for vim plugins?
In that I guess the idea was for you as the guy who wants to write a script that makes installation of vim plugins easy for users. You wanted input on your script, and the input was "would be better if it didn't rely on pacman".
Yeah, I forgot about that aspect, mostly because writing it wasn't "work", it was fun :-)
That indeed was the input and now that Aaron pointed me to some scripts and plugins that actually exist I can see if I can act on that input.
/M
On Tue, May 12, 2009 at 1:28 PM, Magnus Therning magnus@therning.org wrote:
Andrei Thorp wrote:
Yeah, I guess it is more work for you :)
For me, in what role? As a vim user on an Arch system, or as a maintainer of packages for vim plugins?
For the 2nd I would of course not mind if other provide PKGBUILDs that install plugins so that vim-scripts-mgr picks them up.
Anyway, so what don't you like about Mr. Griffin's proposal?
His proposal is great, except that there is no running code :-)
I'd love to have vim go out and check for updates to plugins, similar to how firefox/thunderbird does, or have a package manager for vim, that I as a user can run to get updates or install new plugins. However, AFAIK neither exists at the moment, and I'm not the one to write either.
Actually there was one somewhere. Vim scripts have standard headers that specify the versions and script name and the like. Someone made a script to parse that and update, but I can't find it anywhere.
On Tue, May 12, 2009 at 2:29 PM, Aaron Griffin aaronmgriffin@gmail.com wrote:
On Tue, May 12, 2009 at 1:28 PM, Magnus Therning magnus@therning.org wrote:
Andrei Thorp wrote:
Yeah, I guess it is more work for you :)
For me, in what role? As a vim user on an Arch system, or as a maintainer of packages for vim plugins?
For the 2nd I would of course not mind if other provide PKGBUILDs that install plugins so that vim-scripts-mgr picks them up.
Anyway, so what don't you like about Mr. Griffin's proposal?
His proposal is great, except that there is no running code :-)
I'd love to have vim go out and check for updates to plugins, similar to how firefox/thunderbird does, or have a package manager for vim, that I as a user can run to get updates or install new plugins. However, AFAIK neither exists at the moment, and I'm not the one to write either.
Actually there was one somewhere. Vim scripts have standard headers that specify the versions and script name and the like. Someone made a script to parse that and update, but I can't find it anywhere.
http://www.vim.org/scripts/script.php?script_id=2613 http://www.vim.org/scripts/script.php?script_id=2444
Aaron Griffin wrote:
On Tue, May 12, 2009 at 2:29 PM, Aaron Griffin aaronmgriffin@gmail.com wrote:
On Tue, May 12, 2009 at 1:28 PM, Magnus Therning magnus@therning.org wrote:
Andrei Thorp wrote:
Yeah, I guess it is more work for you :)
For me, in what role? As a vim user on an Arch system, or as a maintainer of packages for vim plugins?
For the 2nd I would of course not mind if other provide PKGBUILDs that install plugins so that vim-scripts-mgr picks them up.
Anyway, so what don't you like about Mr. Griffin's proposal?
His proposal is great, except that there is no running code :-)
I'd love to have vim go out and check for updates to plugins, similar to how firefox/thunderbird does, or have a package manager for vim, that I as a user can run to get updates or install new plugins. However, AFAIK neither exists at the moment, and I'm not the one to write either.
Actually there was one somewhere. Vim scripts have standard headers that specify the versions and script name and the like. Someone made a script to parse that and update, but I can't find it anywhere.
http://www.vim.org/scripts/script.php?script_id=2613 http://www.vim.org/scripts/script.php?script_id=2444
Thanks. I also found http://www.vim.org/scripts/script.php?script_id=642 from a link on one of the pages you pointed me to above.
/M
On Tue, May 12, 2009 at 8:08 PM, Magnus Therning magnus@therning.org wrote:
Daenyth Blank wrote:
On Mon, May 11, 2009 at 14:59, Aaron Griffin aaronmgriffin@gmail.com wrote:
This seems overly complicated if you ask me. Management of scripts in your home dir should be up to you (or some script), but system-wide stuff should install system-wide. I really hate the Debian idea of needing N steps to install software, instead of just 1 step.
If you ask me, a script that will manually download and install scripts from vim.org to your home dir is FAR superior to requiring additional steps beyond simply installing a package
Big +1 on this from me. KISS
Sure, but KISS in what respect and for whom?
KISS is a design principle which applies to software development.
Simplicity refers to the design of your software solution, not to its usage by an user (that is user friendliness).
On Wed, May 13, 2009 at 8:30 AM, Xavier shiningxc@gmail.com wrote:
On Tue, May 12, 2009 at 8:08 PM, Magnus Therning magnus@therning.org wrote:
Daenyth Blank wrote:
On Mon, May 11, 2009 at 14:59, Aaron Griffin aaronmgriffin@gmail.com wrote:
This seems overly complicated if you ask me. Management of scripts in your home dir should be up to you (or some script), but system-wide stuff should install system-wide. I really hate the Debian idea of needing N steps to install software, instead of just 1 step.
If you ask me, a script that will manually download and install scripts from vim.org to your home dir is FAR superior to requiring additional steps beyond simply installing a package
Big +1 on this from me. KISS
Sure, but KISS in what respect and for whom?
KISS is a design principle which applies to software development.
Simplicity refers to the design of your software solution, not to its usage by an user (that is user friendliness).
It's a bit more than that, it's a general principle of avoiding complexity ( http://en.wikipedia.org/wiki/KISS_principle ), hence my question.
/M
aur-general@lists.archlinux.org