Christian J. Robinson wrote:
On Fri, 27 Aug 2010, Charles E Campbell Jr wrote:
gcc: The -mno_cygwin flag has been removed; use a mingw targeted
cross-compiler.
on the first file it tries to compile (blowfish.o), and, sad to say,
no gvim.exe .
I had to edit Make_cyg.mak to use gcc-3
The following patch fixes a few typos.
diff --git a/runtime/doc/undo.txt b/runtime/doc/undo.txt
--- a/runtime/doc/undo.txt
+++ b/runtime/doc/undo.txt
@@ -148,7 +148,7 @@
:earlier {N}d Go to older text state about {N} days before.
:earlier {N}f Go to older text state {N} file
The following patch fixes section number.
diff --git a/runtime/doc/various.txt b/runtime/doc/various.txt
--- a/runtime/doc/various.txt
+++ b/runtime/doc/various.txt
@@ -610,7 +610,7 @@
Only useful for debugging Vim.
Hi,
I've just sudo mounted my hard drive to get my music off of it, and then vi
/etc/fstab so that it come up at boot time.
and I had the urge to hit tab to complete the entries in the fstba file as I
do with bash or many other things.
so then I thought, well if bash already has this feature, how
On 26/08/10 16:40, Ben Fritz wrote:
On Aug 25, 11:11 pm, JiaYanweijia...@126.com wrote:
I think this will be more reasonable than before.
If the encoding of edited text file differ form the system/vim encoding, it's
inconvenient to set default HTML charset to be 'encoding'. Thus, after
On Sat, Aug 28, 2010 at 4:16 PM, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
From my understanding, 'fileencoding' is the encoding Vim is supposed
to use to read/write the file. So, it does make sense that we should
use this instead of just 'encoding' for the charset of the generated
On 29/08/10 04:29, Benjamin Fritz wrote:
On Sat, Aug 28, 2010 at 4:16 PM, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
From my understanding, 'fileencoding' is the encoding Vim is supposed
to use to read/write the file. So, it does make sense that we should
use this instead of just
