On Tue, 12 May 2009, Magnus Therning wrote:
And a quick guess, it looks like the new vim package puts its colors here:
/usr/share/vim/vim72/colors/
Any reason the old /usr/share/vim/ shouldn't be on the default runtimepath?
Looking at other distros it seems using /usr/share/vim/vimX is the
On Mon, May 11, 2009 at 08:50:02PM -0500, Dan McGee wrote:
And a quick guess, it looks like the new vim package puts its colors here:
/usr/share/vim/vim72/colors/
Any reason the old /usr/share/vim/ shouldn't be on the default runtimepath?
Addendum: *any* plugins installed do not work,
On Tue, May 12, 2009 at 2:19 AM, Tobias Kieslich tob...@justdreams.de wrote:
On Tue, 12 May 2009, Magnus Therning wrote:
And a quick guess, it looks like the new vim package puts its colors here:
/usr/share/vim/vim72/colors/
Any reason the old /usr/share/vim/ shouldn't be on the default
Since I can't reply to the dev mailing list thread:
On Tue, May 12, 2009 at 8:25 AM, Dan McGee dpmc...@gmail.com wrote:
On Tue, May 12, 2009 at 2:19 AM, Tobias Kieslich tob...@justdreams.de wrote:
On Tue, 12 May 2009, Magnus Therning wrote:
That means all plugins need to be rebuild and some
Dan McGee wrote:
On Mon, May 11, 2009 at 8:40 PM, Dan McGee dpmc...@gmail.com wrote:
On Tue, May 5, 2009 at 2:22 AM, Tobias Kieslich tob...@justdreams.de wrote:
Hi,
Finally, the new vi* packages are up. There will be a little migration
pain. For optimal results, I recommend to sudo rm
Kessia 'even' Pinheiro wrote:
Hi all,
Tobias, i`m without a machine, so, i can`t check the vim version. Did you
compile new vim with witch version of ruby?
It will be with ruby-1.8 because 1.9 is not in the repos yet... I am
waiting for the vi(m)'s to move out of [testing] before I do the
On Wed, 2009-05-06 at 07:54 -0300, André Ramaciotti wrote:
Hi,
Just a question about this new vi package. Am I the only one having
problems when openning UTF-8 files? I can't even type words with
diacritics or vi will abort. For example, try to create a file with
the following and then open
I was thinking more about the installation/recuperation process than
the daily usage, because it's not always possible to install vim in
such cases. That's why I was questioning only vi being in [core],
though having vim in [core] would add lots of dependencies, so I guess
it's better the way it
On Tue, May 5, 2009 at 12:49 PM, Thomas Bohn tho...@bohnomat.de wrote:
On 2009-05-05 19:20 +0200, tob...@justdreams.de wrote:
the current vi package is actually nvi, the purpose of that was to have a
smaller package for core that also would not stall any updates of
vim/gvim while vi sits in
cover the users who USE and EXPECT 'vim' but still type 'vi' (sigh)
couldn't we suggest them to make an alias ?
Le Mercredi 6 à 13:07, Jan de Groot a écrit :
On Wed, 2009-05-06 at 07:54 -0300, André Ramaciotti wrote:
Just a question about this new vi package. Am I the only one having
problems when openning UTF-8 files? I can't even type words with
diacritics or vi will abort. For example, try to create
Hi,
that can be done, sure, however I don't like the idea of having an
extra package conflict with a core one.
We could name the package nvi, call the binaries nvi and provide a
symlink that gets replace on installing vim but all this symlinking
stuff has proved itself to be error prone.
On Wed, May 6, 2009 at 3:15 PM, Pierre Chapuis catw...@archlinux.us wrote:
Le Wed, 6 May 2009 14:53:43 -0500,
Aaron Griffin aaronmgrif...@gmail.com a écrit :
Might be worth seeing if we can find a patch to fix the crash at least.
Patching might be a good idea, but if you just patch the crash
On Tue, 2009-05-05 at 15:11 +0200, bs wrote:
On Tue, May 5, 2009 at 9:22 AM, Tobias Kieslich tob...@justdreams.de wrote:
Hi,
Finally, the new vi* packages are up. There will be a little migration
pain. For optimal results, I recommend to sudo rm /usr/bin/{view/rview}
before you run sudo
On Tue, May 5, 2009 at 2:11 PM, bs bojan...@gmail.com wrote:
On Tue, May 5, 2009 at 9:22 AM, Tobias Kieslich tob...@justdreams.de wrote:
Hi,
Finally, the new vi* packages are up. There will be a little migration
pain. For optimal results, I recommend to sudo rm /usr/bin/{view/rview}
before
On Tue, 05 May 2009, bs wrote:
hello,
as a linux newbie i am a little confused about the sudo rm
/usr/bin/{view/rview} command. typing it with the {}s does not
work, file or directory not found. am i supposed to delete
/usr/bin/view (which is a link)? i am probably missing something very
On 2009-05-05 00:22 -0700, Tobias Kieslich wrote:
Finally, the new vi* packages are up.
Why not letting Vim replace nvi entirely, the Vim package looks kinda
ugly now.
Thomas
On Tue, May 5, 2009 at 12:20 PM, tob...@justdreams.de wrote:
the current vi package is actually nvi, the purpose of that was to have a
smaller package for core that also would not stall any updates of vim/gvim
while vi sits in testing.
Th vim package is not uglier then it used to be before,
18 matches
Mail list logo
