Hello everyone,
When I'm using plugins like taglist and NERDTree VIM has problems redrawing
the windows. When I move the caret the lines it moves over is redrawn but
it's a mess. Can I fix this somehow so that it is automatically redrawn?
-Martin
I've set up a function that at its core does this:
cexpr system(command that takes a long time to run)
Until the long-running process returns I can't interact with Vim --
which is fine and expected behaviour -- but I am wondering if there is
any way of displaying some kind of progress
Tony Mechelynck escribió:
On 25/01/09 02:00, Jesus Sanchez wrote:
Some time have passed since I started this thread. I will 'reuse' it to
discuss some things I've found on the net after some time searching
about the dark on light or light on dark dilema. The main points I
want talk are:
Hi Martin!
Am 25.01.2009 11:30, Martin Lundberg schrieb:
Hello everyone,
When I'm using plugins like taglist and NERDTree VIM has problems redrawing
the windows. When I move the caret the lines it moves over is redrawn but
it's a mess.
[...]
Is this reproducible? If so, how can you
On Sun, 2009-01-25 at 16:23 +0100, Jesus Sanchez wrote:
Very nice post, and very very complete. I agree (and think everyone
also
agree) the fact that the screens today still use the grey on black
theme for the terminals (tty ones and VGA modes) cause the history
repercusion about this. Also
On Sun, 25 Jan 2009, Jesus Sanchez wrote:
when we all talking about light, not paper. I still have problems cause
in my house all my family use my computer and they say white on black
sucks, and aslo is harder to read. After some discussions they still
don't accept the fact that light to the
bill lam escribió:
On Sun, 25 Jan 2009, Jesus Sanchez wrote:
when we all talking about light, not paper. I still have problems cause
in my house all my family use my computer and they say white on black
sucks, and aslo is harder to read. After some discussions they still
don't accept the
On 25/01/09 16:23, Jesus Sanchez wrote:
Tony Mechelynck escribió:
[...]
[Jesus Sanchez answered]
Very nice post, and very very complete. I agree (and think everyone also
agree) the fact that the screens today still use the grey on black
theme for the terminals (tty ones and VGA modes) cause
Hi,
I use a combination of Terminus font and Tango color scheme and I'm
quite happy with that. Here's a screenshot:
http://picasaweb.google.com/lh/photo/t0jKLsltJ7lQPp8eSwVkig?feat=directlink
I use Terminus in terminal as well, green-on-black.
--
Bohdan
On Dec 21 2008, 6:45 am, Jesus Sanchez
On Sat 24 Jan 2009 at 18:51:31 PST Jesus Sanchez wrote:
When I said colors are better identified with black backgrounds I was
trying to say that if you put a black square, inside that scuare you
put two lines of 1 pixel width. One line is a pure red and other line
is a little modification of pure
On Sun 25 Jan 2009 at 08:08:10 PST bill lam wrote:
After reading white-on-black for several hours, I found it is OK
except the blue on black combination. Since blue is dark blue
#ff on xterm. It is really hard to read. I have to use Xresource
to change color4 (blue) to #00aaff (lighter).
Hi, I know I am a little slow, but I can't find the reason for this.
I haven't been using vim Sessions because of a major annoyance that I
can't figure out and am hoping someone can tell me why this is
happening.
I have set the highlighting for comments to green in my ~/.vimrc:
hi Comment
Hello !
Thanks a lot. All works fine.
One's more question arises. Can I commit not only one file per
operation using vcsplugin ?
--
Best regards,
Sincerely yours,
Yuriy Rusinov.
--~--~-~--~~~---~--~~
You received this message from the vim_use maillist.
For
Saluton Charlie :)
On Sun, 25 Jan 2009 09:54:31 -0800, Charlie Kester dixit:
When working with text, being able to distinguish individual letters
and punctuation marks is usually more important than being able to
distinguish colors.
Difficult for me with or without syntax highlighting. Some
Saluton Tony :)
On Sun, 25 Jan 2009 19:37:30 +0100, Tony Mechelynck dixit:
On 25/01/09 18:35, Raúl Núñez de Arenas Coronado wrote:
[...]
And yes, the standard terminal color shades are ugly. Probably
they were chosen to provide shades which were as orthogonal as
possible between them,
Hi,
is there any way to have some kind of case insensitive iabbrev to have
it like this:
iabbrev integer INTEGER
so all words like these:
integER
Integer
INTeger
will be changed into INTEGER?
szymon
--~--~-~--~~~---~--~~
You received this message from the
sed 's/[iI][nN][tT][eE][gG][eE][rR]/INTEGER/g' input.txt output.txt
sed 's/integer/INTEGER/gI' input.txt output.txt
On Mon, Jan 26, 2009 at 1:11 AM, Szymon Guz mabew...@gmail.com wrote:
Hi,
is there any way to have some kind of case insensitive iabbrev to have
it like this:
iabbrev
2009/1/25 nishant porwal porwal.nish...@gmail.com:
sed 's/[iI][nN][tT][eE][gG][eE][rR]/INTEGER/g' input.txt output.txt
sed 's/integer/INTEGER/gI' input.txt output.txt
Yea, but this is the way to change whole file, I just want the iabbrev
behaviour, to change all while writing.
regards
Hi,
Whenever I try to open a .ps1 file (Powershell v1), Vim thinks it's a
conf filetype. By changing the filetype manually within Vim, the
correct syntax is used.
I've checked the docs and as far as I understand, the autocmds for
picking the right syntax should be taken care of by synload.vim,
One's more question arises. Can I commit not only one file per
operation using vcsplugin ?
Not, as far as I know.
But at least for me commit is comfortable enough from command
line: if you have EDITOR environment variable set to vim and
use svn commit file1 file2 path/to/file3 ... from
Guillermo wrote:
What's the correct way to tell Vim to load a
syntax/indent/ftplugin based on a file extension?
Our tip on this is:
http://vim.wikia.com/wiki/Filetype.vim
The tip gives too much detail before the simple things you want to know,
and incorrectly refers to %USERPROFILE% on
Richard Hartmann, 21.01.2009:
Hi all.
if I run
git blame foo.file | vim -
or
svn blame foo.file | vim -
I get the blame-annotated file in Vim. Is there a way to have the syntax
highlighting ignore the blame stuff and simply highlight the actual
code?
I'm not sure if
On 25/01/09 20:31, Raúl Núñez de Arenas Coronado wrote:
Saluton Tony :)
Salud Raúl / Saluton Raulo
Fortunately, we can choose between the two faces of Vim :) A pity that a
KDE face is not available, for KDE lovers.
GTK2/Gnome2 gvim meshes quite well with KDE (I know, I'm a KDE lover
On 25/01/09 20:23, Raúl Núñez de Arenas Coronado wrote:
[...]
Maybe we should start a good ol' flamewar to force everyone to use less
colors and simpler highlighting and to dominate the world, of course XD
Please don't. You wouldn't want me to blacklist you as a troll, would
you? ;-)
Raúl
Hi, Tony.
What you told was the solution I take. I removed the 'utf-16le' from
'fileencodings' option and now everything is working fine. You were right about
that my utf-16le files doesn't had a BOM start. So, now, when I need to read or
edit this kind of file in GVim I just use:
:e
I'm not sure if everybody is familiar with the blame output. Maybe you
have more chance of getting responses with an example.
blame is git's funny way of saying annotate.
There are several annotate-type syntax highlighting schemes for Vim (for
example, CVSAnnotate.vim and HGAnnotate.vim).
As one of those users using vi for the past 30 years, I have some
questions pertaining mainly to Vim 7.2.
I don't like changes in default behavior of certain programs. Vim7.2
is one. How can I turn off autoindent. In my .vimrc file, I have
set noautoindent and issued in comand mode :set
On 25/01/09 11:30, Martin Lundberg wrote:
Hello everyone,
When I'm using plugins like taglist and NERDTree VIM has problems
redrawing the windows. When I move the caret the lines it moves over is
redrawn but it's a mess. Can I fix this somehow so that it is
automatically redrawn?
-Martin
Paul McFerrin wrote:
As one of those users using vi for the past 30 years, I have some
questions pertaining mainly to Vim 7.2.
I don't like changes in default behavior of certain programs. Vim7.2
is one. How can I turn off autoindent. In my .vimrc file, I have
set noautoindent and
On 25/01/09 14:54, Wincent Colaiuta wrote:
I've set up a function that at its core does this:
cexpr system(command that takes a long time to run)
Until the long-running process returns I can't interact with Vim --
which is fine and expected behaviour -- but I am wondering if there is
Hi everyone,
How do I add .vim color schemes to vim?
Thanks,
Vim-noob
Ubuntu 8.10- vim 7.1
Sent via BlackBerry by ATT
-Original Message-
From: Tony Mechelynck antoine.mechely...@gmail.com
Date: Mon, 26 Jan 2009 06:56:32
To: vim_use@googlegroups.com
Subject: Re: Showing background
I was instructed to use:
vim -u NONE {file}
and that solved all three problems identified. I'm happy now that I
made vim an alias.
When I first noticed a problem, I did not have a .vimrc file; only the
global one in /usr/share/vib/...
- Pau
Charles E. Campbell, Jr. wrote:
Paul McFerrin
Hello,
It can be done if I have a separate file, but I want to do it all in
one plugin. I could not make it work by playing with iconv()
function.
My current workaround works, by manually getting unicode value from
different encoding.
if encoding == utf-8
let utf8_value = [ C-Vuff08,
On 2009-01-25, Paul McFerrin pmcfer...@columbus.rr.com wrote:
As one of those users using vi for the past 30 years, I have some
questions pertaining mainly to Vim 7.2.
I don't like changes in default behavior of certain programs. Vim7.2
is one. How can I turn off autoindent. In my
34 matches
Mail list logo
