"A.J.Mechelynck" <[EMAIL PROTECTED]> writes:
> :silent unlet g:colors_name
> :hi clear Normal
> :set bg=dark
> :hi clear
> :syntax reset
>
> (i.e., forcing Vim to use its "dark" defaults) gives you
> "good-looking" colors reliably, then Vim had probably guessed wrong,
"A.J.Mechelynck" <[EMAIL PROTECTED]> writes:
> I don't know Emacs, but Vim comes bundled with a number of "standard"
> colorschemes (in $VIMRUNTIME/colors). Some are light, others are
> dark. Try them out (using ":colorscheme ", where is the
> filename without the .vim extension), maybe you'll fi
t in ~/.vim/colors). I am attaching, as a simple
> easy-to-understand example, the "almost-default" colorscheme I use in
> the GUI.
>
> Once you have written your own colorscheme, let's say
> ~/.vim/colors/reader.vim, invoke it by ":colorscheme reader".
Again.
[EMAIL PROTECTED] writes:
> I don't think I posted my commented note about 99 but it says if you
> use 99 it's supposed to cause the default (font) or foreground color
> to happen I'm not real sure of the notes vintage, but it appears to
> be from 2003
> # [HP 07/08/03 21:18 Using 99 means it us
"A.J.Mechelynck" <[EMAIL PROTECTED]> writes:
> 99 is not a normal color for a cterm (color terminals have mostly 8 or
> 16 colors, or maybe 8 background and 16 foreground) so maybe it
> doesn't give reliable results. Replace "ctermfg=99" by
> "ctermfg=DarkYellow" or "ctermfg=Brown" to get brown. O
"Yakov Lerner" <[EMAIL PROTECTED]> writes:
> Are you using hpterm here ? Is this some hpterm weirdness
> you're experiencing ? If not, which terminal is this ?
xterm
"A.J.Mechelynck" <[EMAIL PROTECTED]> writes:
> Well, if you get no enlightenment from running Vim with the "-D"
> switch then using "s" repeatedly at the ">" prompt to step through all
> lines of all scripts that get run during startup, then you might try
> ":verbose hi groupname" where "groupname
I found a solution... I have a section in vimrc like the code below.
I'm not really sure what all it does ... one of the drawbacks of just
stealing stuff from someone elses .vimrc... long ago.
If I comment out the line with the two asterisks, vim comes up like I
expect it to without the purple Sta
is wrong
here.
:echo &runtimepath Does show the new one being last but then:
:scriptnames shows one more file being read after zzz.vim:
1: /home/reader/.vimrc
2: /usr/local/share/vim/vim70/colors/peachpuff.vim
3: /usr/local/share/vim/vim70/syntax/syntax.vim
4: /usr/loca
"A.J.Mechelynck" <[EMAIL PROTECTED]> writes:
> Try running Vim as "vim -D" with your usual vimrc. Then when you see
> the ">" prompt, you may optionally run ":echo" commands to see what
> happens, then hit s (Step into) or n (Next line) until you see what
> goes wrong. (s steps into functions and
"Yakov Lerner" <[EMAIL PROTECTED]> writes:
>> Somewhere back down the thread `the case' became.. ok it reads
>> .vimrc.
>
> Then, is it time to change the thread subject then ?
>
>> So why do those settings not appear in the running vim.
>
> The following command:
> :verbose tabstop?
> w
"Yakov Lerner" <[EMAIL PROTECTED]> writes:
>> 1: /home/reader/.vimrc
>
> Case closed. It does read ~/.vimrc.
Somewhere back down the thread `the case' became.. ok it reads
.vimrc. So why do those settings not appear in the running vim.
"Yakov Lerner" <[EMAIL PROTECTED]> writes:
> Aha. It *is* trying to load .vimrc.
> Does ~/.vimrc appear in the output of :scriptnames command ?
>vim
>:scriptnames
The first line:
1: /home/reader/.vimrc
"Yakov Lerner" <[EMAIL PROTECTED]> writes:
> 1. Check your env. var. $VIMINIT.
> If VIMINIT is set, vim will skip ~/.vimrc
>
It shows blank so not set, and I've posted the output of
: echo $MYVIMRC
/home/reader/.vimrc
So it is appartently being sourc
is
overpowering my .vimrc eh?
Put one poster showed how to start vim with no sourcing of all that
guff. vim --noplugins .bashrc
Still get the purple modeline and not my settings.
And just for the record: alias |grep vim
alias vim='vim -c '\''source ~/.vimrc'\'''
And inside vim :echo $MYVIMRC
/home/reader/.vimrc
=
What the heck...
Marc Weber <[EMAIL PROTECTED]> writes:
> No idea what might cause this but you might try
> * adding alias gvim="gvim -c source ~/.vimrc"
I'm not using gvim. I work in X at home machine but even then I use
vim. But a lot of what I do is from a bash cmdline on remote
machines.
This: al
"Yakov Lerner" <[EMAIL PROTECTED]> writes:
>> What on earth is that all about. It doesn't appear to ever look for
>> ~/.vimrc.
>
> I suggest that you build vim from sources.
Ok, I tried that and I must say the new vim download pages are nice
and the new aap tool does the work.
However once I've
y whether your .vimrc could be sourced or not.
> The output of :version, which you attached,
I still get what appears to be 100 or more lines of this:
Searching for "/home/reader/.vim/syntax/syncolor.vim"
Searching for "/usr/share/vim/vimfiles/syntax/syncolor.vim&
First a large pile of files are sourced under:
finished sourcing /usr/share/vim/vimfiles/plugin/newmetadata.vim
Then I see this:
finished sourcing /usr/share/vim/vim70/plugin/zipPlugin.vim
Searching for "/usr/share/vim/vimfiles/after/plugin/**/*.vim"
Searching for "/home/reader/.vim/aft
\ set ve?
"" map z to act as a register selector eliminating the need to type
""
nnoremap z "z
" Make p in Visual mode replace the selected text with the "" register.
vnoremap p :let current_reg = @"gvdi=current_reg
" Don't use E
20 matches
Mail list logo
