On Sun 13-May-07 6:01am -0600, Edward L. Fox wrote:
I finally committed the two missing files from the sf.net's shell
server. Let's blame the Great Fire Wall built by the P.R.C.
government.
SVN now appears to be working nicely and appears to have the
full 7.1 code. Thanks!
--
Best regards,
On Mon 19-Feb-07 7:21am -0600, A.J.Mechelynck wrote:
Works for me.
For me too. BTW, Tony, I've never used :copen before - I
use :cw . There look the same but the documentation doesn't
seem to indicate that they are the same.
What's the difference between :copen and :cwindow ?
--
Best
Hello Vim Developers,
The help files specifies (see :help modeline):
-
There are two forms of modelines. The first form:
[text]{white}{vi:|vim:|ex:}[white]{options}
[text] any text or empty
{white}
On Wed 14-Feb-07 1:30am -0600, A.J.Mechelynck wrote:
Bill McCarthy wrote:
Most end with a ':' which does not appear to be permitted
above.
It is. It just adds an empty do-nothing setting at the end.
Thanks, Tony, I didn't consider the do-nothing setting and
didn't read the exception
On Fri 26-Jan-07 10:46pm -0600, Denis Perelyubskiy wrote:
in version 7.0.188 (I am on windows xp, us) nothing works when I select
'..' when browsing a directory. has anyone seen this? is this something
peculiar to my installation, a bug, or a feature?
I reported this problem to Chip on 1/9.
Denis,
On Sat 27-Jan-07 1:26am -0600, Bill McCarthy wrote:
On Fri 26-Jan-07 10:46pm -0600, Denis Perelyubskiy wrote:
in version 7.0.188 (I am on windows xp, us) nothing works when I select
'..' when browsing a directory. has anyone seen this? is this something
peculiar to my installation
Hello Markus,
Thanks for updating your plugin. It's working fine here on
Windows XP, except for one cosmetic problem.
Most of my text files have DOS EOLs (CR/LF). When the
file is decrypted, all lines end with ^M. If I save the
file, all lines end with CR/CR/LF - the only difference from
Hello Vim Developers,
Here's what the docs say:
===
*^*
^ To the first non-blank character of the line.
|exclusive| motion.
On Wed 6-Dec-06 6:24pm -0600, A.J.Mechelynck wrote:
Bill McCarthy wrote:
(3) '0' and 'Home' appear to be identical. Does anyone
see a difference?
(3) Yes I do. Notice the one mentions the same _text_
column and the other the same _screen_ column. Hit 0 on
a line starting with a hard
On Tue 21-Nov-06 7:38pm -0600, Liu Yubao wrote:
==
pad pv 168
patching file src/memline.c
Assertion failed: hunk, file ../patch-2.5.9-src/patch.c, line 339
This application has requested the Runtime to terminate it in an unusual
On Mon 13-Nov-06 7:54pm -0600, Eggum, DavidX S wrote:
Okay, try this, Matt (it is, again, lightly tested). Granted, it
recalculates from scratch every time, but it only does it when it needs
to and it should still be pretty fast. It also doesn't rely on the
events to be called once every
On Sun 12-Nov-06 7:54pm -0600, [EMAIL PROTECTED] wrote:
Well I'm reporting the above g:zbuflistcount in my 'rulerformat'.
Don't you think you should have mentioned that?
I really don't think I can afford the baggage of calling your function
from within my 'rulerformat'.
No, for 100 buffers,
On Thu 2-Nov-06 5:11am -0600, [EMAIL PROTECTED] wrote:
I'm pretty new to this mailing list and I hope I'm posting at the
right place. I just want to report a simple bug, easy to reproduce.
I have only tested it on Windows.
Open vim, write a single 1 characters line (filled with blanks
On Wed 18-Oct-06 4:13pm -0600, Mark Guzman wrote:
I hate to report problems w/o having solutions, but the svn repos is
currently only up to patch 132. I'm wondering if whatever update script
was maintaining it is broken... Hopefully someone with access can take a
look at it.
That's updated
On Tue 17-Oct-06 4:04pm -0600, Yakov Lerner wrote:
Of different current methods to access vim sources (svn, ftp, rsync, etc)
which one is fastest to be updated when new patch is issued, and
also has most reliable/fast server ?
I wasn't aware that sources were on FTP. Where are they?
Patches
Included patches:1-118
Here the output of :version
VIM - Vi IMproved 7.0 (2006 May 7, compiled Oct 8 2006 13:02:44)
MS-Windows 32 bit GUI version with OLE support
Included patches: 1-121
Compiled by Bill McCarthy [EMAIL PROTECTED]
Big version with GUI. Features included (+) or not (-):
+arabic
On Sun 8-Oct-06 7:29pm -0600, Bill McCarthy wrote:
New versions of 4nt and tcmd were recently loaded to the FTP
site. These are still called 8.00.49. What is the
difference?
Sorry, I sent that to the wrong email address.
--
Best regards,
Bill
On Sun 8-Oct-06 7:39pm -0600, A.J.Mechelynck wrote:
Bill McCarthy wrote:
On Sun 8-Oct-06 5:42pm -0600, Alexey I. Froloff wrote:
When current version of vim runtime will be updated for latest
patches? Patch 111 modifies autoload/gzip.vim and doc/eval.txt
which are still outdated on ftp
On Fri 6-Oct-06 12:25am -0600, Igor Prischepoff wrote:
Well, i still don't understand vim logic behind that process.
Let's see more realistic example.
gvim -U NONE -u NONE
Only last time, although I don't think it matters in this
example, you are working in 'cp'
On Fri 6-Oct-06 12:15am -0600, Gary Johnson wrote:
I also found this under :help gui-init:
To skip loading the system menu include 'M' in 'guioptions'.
So to avoid loading _anything_, at the expense of not having any
menus, one could start gvim as
gvim -N -u NONE -i NONE --cmd
On Fri 6-Oct-06 12:38pm -0600, Yakov Lerner wrote:
On 10/6/06, Bill McCarthy [EMAIL PROTECTED] wrote:
On Thu 5-Oct-06 8:54pm -0600, Gary Johnson wrote:
gvim -u NONE -i NONE -N
Setting -u NONE -i NONE -N is all that's needed. See :help -u.
I never noticed that 'vim -u NONE' ever read
On Wed 4-Oct-06 10:16pm -0600, Igor Prischepoff wrote:
Hi, i think i have found a bug in vim 7.0
Patch level 1-109.
Windows version +perl +python (i don't think this matters in this case)
here is how to reproduce:
gvim -u NONE -U NONE
:set complete-=tdon't want complete from
On Thu 5-Oct-06 8:54pm -0600, Gary Johnson wrote:
On 2006-10-06, Peter Hodge [EMAIL PROTECTED] wrote:
BTW, using
gvim -u NONE -U NONE
is both redundant (in the case of -U NONE), dangerous (since
default settings may truncate your viminfo on exit), and put
you in vi
On Thu 14-Sep-06 6:35am -0600, Bram Moolenaar wrote:
Patch 7.0.106
I encountered a problem that has appeared before patching
files in runtime. I received the following from my patch
invocation:
patching file `menu.vim'
Hunk #1 FAILED at 2.
Hunk #2 FAILED at 885.
Hunk #3
On Mon 11-Sep-06 3:02am -0600, Nikolai Weibull wrote:
This stream of thought mode you're using is more suited for IRC, see
http://www.vim.org/community.php.
Alternately, the vim list is a good choice. And never add
return receipt requests in posts to a mailing list.
--
Best regards,
Bill
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
Hello Vim Developers,
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 to not overwrite
existing files unless explicitly told to
On Wed 6-Sep-06 8:01am -0600, A.J.Mechelynck wrote:
In (g)vim 7.0.90, when I try to invoke the help, let's say
:help :help
the program hangs; and when I finally hit Ctrl-C I get:
E426: tag not found: :[EMAIL PROTECTED]
Similarly for F1
E426: tag not found: [EMAIL PROTECTED]
On Sat 19-Aug-06 3:13pm -0600, Yegappan Lakshmanan wrote:
On 8/10/06, Bill McCarthy [EMAIL PROTECTED] wrote:
The function reltimestr() return a string which may have
leading spaces. Is that a bug or a feature?
The string returned by reltimestr() has leading spaces, because
the following
On Sun 13-Aug-06 7:41pm -0600, Steve Hall wrote:
A normal full install should have all or nearly all these (at least my
install here on Fedora Core 5 does):
vim70/autoload/
colors/
compiler/
doc/
ftplugin/
icons/
indent/
keymap/
On Wed 26-Jul-06 1:20pm -0600, A.J.Mechelynck wrote:
Morality: Whenever possible, use / as path separator in Vim, even on
Windows. There are a few exceptions (where they don't work).
IMHO too many. One common example is passing a file to a
program within Vim - the '/' appears to be treated
Hello Vim Developers,
I was timing the startup process by stepping though what I
think Gvim does (on Win XP Pro with 7.0.42).
gvim -u NONE -N
That starts up without _vimrc or _gvimrc or plugins and sets
nocp.
:so $vim\_vimrc
worked fine.
:so $vim\_gvimrc
also worked fine.
On Sun 23-Jul-06 7:09pm -0600, Marvin Renich wrote:
At this point, I see the output from exec b curbuf but using
:messages I can see that the echomsg did indeed display (before the
output from :b). I also tried redraw between the :b and the :echomsg.
I don't have an answer for you but I
On Thu 11-May-06 2:03am -0600, you wrote:
Bill McCarthy wrote:
When I checkout vim7 with svn under WinXP Pro, my text files
are all coming out as UNIX files (using LF instead of
CR/LF).
The svn program is designed to handle proper EOL for an
operating system when a property called
On Wed 10-May-06 10:27am -0600, Bram Moolenaar wrote:
Patch 7.0.006
Problem:Mac: make shadow doesn't make a link for infplist.xml. (Axel
Kielhorn)
Solution: Make the link.
Files: src/Makefile
From WinXP, I installed with the big exe file and unzipped
the src and lang
On Wed 10-May-06 9:43pm -0600, Anduin Withers wrote:
Why do you want CR-LF files? A single LF should work just fine. The
only place where I know it doesn't work is when you read Make_ivc.mak
into Visual Studio.
Automatic LF to CR-LF translation always causes trouble somewhere.
CVS did
On Sun 7-May-06 10:58am -0600, Bram Moolenaar wrote:
Vim 7 is out!
Congratulations!
I looked at the release area and noticed that the vim70 tree
for Windows is still different from what is available by CVS
or SVN. This remains a minor inconvenience for Windows
users - either we use CVS (or
On Sat 29-Apr-06 3:49pm -0600, Bram Moolenaar wrote:
There are two setups, the Unix one and the MS-Windows one.
If you use the Unix setup you need to do make install. Thus uses the
files in the ../runtime directory that were unpacked from the Unix tar
archive.
If you use the MS-Windows
Hello Vim Developers,
Compiling with MVC or Ming, the exe files are copied from
c:\vim\vim70f\src to c:\vim\vim70f (the usual place). But
running install produces the following:
[c:\vim\vim70f]install
This program sets up the installation of Vim 7.0f04 BETA
ERROR: Cannot find
39 matches
Mail list logo
