Georg Dahn wrote:
Simetimes C-R in Insert mode is very useful. I use it to
format articles automatically. I set 'noai' and 'tw=78'. But
for texts with many lines this fails. I use the file
vimtips.txt I downloaded from vim.org.
1. Open vimtips.txt
2. Do :set noai
3. Do :set tw=78
4.
Yakov wrote:
I'v began testing of VIM 7 rather late, so may be this is fixed
already but anyway folks from IRC knows nothing bout that fact.
I'v built vim7c04 on QNX632 and NetBSD with --enable-gui=gtk. When i
use :tabnew i got several tabs. That works but when im trying to
navigate throw
Gregory Margo wrote:
test49.vim assumes the binary is named 'vim'.
If the --with-vim-name option is used (such as --with-vim-name=vim7)
then test49 fails.
Here is a minor patch that makes test49 respect the VIMPROG environment
variable from the Makefile, falling back to the current
run: gvim .
on Windows at bottom it will say, eg: C:\ Illegal file name
on Solaris and Linux at the bottom it will say, eg: . is a directory
The Unix message is less confusing. Can this for Windows versions as it
still occurs in vim7.0f? Same message appears when doing
:new .
Thanks
William
Hi!
Where do you find this vimtips.txt with 4 lines? I
only found one with 3543 lines.
http://www.vim.org/tips/tip_download.php?download=download
It contains a lot of empty lines, has a sice of a little
more then 1,2 MB, and has 40243 lines at the moment.
I tried another file but it
William S Fulton wrote:
run: gvim .
on Windows at bottom it will say, eg: C:\ Illegal file name
on Solaris and Linux at the bottom it will say, eg: . is a directory
The Unix message is less confusing. Can this for Windows versions as
it still occurs in vim7.0f? Same message appears when doing
[EMAIL PROTECTED] wrote:
All,
I found a bug related to syntax highlighting, although I wouldn't be
surprised if people already know about this. Simply, the syntax
highlighting sometimes gets messed up and I have to refresh the window
(with c-l) in order make the highlighting correct again.
I
Georg Dahn wrote:
Where do you find this vimtips.txt with 4 lines? I
only found one with 3543 lines.
http://www.vim.org/tips/tip_download.php?download=download
It contains a lot of empty lines, has a sice of a little
more then 1,2 MB, and has 40243 lines at the moment.
I
Matt Mzyzik wrote:
I found a bug related to syntax highlighting, although I wouldn't be
surprised if people already know about this. Simply, the syntax
highlighting sometimes gets messed up and I have to refresh the window
(with c-l) in order make the highlighting correct again.
I have
On Fri, Apr 28, 2006 at 04:08:32PM +0200, Nikolai Weibull wrote:
On 4/28/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I found a bug related to syntax highlighting, although I wouldn't be
surprised if people already know about this. Simply, the syntax
highlighting sometimes gets messed up and
Charles Campbell wrote:
William S Fulton wrote:
run: gvim .
on Windows at bottom it will say, eg: C:\ Illegal file name
on Solaris and Linux at the bottom it will say, eg: . is a directory
The Unix message is less confusing. Can this for Windows versions as
it still occurs in
[EMAIL PROTECTED] wrote:
On Fri, Apr 28, 2006 at 04:08:32PM +0200, Nikolai Weibull wrote:
On 4/28/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I found a bug related to syntax highlighting, although I wouldn't be
surprised if people already know about this. Simply, the syntax
Bram Moolenaar wrote:
Charles Campbell wrote:
William S Fulton wrote:
run: gvim .
on Windows at bottom it will say, eg: C:\ Illegal file name
on Solaris and Linux at the bottom it will say, eg: . is a directory
The Unix message is less confusing. Can this for Windows versions as
it still
William S Fulton wrote:
run: gvim .
on Windows at bottom it will say, eg: C:\ Illegal file name
on Solaris and Linux at the bottom it will say, eg: . is a directory
The Unix message is less confusing. Can this for Windows versions as
it still occurs in vim7.0f? Same message appears when
I identified which functions are slow and which are fast out of functions
called (load_dummy_buffer() + wipe_dummy_buffer()) pair.
As I wrote earlier this pair of functions is what slows down vimgrep,
not the search. The loop of 1000x (load_dummy_buffer() + wipe_dummy_buffer())
takes 30 seconds
Hi Yakov,
On 4/28/06, Yakov Lerner [EMAIL PROTECTED] wrote:
I identified which functions are slow and which are fast out of functions
called (load_dummy_buffer() + wipe_dummy_buffer()) pair.
As I wrote earlier this pair of functions is what slows down vimgrep,
not the search. The loop of 1000x
16 matches
Mail list logo