Shawn Walker writes:
> The problem is that you're setting syntax on *before* you set the
> value of t_Co. Move this:
>
> " Switch syntax highlighting on, when the terminal has colors
> " Also switch on highlighting the last used search pattern.
> if &t_Co > 2 || has("gui_running")
> syntax on
Harry Putnam wrote:
Harry Putnam writes:
Setup:
OS=Opensolaris 2008.11
vim=See full `:version output at the end
I think parts of this thread stayed on gmane.editors.vim or at least I
thought I saw a post here somewhere that asked me to post my vimrc.
In case anyone is still willing to help
Harry Putnam writes:
> Setup:
> OS=Opensolaris 2008.11
> vim=See full `:version output at the end
I think parts of this thread stayed on gmane.editors.vim or at least I
thought I saw a post here somewhere that asked me to post my vimrc.
In case anyone is still willing to help figure this out.
Sean Sprague writes:
You'd think it might be but if so then :so .vimrc would find the same
problem but it does not... It just works if I do a manual source.
>>> Can you post the contents of your .vimrc somewhere (like pastebin) ?
>>>
>>
>> Egad yes... I should have done
Harry Putnam wrote:
Shawn Walker writes:
Harry Putnam wrote:
Shawn Walker writes:
It looks like it's opening it just fine. So maybe there's a syntax
error in the file or something causing vim to ignore its contents?
What makes you believe it's being ignored?
You'
On 11/03/09 21:47, Harry Putnam wrote:
Shawn Walker writes:
What might cause ~/.vimrc to be ignored on vim start
It works fine on my system, but the file is owned by me, and it's not
a symlink.
It worked for me for a while too. But now it doesn't. To test, I
moved the actual actual file
Shawn Walker writes:
> Harry Putnam wrote:
>> Shawn Walker writes:
>>
>>> It looks like it's opening it just fine. So maybe there's a syntax
>>> error in the file or something causing vim to ignore its contents?
>>>
>>> What makes you believe it's being ignored?
>>
>> You'd think it might be bu
Harry Putnam wrote:
Shawn Walker writes:
It looks like it's opening it just fine. So maybe there's a syntax
error in the file or something causing vim to ignore its contents?
What makes you believe it's being ignored?
You'd think it might be but if so then :so .vimrc would find the same
pr
Shawn Walker writes:
> It looks like it's opening it just fine. So maybe there's a syntax
> error in the file or something causing vim to ignore its contents?
>
> What makes you believe it's being ignored?
You'd think it might be but if so then :so .vimrc would find the same
problem but it does
Harry Putnam wrote:
Brandon Hume writes:
On Wed, 2009-03-11 at 15:47 -0500, Harry Putnam wrote:
It worked for me for a while too. But now it doesn't. To test, I
moved the actual actual file into ~/ and as I showed in OP it belongs
to me.
What does truss tell you is happening?
ie: truss -o
Brandon Hume writes:
> On Wed, 2009-03-11 at 15:47 -0500, Harry Putnam wrote:
>> It worked for me for a while too. But now it doesn't. To test, I
>> moved the actual actual file into ~/ and as I showed in OP it belongs
>> to me.
>
> What does truss tell you is happening?
>
> ie: truss -o vim.tr
Lurie writes:
> Worked fine for me for all builds (now on b109), so you might want
> to simply copy it, instead of using a symlink.
Yes, of course I did that right away but it made no difference.
___
opensolaris-discuss mailing list
opensolaris-discus
On Wed, 2009-03-11 at 15:47 -0500, Harry Putnam wrote:
> It worked for me for a while too. But now it doesn't. To test, I
> moved the actual actual file into ~/ and as I showed in OP it belongs
> to me.
What does truss tell you is happening?
ie: truss -o vim.truss -f vim testfile
grep vimr
Harry Putnam wrote:
Shawn Walker writes:
But still it does not get sourced when I start vim on a file.
What build are you on? I'm using 106.
I´m on 108
I can only suggest you try trussing the process then to see if any
errors show up. I just updated to build 109 last night and it stil
Worked fine for me for all builds (now on b109), so you might want to simply
copy it, instead of using a symlink.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Harry Putnam schrieb:
> Setup:
> OS=Opensolaris 2008.11
> vim=See full `:version output at the end
>
> When I start vim on a file it does not source the ~/.vimrc file.
> That file is actually a symlink to the hard file elsewhere.
>
> Permissions are on both slink and hard copy:
> ls -l ~/.vimrc:
Shawn Walker writes:
>> But still it does not get sourced when I start vim on a file.
>
> What build are you on? I'm using 106.
I´m on 108
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Harry Putnam wrote:
Shawn Walker writes:
What might cause ~/.vimrc to be ignored on vim start
It works fine on my system, but the file is owned by me, and it's not
a symlink.
It worked for me for a while too. But now it doesn't. To test, I
moved the actual actual file into ~/ and as I show
Shawn Walker writes:
>> What might cause ~/.vimrc to be ignored on vim start
>
> It works fine on my system, but the file is owned by me, and it's not
> a symlink.
It worked for me for a while too. But now it doesn't. To test, I
moved the actual actual file into ~/ and as I showed in OP it belo
Harry Putnam wrote:
Setup:
OS=Opensolaris 2008.11
vim=See full `:version output at the end
When I start vim on a file it does not source the ~/.vimrc file.
That file is actually a symlink to the hard file elsewhere.
Permissions are on both slink and hard copy:
ls -l ~/.vimrc:
lrwxrwxrwx 1 reade
Setup:
OS=Opensolaris 2008.11
vim=See full `:version output at the end
When I start vim on a file it does not source the ~/.vimrc file.
That file is actually a symlink to the hard file elsewhere.
Permissions are on both slink and hard copy:
ls -l ~/.vimrc:
lrwxrwxrwx 1 reader staff 35 [...] /exp
21 matches
Mail list logo
