Patch 7.0.095
Problem:The Greek tutor is not available in utf-8. el is used for the
language, only gr for the country is recognized.
Solution: Add the utf-8 Greek tutor. Use it for conversion to iso-8859-7
and cp737. (Lefteris Dimitroulakis)
Files:
Patch 7.0.096
Problem:taglist() returns the filename relative to the tags file, while
the directory of the tags file is unknown. (Hari Krishna Dara)
Solution: Expand the file name. (Yegappan Lakshmanan)
Files: src/tag.c
*** ../vim-7.0.095/src/tag.cThu Apr 27 23:40:34
This patch adds 'extrahuge' build size, which is
huge+interpreters (spelled as --with-features=extrahuge
or --with-features=allinterp).
Yakov
P.S. Maybe --with-features=max is better name.
patch-extrahuge
Description: Binary data
Patch 7.0.097
Problem::tabclose N that closes another tab page does not remove the tab
pages line. Same problem when using the mouse.
Solution: Adjust the tab pages line when needed in tabpage_close_other().
Files: src/ex_docmd.c
*** ../vim-7.0.096/src/ex_docmd.c
Bug? With
gvim -o3 file1.txt file2.txt file3.txt
only the first two are displayed in a window. (All 3 files exist.)
The arguments list is OK, since
:bot new
:last
opens the 3rd file in a 3rd window.
If the line
set noea wmh=0 wh=9 hh=9
(in my vimrc)
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Bug? With
gvim -o3 file1.txt file2.txt file3.txt
only the first two are displayed in a window. (All 3 files exist.)
The arguments list is OK, since
:bot new
:last
opens the 3rd file in a 3rd window.
If the line
I started using FreeBasic which uses the *.bas ending and was
wondering if:
1. Anyone is interested in me sending in the updated basic.vim file.
2. If this is the right mailing group to send it to.
Thanks!
Mark
Mark Manning wrote:
I started using FreeBasic which uses the *.bas ending and was
wondering if:
1. Anyone is interested in me sending in the updated basic.vim file.
2. If this is the right mailing group to send it to.
Thanks!
Mark
Normal procedure would be to first try contacting the
In the syntax stuff, the c.vim file should be changed to have the following:
Old:
syn regioncStringstart=++ skip=+\|\\+ end=++
contains=cSpecial
New
syn regioncStringstart=++ skip=+\||'+ end=++
contains=cSpecial
syn regioncStringstart=+'+
On 9/10/06, Mark Manning [EMAIL PROTECTED] wrote:
In the syntax stuff, the c.vim file should be changed to have the following:
Old:
syn regioncStringstart=++ skip=+\|\\+ end=++
contains=cSpecial
New
syn regioncStringstart=++ skip=+\||'+ end=++
I get:
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[EMAIL PROTECTED]
SMTP error from remote mail server after RCPT TO:[EMAIL PROTECTED]:
host uk2mxarray3.uk2.net [83.170.64.215]: 550 address
Patch 7.0.098
Problem:Redirecting command output in a cmdline completion function
doesn't work. (Hari Krishna Dara)
Solution: Enable redirection when redirection is started.
Files: src/ex_docmd.c, src/ex_getln.c
*** ../vim-7.0.097/src/ex_docmd.c Sun Sep 10 15:50:32
I'm working in FreeBasic and some C and some Perl. This is one of the
fixes in the basic.vim thing I'm doing and I saw the same thing in the
c.vim file and thought they would give the same incorrect highlighting.
I ran into this (for C) while working at NASA and thought I'd fix it,
but as
Patch 7.0.099
Problem:GUI: When the popup menu is visible using the scrollbar messes up
the display.
Solution: Disallow scrolling the current window. Redraw the popup menu
after scrolling another window.
Files: src/gui.c
*** ../vim-7.0.098/src/gui.cTue
That is very strange. In 7.0.17 the exit command is still highlighted
as a string. If I put in an additional single quote then it
re-highlights as a function.
test.pl
print This's a test';
exit( 0 );
Look correct but the
test.pl
print This's a test;
exit( 0 );
Does not. Also
Mark Manning wrote:
That is very strange. In 7.0.17 the exit command is still highlighted
as a string. If I put in an additional single quote then it
re-highlights as a function.
test.pl
print This's a test';
exit( 0 );
Look correct but the
test.pl
print This's a test;
exit( 0
Mark Manning wrote:
Ok, with so many people going What do you mean? I'm going to do the
right thing and download the latest and greatest version. Obviously
there is something wrong going on here with me and my system. Otherwise
so many people wouldn't be saying their stuff is working
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
(If I
put in echo version it comes back as 700. Even the 7.0.17 version
comes back as 700
Output of ':echo version' does not reflect patchlevel. (the .17 in
7.0.17 is patchlevel).
You can see the patchlevel on the initial splashscreen, or
in
Hey, I hate to keep barging in here asking questions and such but here
is a new one. :-)
In the new basic.vim file I am having a problem. In FreeBasic you can
use both single as well as double quotes to enclose a string.
Unfortunately, you can also have comments which start with a single
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
Hey, I hate to keep barging in here asking questions and such but here
is a new one. :-)
In the new basic.vim file I am having a problem. In FreeBasic you can
use both single as well as double quotes to enclose a string.
Unfortunately, you can
-- Forwarded message --
From: Mark Manning [EMAIL PROTECTED]
Date: Sep 11, 2006 1:43 AM
Subject: Re: New question
To: Yakov Lerner [EMAIL PROTECTED]
Ok, tried it and it works! :-)
Thanks! :-)
Mark
I saw in the c.vim that there was an error statement for octal numbers.
There isn't one for hex numbers so I made one really quickly. If you
want, just put it into the c.vim file. :-)
The test:
syn regioncHexErrorstart=0x\x*[g-zG-Z] end=\W
The highlight command:
hi link
On 9/11/06, Mark Manning [EMAIL PROTECTED] wrote:
I saw in the c.vim that there was an error statement for octal numbers.
There isn't one for hex numbers so I made one really quickly. If you
want, just put it into the c.vim file. :-)
The test:
syn regioncHexErrorstart=0x\x*[g-zG-Z]
Thanks for the info! :-)
(Hit the reply button rather than Compose Mail To.)
Mark
It is fairly easy to check for inconsistencies in Binary, Octal, and Hex
because they have a fixed format. Decimal is not as easy due to there
being integers, reals, and general format numbers (ie: #e+/-#) which are
all grouped into the Decimal category. I'll think about it though.
Maybe I
Hi.
I tried ftp access with netrw.vim.
ex: :e ftp://machine/path/
I get --No lines in buffer--.
and I get following message in vim buffer in japanese.
ftp: is not internal command.
I guess that the first problem cause by :file command.
and the second cause by following code.
Mark Manning wrote:
Ok, after downloading the current items on the web page at vim.org both
C and Perl are working ok (in both Windows and Cygwin/Linux). Basic
still has the problems from before. Thanks to everyone for speaking
up. :-)
To Tony: Thanks for the diff command. I'll see
On Sun, 10 Sep 2006 at 1:56pm, Bram Moolenaar wrote:
Patch 7.0.096
Problem:taglist() returns the filename relative to the tags file, while
the directory of the tags file is unknown. (Hari Krishna Dara)
Solution: Expand the file name. (Yegappan Lakshmanan)
Files:
On Sun, 10 Sep 2006 at 9:07pm, Bram Moolenaar wrote:
Patch 7.0.098
Problem:Redirecting command output in a cmdline completion function
doesn't work. (Hari Krishna Dara)
Solution: Enable redirection when redirection is started.
Files:src/ex_docmd.c,
A.J.Mechelynck wrote:
Mark Manning wrote:
Ok, after downloading the current items on the web page at vim.org
both C and Perl are working ok (in both Windows and Cygwin/Linux).
Basic still has the problems from before. Thanks to everyone for
speaking up. :-)
To Tony: Thanks for the
On Fri 8-Sep-06 4:11pm -0600, Bram Moolenaar wrote:
Bill McCarthy wrote:
To better understand what vimdiff is doing (and why it is so
slow), I had my shell (4NT under WinXP) keep a log showing
me just what was requested. [Note: I use '!' instead of ''
for redirection because my 4NT is set
Laurent Birtz wrote:
Hello,
I need help to change the default behavior of the 'autoindent' option.
The doc says:
Copy indent from current line when starting a new line (typing CR
in Insert mode or when using the o or O command). If you do not
type anything on the new line except BS
A.J.Mechelynck wrote:
Tom Carr wrote:
Let's say I have the following mapping:
nnoremap = 3l
Now if I type =, it moves 3 characters to the right, as expected.
Now if I type 1=, it moves 13 characters to the right instead of 3.
Now if I type 3=, it moves 33 characters to the right instead of 9.
Michal Wieczorek wrote:
Hello.
I'd like to see the syntax highlight in the folded lines.
After reading the help I'm able to change the foldtext()
and highlight of the whole line but I can't turn on
syntax highlighting for it.
I found some letters about it (#35931, #18855)
but it wasn't mansion
Tom Carr wrote:
Let's say I have the following mapping:
nnoremap = 3l
Now if I type =, it moves 3 characters to the right, as expected.
Now if I type 1=, it moves 13 characters to the right instead of 3.
Now if I type 3=, it moves 33 characters to the right instead of 9.
It works
On 9/9/06, Laurent Birtz [EMAIL PROTECTED] wrote:
Hello,
I need help to change the default behavior of the 'autoindent' option.
The doc says:
Copy indent from current line when starting a new line (typing CR
in Insert mode or when using the o or O command). If you do not
type
On 9/9/06, Laurent Birtz [EMAIL PROTECTED] wrote:
Hello,
I need help to change the default behavior of the 'autoindent' option.
The doc says:
Copy indent from current line when starting a new line (typing CR
in Insert mode or when using the o or O command). If you do not
type
Hi everybody,
I have a quick question regarding ftplugins. I created a directory in my
after/ftplugin directory for each filetype, with several plugins in
each. Up to now I had a directory called c, which served to hold plugins
for both c and c++ files, and this worked well. However I decided to
On 9/10/06, Marius Roets [EMAIL PROTECTED] wrote:
Hi everybody,
I have a quick question regarding ftplugins. I created a directory in my
after/ftplugin directory for each filetype, with several plugins in
each. Up to now I had a directory called c, which served to hold plugins
for both c and
Marius Roets wrote:
Hi everybody,
I have a quick question regarding ftplugins. I created a directory in my
after/ftplugin directory for each filetype, with several plugins in
each. Up to now I had a directory called c, which served to hold plugins
for both c and c++ files, and this worked well.
Hi,
I often want to insert _one_ object only while being in normal mode
and return to normal mode as soon as possible.
My currrent edit scheme looks similiar to this:
(missing empty line in source code recognized)
either o or O pressed which throws me into insert mode
ESCape from insert
Hi,
I don't find a way how to make C++ indentation when all function
arguments are aligned in this way:
int TcSomeClass::SomeMethod(int arg1,
int arg2,
char *arg3) {
Currenly I receive the
On 9/10/06, Meino Christian Cramer [EMAIL PROTECTED] wrote:
Hi,
I often want to insert _one_ object only while being in normal mode
and return to normal mode as soon as possible.
My currrent edit scheme looks similiar to this:
(missing empty line in source code recognized)
either o or O
Meino Christian Cramer wrote:
Hi,
I often want to insert _one_ object only while being in normal mode
and return to normal mode as soon as possible.
My currrent edit scheme looks similiar to this:
(missing empty line in source code recognized)
either o or O pressed which throws me into
On 9/10/06, Dima [EMAIL PROTECTED] wrote:
Hi,
I don't find a way how to make C++ indentation when all function
arguments are aligned in this way:
int TcSomeClass::SomeMethod(int arg1,
int arg2,
On 9/10/06, Sven Brueggemann [EMAIL PROTECTED] wrote:
Hello,
Vim 7 combines syntax colouring and diff colouring when diffing. This
often makes the diffs hard to read.
Is there a way to automagically turn syntax colouring off when diffing?
put this into your ~/.vunrc:
if diff | syntax off |
On 9/10/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/10/06, Sven Brueggemann [EMAIL PROTECTED] wrote:
Hello,
Vim 7 combines syntax colouring and diff colouring when diffing. This
often makes the diffs hard to read.
Is there a way to automagically turn syntax colouring off when diffing?
Sven Brueggemann wrote:
Hello,
Vim 7 combines syntax colouring and diff colouring when diffing. This
often makes the diffs hard to read.
Is there a way to automagically turn syntax colouring off when diffing?
Kind regards
Sven
(Untested)
:setl syn=
:diffthis
Yakov Lerner wrote:
Vim 7 combines syntax colouring and diff colouring when diffing.
This often makes the diffs hard to read.
Is there a way to automagically turn syntax colouring off when
diffing?
put this into your ~/.vimrc:
if diff | syntax off | endif
Now that was fast... Thanks!
Kind
Yakov Lerner wrote:
On 9/10/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/10/06, Sven Brueggemann [EMAIL PROTECTED] wrote:
Hello,
Vim 7 combines syntax colouring and diff colouring when diffing. This
often makes the diffs hard to read.
Is there a way to automagically turn syntax
On 9/10/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 9/10/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 9/10/06, Sven Brueggemann [EMAIL PROTECTED] wrote:
Hello,
Vim 7 combines syntax colouring and diff colouring when diffing. This
often makes the diffs hard to
On 9/10/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
2. This won't work if diff mode is entered after starting Vim, as
opposed to invoking it as [g]vimdiff or [g]vim -d from the command-line.
Right, but if all you use is vimdiff at shell prompt (as I do),
this is good enough and simple.
Hi,
Yakov Lerner wrote:
How can a script test for specific patchlevel ?
For example, I have vim 7.0.86 and I need to check in the script that
patchlevel is = 7.0.86. But v:version is 700. How ? It would be
nice if to have patchlist available through some v: variable.
you can check for a
On 9/10/06, Jürgen Krämer [EMAIL PROTECTED] wrote:
Hi,
Yakov Lerner wrote:
How can a script test for specific patchlevel ?
For example, I have vim 7.0.86 and I need to check in the script that
patchlevel is = 7.0.86. But v:version is 700. How ? It would be
nice if to have patchlist
Jürgen Krämer wrote:
Hi,
Yakov Lerner wrote:
How can a script test for specific patchlevel ?
For example, I have vim 7.0.86 and I need to check in the script that
patchlevel is = 7.0.86. But v:version is 700. How ? It would be
nice if to have patchlist available through some v: variable.
you
In particular, here's a solution:
map = :RightShiftcr
com! -count=1 RightShift call RightShifter(count)
fun! RightShifter(cnt)
exe norm! .(3*a:cnt).l
endfun
That's an interesting hack, but there are a few problems with this solution:
* This only works correctly on the first line of the
If you would accept using a user-command, then you could for instance define
command -nargs=0 -count=1 -bar L call MoveByThrees(count)
function MoveByThrees(count)
let i = a:count
while i 0
normal 3l
i = i - 1
endwhile
http://vim.sourceforge.net/scripts/script.php?script_id=1649
scrollfix.vim - keep cursor at fixed visual line of window
This plugin, scrollfix, maintains cursor at fixed visual line of window
(except when near beginning of file and near end of file. The
latter is configurable. You can choose
Can you try this to see whether it does what you want ?:
:imap Enter Enterspacebs
I get the following behavior:
When I press 'o', it starts an empty line correctly indented. If
I press 'escape' immediately, the indentation is removed and the
cursor moves to column 1. If I press
On 9/10/06, Laurent Birtz [EMAIL PROTECTED] wrote:
Can you try this to see whether it does what you want ?:
:imap Enter Enterspacebs
I get the following behavior:
When I press 'o', it starts an empty line correctly indented. If
I press 'escape' immediately, the indentation is
Yakov Lerner wrote:
Laurent Birtz wrote:
When I press 'o', it starts an empty line correctly indented. If I
press
'escape' immediately, the indentation is removed and the cursor
moves to
column 1. If I press 'enter' instead, the indentation is removed
for the
first line, but the
Hi Yakov,
On Sunday 10 September 2006 12:27, Yakov Lerner wrote:
I created file ~/bat/my.dir.vim/after/ftplugin/c/xxx.vim containing line
call input(This is after/ftplugin/c/xxx.vim)
and file ~/bat/my.dir.vim/after/ftplugin/cpp/cpp_xyz.vim containing line
call input(This is
Hi Tony,
On Sunday 10 September 2006 12:51, A.J.Mechelynck wrote:
AFAIK both sets should be loaded. See:
- BufRead and BufNewFile autocommands for the concerned file extension
(*.c, *.cpp, *.c++, etc.)
- FileType autocommand
- function s:LoadFTPlugin in $VIMRUNTIME/ftplugin.vim
- c
On 9/10/06, Benjamin Esham [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
Laurent Birtz wrote:
When I press 'o', it starts an empty line correctly indented. If I
press
'escape' immediately, the indentation is removed and the cursor
moves to
column 1. If I press 'enter' instead, the
On 9/10/06, Benjamin Esham [EMAIL PROTECTED] wrote:
I get this behavior with 7.0.94, but it's done this for as long as I can
remember (I've been using Vim since 6.2, I think).
Some RedHat-8-based appliences around here have vim 6.1 :-)
Yakov
Yes with these two mappings mentioned earlier in this thread,
all lines are indented after oEnterEnterEnter:
:inoremap Enter Enterspacebs
:nnoremap o ospacebs
Got it! With these two mappings, it works correctly.
Apparently on my system (vim version 6.4,
Benjamin Esham wrote:
Yakov Lerner wrote:
Laurent Birtz wrote:
When I press 'o', it starts an empty line correctly indented. If I press
'escape' immediately, the indentation is removed and the cursor moves to
column 1. If I press 'enter' instead, the indentation is removed for the
first
Laurent Birtz wrote:
Yes with these two mappings mentioned earlier in this thread,
all lines are indented after oEnterEnterEnter:
:inoremap Enter Enterspacebs
:nnoremap o ospacebs
Got it! With these two mappings, it works correctly.
Apparently on my system
:imap o ospacebs means add a space and delete it whenever you
insert a lowercase o in _Insert_ mode. This creates an undo point
after each lowercase o, which is probably not what you want.
See :map-overview
Eep! Indeed. I'm a vim newbie and I didn't RTFM properly.
Thanks!
Laurent Birtz
Elliot Shank wrote:
I swear I saw something on this list about this before, but I can't find
it. If someone can point me at the prior post, I'd appreciate it.
I've got a utf-8 file with some CJK characters in it. These characters
are being displayed on the line below they are actually on.
70 matches
Mail list logo
