On Tue, May 04, 2010 at 06:23:42PM +0200, Dominik Zyla wrote:
> On Fri, Apr 30, 2010 at 02:34:11PM -0700, el...@spinics.net wrote:
> > On Fri, 30 Apr 2010 14:22:13 -0700, Kwan Lowe
> > wrote:
> >
> > > Check filesystems for space? Temp dir? Maybe try cleaning out your
> > > .vimrc to see if so
On Fri, Apr 30, 2010 at 02:34:11PM -0700, el...@spinics.net wrote:
> On Fri, 30 Apr 2010 14:22:13 -0700, Kwan Lowe
> wrote:
>
> > Check filesystems for space? Temp dir? Maybe try cleaning out your
> > .vimrc to see if some cruft in it? Also check /etc/vimrc for
> > changes.. Maybe even re-inst
On Fri, 30 Apr 2010 14:22:13 -0700, Kwan Lowe
wrote:
> Check filesystems for space? Temp dir? Maybe try cleaning out your
> .vimrc to see if some cruft in it? Also check /etc/vimrc for
> changes.. Maybe even re-install or check to see if the packages have
> been corrupted?
Check inode availab
>Same versions as me.
>
>Check filesystems for space? Temp dir? Maybe try cleaning out your
>.vimrc to see if some cruft in it? Also check /etc/vimrc for
>changes.. Maybe even re-install or check to see if the packages have
>been corrupted?
All the systems exhibit, space is good etc. Even w/o a
On Fri, Apr 30, 2010 at 5:02 PM, Joseph L. Casale
wrote:
>>Nothing jumps out.. What specific version are you running? selinux enabled?
>
> vim-enhanced-7.0.109-6.el5
> vim-common-7.0.109-6.el5
> vim-minimal-7.0.109-6.el5
>
> No selinux. Odd, it was working on all the systems until recently?
Same
>Nothing jumps out.. What specific version are you running? selinux enabled?
vim-enhanced-7.0.109-6.el5
vim-common-7.0.109-6.el5
vim-minimal-7.0.109-6.el5
No selinux. Odd, it was working on all the systems until recently?
___
CentOS mailing list
CentOS
On Fri, Apr 30, 2010 at 4:42 PM, Joseph L. Casale
wrote:
>>Can you dump your current configuration?
>
> Sure, on one machine:
>
> :set
> --- Options ---
[snip]
Nothing jumps out.. What specific version are you running? selinux enabled?
___
CentOS maili
>Can you dump your current configuration?
Sure, on one machine:
:set
--- Options ---
background=dark history=50 incsearch scrolloff=5
smartcase viminfo='20,"50 t_Sf=^[[3%dm
backup hlsearch nomodelineshowbreak=>
On Fri, Apr 30, 2010 at 4:11 PM, Joseph L. Casale
wrote:
>>Works for me.. Maybe you have backupdir set someplace else?? I just
>>tried with fully updated 4.8 and 5.5 systems..
>
> Odd, even with backupdir explicitly set, it doesn't make a copy?
> It's getting disabled someplace as strace doesn't i
>Works for me.. Maybe you have backupdir set someplace else?? I just
>tried with fully updated 4.8 and 5.5 systems..
Odd, even with backupdir explicitly set, it doesn't make a copy?
It's getting disabled someplace as strace doesn't indicate any
mention of it.
__
On Fri, Apr 30, 2010 at 3:13 PM, Joseph L. Casale
wrote:
> None of my CentOS servers that are up to date recognize :set backup?
> A strace shows no mention of it, the backup never gets created, what
> am I missing here, anyone know if something changed that affects the
> backup behavior?
Works fo
None of my CentOS servers that are up to date recognize :set backup?
A strace shows no mention of it, the backup never gets created, what
am I missing here, anyone know if something changed that affects the
backup behavior?
Thanks!
jlc
___
CentOS mailing
12 matches
Mail list logo