Yakov Lerner wrote:
On 5/14/07, Václav Šmilauer [EMAIL PROTECTED] wrote:
Hello,
I submit patch that implements the 'breakindent' feature. It is on vim
todo
list, since the moment I tried a few years ago (see e.g.
http://marc.info/?l=vim-devm=109921292009721w=1). Picture says what
it's
Charles E Campbell Jr wrote:
A.J.Mechelynck wrote:
I'm not sure what varnumber_T means: will st.stsize (the dividend) be
wide enough to avoid losing bits on the left?
varnumber_T is int (long if an sizeof(int) = 3).
st.stsize 's size depends on whether 32bit or 64bit integers are available
Yakov Lerner wrote:
[...]
stat() on Linux has 32-bit st_size field (off_t is 32-bit). There is
stat64()
syscall which uses 'struct stat64' structure where st_size is 64-bit. By
defining __USE_LARGEFILE64 at compile-time, stat() is redirected to
stat64(). I don't know whether default Linux vim
In
*options.txt* For Vim version 7.1. Last change: 2007 May 11
under 'browsedir', at line 1151, there is:
{not in Vi} {only for Motif and Win32 GUI}
Actually, this option is functional in my GTK2/Gnome GUI.
Best regards,
Tony.
--
The day after tomorrow is the
Stephan Hegel wrote:
Hi,
A.J.Mechelynck wrote:
- Using cat is OK as long as you can be sure that you'll get them in
numeric order: this is usually the case on Unix but not necessarily on
Dos, where a wildcarded filename usually gets its results in directory
order, not sorted by filename
Stephan Hegel wrote:
A.J.Mechelynck wrote:
- What is ncftp? On my openSUSE 10.2 system I have a program called
ftp but none called ncftp.
[39]./home/steve: rpm -qi ncftp
Name: ncftpRelocations: (not relocatable)
Version : 3.1.9
:set enc? penc?
encoding=utf-8
printencoding=utf-8
:%ha
not found in runtimepath: print/utf-8.ps
Is this last message normal?
I have here a file including an Esperanto-French glossary, which contains both
the consonants+circumflex of Esperanto and the French oe ligature. No matter
how I
scott wrote:
[...]
ncftp should have popped right up for you -- what do you have
in Configured Software Catalogs (under installation sources)?
sc
Status Refresh Name URL
On On YaST
iso:///?iso=openSUSE-10.2-GM-DVD-i386.isourl=hd:///?device=/dev/hda2filesystem=auto
On On
Forward to vim-dev list. See my comments at bottom.
Original Message
Subject: Re: compiling vim7.1 (huge version) gets build with normal version
Date: Tue, 15 May 2007 08:14:28 -0700
From: Tushar Desai [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: A.J.Mechelynck [EMAIL
Stephan Hegel wrote:
A.J.Mechelynck wrote:
patch -p0 patches/7.1.001
patch -p0 patches/7.1.002
As long as you have two patches this can be done easily. But what
if you have 100+ ?
Then try this:
cat patches/7.1.* patchfile
patch -p0 patchfile
rm patchfile
Done.
Rgds,
Stephan
fREW wrote:
Hey Tony,
What is the URL for your Vim Compile site? I can't find the link anywhere.
Thanks!
-fREW
Method I: Start at my home portal
http://users.skynet.be/antoine.mechelynck/
Click The Vim Editor
then the two bottom links in the list at top left point to my HowTo pages for
Nageshwar M wrote:
Hello,
I compiled the vim 7.1 source for unix and installed it in my fedora
core 4 pc. When I pressed arrows its printing A,B,C,D's(in insert
mode) , backspace is not working and when I pressed delete
continuously the gvim is closing down. Someone please help me.
The
Larson, David wrote:
I just upgraded to 7.1, and now when I open up a gvim session, I get
this huge monospaced font that I can't change. If I type:
:set guifont?
it returns 7x14 which is what I set it to, but it isn't what is
displayed. If I change the setting to *any* other font that is valid
Micah Cowan wrote:
Bram Moolenaar wrote:
[...]
The solution is simple: Don't create a link in place of the .viminfo
file. And certainly not to /dev/null.
Background info: When Vim finds an existing .viminfo file, it writes the
new info into a temp file (since it's still reading from the
Micah Cowan wrote:
A.J.Mechelynck wrote:
Micah Cowan wrote:
Bram Moolenaar wrote:
[...]
The solution is simple: Don't create a link in place of the .viminfo
file. And certainly not to /dev/null.
Background info: When Vim finds an existing .viminfo file, it writes the
new info into a temp
Robert Lee wrote:
A.J.Mechelynck wrote:
Micah Cowan wrote:
A.J.Mechelynck wrote:
Micah Cowan wrote:
Bram Moolenaar wrote:
[...]
The solution is simple: Don't create a link in place of the .viminfo
file. And certainly not to /dev/null.
Background info: When Vim finds an existing .viminfo
Micah Cowan wrote:
Following description lifted from bug filed at
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/78960
[EMAIL PROTECTED]:~$ rm .viminfo
[EMAIL PROTECTED]:~$ ln -s /dev/null .viminfo
[EMAIL PROTECTED]:~$ ls -l .viminfo
lrwxrwxrwx 1 sa sa 9 2007-01-12 17:16 .viminfo -
Taylor Venable wrote:
[...]
If it did follow the symlink to /dev/null, and tried to read from that
device, it would fail. You can't (or at least, shouldn't) read from
/dev/null because it's a sink, not a source. What kind of behavior
would you expect, trying to read from /dev/null?
[...]
Bram Moolenaar wrote:
[...]
I'll add a specific line to copy rgb.txt.
Just for the record, after reformatting the entries to a common format and
sorting, a diff between my ~/.build/vim/vim71a/runtime/rgb.txt and my
/usr/share/X11/rgb.txt shows no other difference than the header comment --
Michael Wookey wrote:
A.J.Mechelynck wrote:
Michael Wookey wrote:
Hello vimmers,
I am running 7.1a.001 on OSX and have just noticed the following
from
console vim (running in Terminal.app and also occurs in iTerm.app).
If I change the colour scheme I receive a lot of error output
I had a devil of a time locating the rgb.txt file on my SuSE 10.2 distro. In
order to alleviate the task of fellow users, I propose the attached patch to
:help rgb.txt.
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
223. You set up a web-cam as your home's
Michael Wookey wrote:
Hm... Maybe the console version checks the values of the guibg= guifg=
settings even though it doesn't use them. Try dropping the attached
file into your $VIMRUNTIME folder and see if it makes any difference.
(See :help rgb.txt for an explanation of how Vim uses it. IIUC,
Micah Cowan wrote:
I wrote:
Therefore, there would seem to be no harm whatsoever in detecting screen
as an xterm-mouse-code-capable terminal, and sending the mouse-mode
sequence (xterm protocol, since AFAIK screen provides no way to detect
the underlying xterm version). If the underlying
Setting followups to vim-dev
Steve Hall wrote:
The current right-click menu on GUI tabs is hardcoded and presents a
whole host of issues for anyone who uses code to manage buffers, tabs,
or windows. It pretends to be a sophisticated menu but it really
executes a basic Vim command which may or
Micah Cowan wrote:
Edward L. Fox wrote:
On 5/10/07, Gautam Iyer [EMAIL PROTECTED] wrote:
I got the same error. My response was
rm -rf vim7
svn co https://svn.sourceforge.net/svnroot/vim/trunk vim7
svn switch can only switch from a directory into another directory
inside the same
Anatoli Sakhnik wrote:
Hello!
On RHEL4 works well!
On Fedora Core 6 couldn't automatically determinte $VIMRUNTIME, lacked
the last part 'vim71a' in the path when I tried to open a file (say,
Foo.hs). Without initial file opening from command line works well.
On mingw (Windows XP) couldn't
Micah Cowan wrote:
[...]
But you already have hacked support into your programs for mouse
support. Now that you've done that, couldn't you just open it up a bit?
Is there anything wrong with always recognizing the appropriate xterm
sequences (provided that they don't first match a valid terminfo
One word under :help 'ttymouse' was obviously forgotten when that option got
more possible settings. See suggested patch, attached.
Best regards,
Tony.
--
You should never wear your best trousers when you go out to fight for
freedom and liberty.
-- Henrik Ibsen
***
Michael Wookey wrote:
Hello vimmers,
I am running 7.1a.001 on OSX and have just noticed the following from
console vim (running in Terminal.app and also occurs in iTerm.app).
If I change the colour scheme I receive a lot of error output. For
example:
:colorscheme desert
Results in:
Michael Wookey wrote:
Hello vim list,
I've just synced up to 7.1a.001 (svn #263) and built on Win32 (MSVC).
Everything builds fine and I replace my previous gvim.exe and vim.exe
with the newly built versions. I also sync my runtime from
ftp.nluug.nl.
My vim installation is in:
Markus Trenkwalder wrote:
Hi list,
checked out vim-7.1a.001 today from svn (#263) and tried to compile it
with mingw-gcc and got the following error:
8
$ make -f Make_ming.mak
gcc -c -Iproto -DWIN32 -DWINVER=0x0400 -D_WIN32_WINNT=0x0400
-DHAVE_PATHDEF -DFEAT_BIG -DHAVE_GETTEXT
Bram Moolenaar wrote:
Tony Mechelynck wrote:
[...]
I notice this patch modifies one runtime file. This reminds me that runtime
updates are not always reflected in patches. Do the files in
ftp://ftp.vim.org/pub/vim/runtime/ (and the equivalent rsync repository,
ftp.nluug.nl::Vim/runtime/ )
Edward L. Fox wrote:
On 5/7/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
[...]
You're not the first; there seems to have been a f*ckup in the svn commit
lately. I suggest you scrap your existing 7.1a sources and restart from
scratch, by downloading the 7.1a.000 sources then applying the
7.1a
Gary Johnson wrote:
On 2007-05-05, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Bram Moolenaar wrote:
Announcing: Vim (Vi IMproved) version 7.1a BETA
This is a BETA release of Vim 7.1. It consists of Vim 7.0 plus all
patches and updated runtime files.
I expect this to be stable, since
Yakov Lerner wrote:
On 2007-05-05, Bram Moolenaar [EMAIL PROTECTED] wrote:
Announcing: Vim (Vi IMproved) version 7.1a BETA
I tried to build vim7.1 from svn. But all I get from usual
svn location (https://svn.sourceforge.net/svnroot/vim/vim7), is
vim 7.0.236. Will vim7.1 be served at this
Michael Henry wrote:
Gary Johnson wrote:
On 2007-05-05, A.J.Mechelynck [EMAIL PROTECTED] wrote:
(Warning: In the ln command as used here, the target name comes
before the link name. I find this counter-intuitive.)
It's not just me then. I have to think carefully about that every
time I
Bram Moolenaar wrote:
Patch 7.1a.001
Problem:Crash when downloading a spell file. (Szabolcs Horvat)
Solution: Avoid that did_set_spelllang() is used recursively when a new
window is opened for the download.
Also avoid wiping out the wrong buffer.
Files:
François Pinard wrote:
[Martin Krischik]
[Martin Krischik]
That is probalby because the svn server is a mess.
[probably]
Only the vim svn archive has no space for tags, braches or releases.
[branches]
It is not a mess, merely
Yakov Lerner wrote:
On 5/1/07, Yakov Lerner [EMAIL PROTECTED] wrote:
[...]
How about using SIGALRM when search is progressing, every second ?
SIGALRM handler would store time() into global var (and reload alarm(1)).
The search would check the global var for changes, every line.
It is cheap to
Bram Moolenaar wrote:
[...]
Modelines are default off when you are root. The mail filetype plugin
also switches it off.
[...]
Are you sure? In a terminal logged-in as root, using vim 7.0.235:
vim -u NONE -N
:set ml? mls?
modeline
modelines=5
Modelines default off when
scott wrote:
i had to
'rm src/auto/config.cache
before i could build with this one
sc
Yes, this is normal for a patch affecting the configure files:
src/auto/configure
src/configure.in
src/config.h.in
Me too: the first make ended in an error, suggesting to
Bram Moolenaar wrote:
Patch 7.0.237
Problem:For root it is recommended to not use 'modeline', but in
not-compatible mode the default is on.
Solution: Let 'modeline' default to off for root.
Files: runtime/doc/options.txt, src/option.c
Note:
:set mlvim
or
Announcement: I've tentatively uploaded my current vim binary. Here are the
details and caveats:
- :version output is at
http://users.skynet.be/antoine.mechelynck/vim/version.txt -- check this first
before you attempt to download the executable.
- executable is at
John Beckett wrote:
[...]
Is folding really needed in a default modeline?
John
Folding may be useful in a modeline. (Don't know what you call a default
modeline.) Depending on how the particular file is written, you may want to
set foldmethod=marker (and which marker), foldmethod=syntax,
Ernie Rael wrote:
Hi all,
I've just joined this list. I'm not a vim developer per se. However, I
put together jVi, http://jvi.sourceforge.net , whose core is a port of
some of vim to java. It runs on NetBeans ( and JBuilder, but not
supported any more). jVi is based on vim-5.6.
A jVi user
Babiker Osman wrote:
Hi
السلام
I wonder who is the most arabic -vim -tex expert to
consult him
babiker osman
It depends what you want to do.
- If it's so high-fired secret that you won't give us any hint of what you
might be doing, just dig into the help. Start at :help arabic.txt if
Tomas Golembiovsky wrote:
Greetings mortals,
today somebody came to #vim, and pasted some modeline (containig joke or
such). He muttered something about not knowing what that means and left
before long. But (!) what I noticed is that feedkeys() was used as part of
foldexpression and it turned
Nikolai Weibull wrote:
On 4/27/07, Jonathan Smith [EMAIL PROTECTED] wrote:
A.J.Mechelynck wrote:
- Insane? All is relative. We're only at 7.0.233 as of today. FYI, Vim
6.2 went to 532 patches, see http://ftp.vim.org/pub/vim/patches/
Release early, release often :)
Isn't that what's
Nikolai Weibull wrote:
On 4/27/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
On 4/27/07, Jonathan Smith [EMAIL PROTECTED] wrote:
A.J.Mechelynck wrote:
- Insane? All is relative. We're only at 7.0.233 as of today.
FYI, Vim
6.2 went to 532 patches, see http
Bram Moolenaar wrote:
[...]
I guess most Turkish characters are in latin1, only the ones that are
not won't work with 'langmap'.
small undotted i, g-breve, s-cedilla, ...
Best regards,
Tony.
--
The primary requisite for any new tax law is for it to exempt enough
voters to win the next
Jonathan Smith wrote:
With the insane number of patches collecting against 7.0, and presumably
the new features accumulating in the devel tree, is anyone thinking
about when a 7.1 release might be made?
-smithj
- Insane? All is relative. We're only at 7.0.233 as of today. FYI, Vim 6.2
Jonathan Smith wrote:
[...]
Even if BM is the only one who can actually make a release, I'd imagine
others have opinions on the matter. Anyway, I was just wondering.
-smithj
AFAICT, the current bugs are all (or almost all) mere bugfixes. I don't feel a
release is imperatively called-for
Sebastian Menge wrote:
Am Donnerstag, den 26.04.2007, 14:08 +0200 schrieb Sebastian Menge:
Perhaps this Mail from eclipse helps:
[ ... ]
quote from that mail:
SWT supports the embedding of OleDocuments and Active X Controls only.
In order to be an ActiveX control, the control must support
Robert Lee wrote:
Nikolai Weibull wrote:
On 4/24/07, Gregory Seidman [EMAIL PROTECTED] wrote:
In fact, what I'm asking it
to do currently rarely takes much time, but it could be really nice
to ask
it to do a lot more and still not pay a huge time or memory penalty.
What
Robert Lee wrote:
[...]
Counterwish #2: Dump VimScript and replace it with EMCAScript (maybe
using SpiderMonkey) so that people don't need to learn a new language
just to change the color scheme or keyboard mappings. Yes, this will
break backwards compatibility. Tough.
[...]
Don't? WTF
Nikolai Weibull wrote:
On 4/24/07, Ilya Sher [EMAIL PROTECTED] wrote:
Robert Lee wrote:
[snip]
Counterwish #2: Dump VimScript and replace it with EMCAScript (maybe
using SpiderMonkey) so that people don't need to learn a new language
If I understand you correctly, you assume that
ECMAScript
Nikolai Weibull wrote:
On 4/24/07, Andy Wokula [EMAIL PROTECTED] wrote:
Nikolai Weibull schrieb:
On 4/24/07, Andy Wokula [EMAIL PROTECTED] wrote:
Thomas schrieb:
So maybe one could make vimscript search a variable foo as l:foo,
a:foo,
(maybe also: w:foo, b:foo), s:foo, g:foo, and then
Виктор Кожухаров wrote:
Hello,
I think there might be a bug with vim7, and they way it handles the
arrow keys in a terminal.
The problem is, that in insert mode, the arrow keys don't navigate
through the text, but output letters. For example, pressing Up in
insert mode would do the equivalent
Nikolai Weibull wrote:
On 4/20/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Getting better. Nikola's comments also apply (thanks Nikola!).
No problem. I guess there's a bug in the current Ctrl+N
implementation? It seems to be cutting off the last character in the
completion. ;-)
nikolai
Nikolai Weibull wrote:
On 4/21/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
On 4/20/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Getting better. Nikola's comments also apply (thanks Nikola!).
No problem. I guess there's a bug in the current Ctrl+N
implementation
Alexei Alexandrov wrote:
Hi All!
When spell checking is on by default, quick fix window is full of spell
checking errors. Probably it should have off always, shouldn't it?
Spell checking is off by default (the default for 'spell' is off). If it is on
in a window you create, it must be
Ken Hirsch wrote:
Here is an experimental patch for a new feature for gvim on MS Windows.
I'm glad to hear any feedback about the code or the feature itself. I've
tried to follow the conventions in the vim source code. I call the
feature ClipboardWatch.
The new feature triggers an event
Bram Moolenaar wrote:
Patch 7.0.224
Problem:When expanding ## spaces are escaped twice.
Solution: Don't escape the spaces that separate arguments.
Files: src/eval.c, src/ex_docmd.c, src/proto/ex_docmd.pro
[...]
This patch failed to appear at ftp.vim.org. Patching from the .eml
Bram Moolenaar wrote:
Tony Mechelynck wrote:
[...]
Patching from the .eml
saved email succeeded after hand-converting from quoted-printable to
8bit -- not actually 8bit since the only things to convert were
:%s/=3D/=/g
:%s/=\n//g
I'm still using text-only e-mail and don't
Thomas wrote:
Hi,
When I use the following command (for demonstration purposes):
au CursorMoved * norm! zz
When I now press s-c-left or s-c-right, zz get inserted in the buffer.
These cursor key seem to be set by :behave mswin.
In summary:
:au CursorMoved * norm! zz
:behave mswin
Press
Andy Wokula wrote:
GVim7 (Win32) crashes if I do the following:
clean startup
:new
:tabnew
:call winnr(#)
happens with or without 219 patches included
Andy
also on Linux with gvim 7.0.219 called as gvim -N -u NONE and also when
replacing :call by :echo.
Note that the last accessed
Bram Moolenaar wrote:
Tony Mechelynck wrote:
In languages using accented letters, the Vim spell checker doesn't recognise
HTML entities (in HTML text): for example, the letters outside of the ...;
entities are highlighted as spellBad (after :set spell spelllang=fr) in
the following French
François Pinard wrote:
[Bram Moolenar]
Tony Mechelynck wrote:
In languages using accented letters, the Vim spell checker doesn't
recognise HTML entities (in HTML text) [...]
You'll have to check if using and ; in the middle of a word is
causing trouble. Adding them to word characters
In languages using accented letters, the Vim spell checker doesn't recognise
HTML entities (in HTML text): for example, the letters outside of the ...;
entities are highlighted as spellBad (after :set spell spelllang=fr) in
the following French words:
ougrave; meaning:
Ken Hirsch wrote:
[...]
To clarify, based on my understanding: if software is exported from the
U.S., which vim arguably is, and it is capable of powerful encryption
(64-bit symmetric keys, other limits for public-key/elliptic
algorithms), then it _is_ subject to export restrictions. As the
Opening a vimball in Vim sets 'nomodifiable' not only locally but also
globally: henceforward, all new [No Name] buffers opened in the same session
will be created with 'nomodifiable' set.
Workaround: Use :set modifiable in the first [No Name] buffer created after
opening a vimball.
Fix:
A.J.Mechelynck wrote:
Opening a vimball in Vim sets 'nomodifiable' not only locally but also
globally: henceforward, all new [No Name] buffers opened in the same
session will be created with 'nomodifiable' set.
Workaround: Use :set modifiable in the first [No Name] buffer created
after
John Wiersba wrote:
This appears to be a bug to me, but I want to check before filing a bug report.
I was unable to get any clarification on the vim mailing list.
Under cygwin, :e file* will match in a case-insensitive manner. I believe this is wrong,
since cygwin is emulating unix which is
Josh wrote:
I am interested in creating a kde or other window manager interface
for vim, adding debugger support or fixing bugs for google summer of
code. Are there any details that I need to know before I submit my
applications?
It may be obvious, but obvious things have a way of getting
Ian Tegebo wrote:
I followed the instructions at:
http://www.a-a-p.org/ports.html
and that installation yielded a vim without perl support. After looking at:
http://www.a-a-p.org/examples.html#variants
It seems like adding several flags shouldn't be that hard; I could even
imagine
that
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Ctrl-W ] (or :wincmd ] ) splits the window to show the definition of the tag
under the cursor, but prefixing it with :tab doesn't open a new tab:
Reproducible: Always
Steps to reproduce:
1. Place the cursor on a tag (e.g. on an identifier in a
Ctrl-W ] (or :wincmd ] ) splits the window to show the definition of the tag
under the cursor, but prefixing it with :tab doesn't open a new tab:
Reproducible: Always
Steps to reproduce:
1. Place the cursor on a tag (e.g. on an identifier in a program for which
ctags has been run).
2. Type
Paul Stuart wrote:
Hi there,
I'm having some trouble compiling vim 7 on solaris
8, and I wonder if someone could point me in the right
direction.
This is what I see when I compile it :
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MOTIF -I/usr/dt/include -g -O2
-o
Forwarding to list.
Original Message
Subject: Re: Why does VimResized get triggered 4 times per resize
Date: Fri, 9 Mar 2007 18:49:25 +0200
From: Marius Roets [EMAIL PROTECTED]
To: A.J.Mechelynck [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
[EMAIL PROTECTED]
Hi Tony
Mike Li wrote:
one more update: if i add the following two lines to my _vimrc, then
the ucs-2le text file works:
set fileencodings+=ucs-2le
set encoding=utf-8
note that both need to be set before i edit the file. once i load the
file, setting them no longer helps.
-x
Of course:
- Vim needs
thomas wrote:
2007/3/2, A.J.Mechelynck [EMAIL PROTECTED]:
Mapping seems to be buggy with some characters.
For instance:
:imap ' foo
does not work (the apostrophe is U+2019).
What is 'encoding' set to? Using multibyte characters (e.g. in a
mapping) will
only work if 'encoding' (which
Bram Moolenaar wrote:
[...]
How can you tell if the mapping works or not?
You can see what a key actually produces with CTRL-V key . So when
you type
:imap CTRL-V key foo
Where CTRL-V is one key and key is the mapped key.
Does the mapping still not work?
When I type
:map!
Yakov Lerner wrote:
Hello Bram,
Maybe vim would better set eol/noel after ':r !cmd' also,
no only after reading the file into buffer ? (that is, the condition
whether input had final \n or not).
As I can see currently, this piece of info is lost after ': !cmd' ?
Yakov
Maybe after :$r !cmd
When cycling through matches using :cnext, if there are several matches in a
single long line, the line is only shortened the first time (but _not_ the
2nd, 3rd, etc.,) to avoid a Hit-Enter prompt.
Reproducible: every time.
Steps to reproduce:
1. :set wrap I'm not sure this is necessary
2.
Nathan Coulter wrote:
bug report
==
version:
VIM - Vi IMproved 7.0 (2006 May 7, compiled May 7 2006 16:23:43)
MS-Windows 32 bit GUI version with OLE support
problem:
Writing to a file on a windows share where the underlying filesystem
supports hard links, modifying a
Manu Hack wrote:
gvim --version gives
[...]
So? What exactly are you trying to do? How does it fail?
Best regards,
Tony.
--
'Twas midnight, and the UNIX hacks
Did gyre and gimble in their cave
All mimsy was the CS-VAX
And Cory raths outgrabe.
Beware the software rot, my son!
The faults that
Bill McCarthy wrote:
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
Ryan Phillips wrote:
Gautam Iyer [EMAIL PROTECTED] said:
Hi All,
I just upgraded to Vim-7.0.195, and found that my quick fix bindings
don't work any more. For instance
:vimgrep /pattern/ *.c
:copen
Then pressing Enter on a particular error does not move to that error
location quick
Bram Moolenaar wrote:
Alexei Alexandrov wrote;
Hi Bram Moolenaar, you wrote:
Patch 7.0.193
Problem:Using --remote or --remote-tab with an argument that matches
'wildignore' causes a crash.
Solution: Check the argument count before using ARGLIST[0].
Files: src/ex_cmds.c
Alexei Alexandrov wrote:
Hi Bram Moolenaar, you wrote:
I think the best method is to obtain all the files from subversion and
then get the latest runtime files with rsync. Get spell files manually
(this can be done automatically if you use a language for the first
time).
I tried to use the
Bernhard Walle wrote:
* A.J.Mechelynck [EMAIL PROTECTED] [2007-02-13 01:40]:
It's Vim compiled by myself, from no other sources than Bram's official
ones (including 192 official patches).
Yes, that fixes it, but I don't want to have the new version in /usr/
simply because I have not root
Bill McCarthy wrote:
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
Bernhard Walle wrote:
* A.J.Mechelynck [EMAIL PROTECTED] [2007-02-12 02:47]:
Bernhard Walle wrote:
Hello,
after I installed netrw 107 in my ~/.vim, I cannot browse a directory
which
:e /path/to/dir
any more. That's annoying because also bookmarks don't work in the
directory browser
Bram Moolenaar wrote:
Tony Mechelynck wrote:
In
VIM - Vi IMproved 7.0 (2006 May 7, compiled Feb 4 2007 03:42:30)
Included patches: 1-191
Compiled by [EMAIL PROTECTED]
Huge version with GTK2-GNOME GUI. Features included (+) or not (-):
[...]
exists(:simalt) or exists(:tearoff) return 2;
Nikolai Weibull wrote:
On 1/30/07, Martin Krischik [EMAIL PROTECTED] wrote:
Am Dienstag 30 Januar 2007 schrieb [EMAIL PROTECTED]:
- being able to open very large files quickly and
without using too much memory. This could possibly
be achieved by not loading the entire file immediately.
Nikolai Weibull wrote:
On 1/29/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
On 1/29/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
The idea would be to leave the undo list alone, so that when the undo
table gets updated next it'll have a bigger
Martin Stubenschrott wrote:
I often want to complete full strings in quotes (foo, 'bla',
`command bla blub`).
But for now, I really need to type all these things again and again. It
would be nice, if I could say fc-x-c- to complete full strings.
Or maybe also c-xc-' for single qouted strings,
Martin Stubenschrott wrote:
On Sat, Jan 27, 2007 at 07:35:16PM +0100, Bram Moolenaar wrote:
Whatever this ends up to be: Please send me the best javascript indent
script, so that I can include it with the runtime files. A best guess
is better than nothing.
Full ack.
BTW: The last time I
Marcus Aurelius wrote:
[...]
If the user wants to edit long lines, (s)he cannot write a quick mapping
on-the-fly, because he needs something like this:
map buffer silent up gk
imap buffer silent up C-ogk
map buffer silent down gj
imap buffer silent down C-ogj
map buffer silent home ghome
imap
Georg Dahn wrote:
Hi!
--- A.J.Mechelynck [EMAIL PROTECTED] wrote:
map Down gj
imapDown C-Ogj
map Upgk
imapUpC-Ogk
IMHO these mappings are a better choice:
noremap Down gj
noremap Up gk
inoremap expr Down pumvisible() ? \ltDown : \ltC-Ogj
inoremap expr Up pumvisible
1 - 100 of 342 matches
Mail list logo
