(EVENT_STDINREADPOST, NULL, NULL, FALSE, curbuf);
+# endif
+}
+#endif
+
/* require ! to overwrite the file, because it wasn't read completely */
#ifdef FEAT_EVAL
if (aborting())
any insights appreciated,
mosh.
Regards,
Edward L. Fox
To Yongwei:
Does this patch solve your problem?
To Bram:
Please consider adding this patch. I think it is really a bug.
Index: src/gui_w32.c
===
--- src/gui_w32.c (revision 296)
+++ src/gui_w32.c (working copy)
@@
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.
On 5/13/07, Edward L. Fox [EMAIL PROTECTED] wrote:
Hi Vimmers,
On 5/13/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Announcing: Vim (Vi IMproved) version
On 5/14/07, David Nečas (Yeti) [EMAIL PROTECTED] wrote:
On Sun, May 13, 2007 at 09:28:11PM +0100, [EMAIL PROTECTED] wrote:
Umm, I suspect there's still an issue for us pesky OSX users with our
case-insensitive filesystems:
[long list of successful updates snipped]
svn: Failed to add
in a temporary file:
svn:'/src/vim7/svn/svn-commit.tmp'
[EMAIL PROTECTED] svn]$
Regards,
Edward L. Fox
On 5/12/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Nicolas Weber wrote:
The directories structure of the Subversion repository has been
changed. Please use this command to checkout the latest sources:
svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7
If you
On 5/10/07, Gautam Iyer [EMAIL PROTECTED] wrote:
On Wed, May 09, 2007 at 02:20:52PM -0700, Micah Cowan wrote:
If you had checked out a copy of the sources before, please run this
command in your source root directory to switch into the current
branch:
svn switch
On 5/8/07, Markus Trenkwalder [EMAIL PROTECTED] wrote:
Tried the ftp versions (including patch 7.1a.001) now. Same again. And
as Edward Fox told earlier the SVN repository should be almost the same
as CVS.
*Almost* the same with ftp versions.
*Definitely* the same with CVS.
I also tried
On 5/8/07, Markus Trenkwalder [EMAIL PROTECTED] wrote:
Edward L. Fox wrote:
On 5/8/07, Markus Trenkwalder [EMAIL PROTECTED] wrote:
Tried the ftp versions (including patch 7.1a.001) now. Same again. And
as Edward Fox told earlier the SVN repository should be almost the same
as CVS
in your source root directory to switch into the current
branch:
svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1
Hope this change won't bother you too much.
Regards,
Edward L. Fox
please give me the most bleeding-edge sources so that I can commit
them into the trunk/ directory of the SVN repository, and some users
who wish to use the unstable experimental version then can help you to
test the code.
Best regards,
Edward L. Fox
On 5/9/07, Edward L. Fox [EMAIL PROTECTED] wrote:
Hi Vimmers,
As many many people requested, I finally decide to obey the svn book's
advice and will build up trunk/ tags/ and branches/. But so far as you
know, sf.net's svn service is not in a good status so I'm not able to
commit all changes
On 5/9/07, Suresh Govindachar [EMAIL PROTECTED] wrote:
Edward L. Fox announced:
Hi Vimmers,
The directories structure of the Subversion repository has been
changed. Please use this command to checkout the latest sources:
svn co https://vim.svn.sourceforge.net/svnroot/vim
On 5/8/07, scott [EMAIL PROTECTED] wrote:
i was surpised by the fact that simply running 'svn update' bumped me up to
7.1a -- from previous posts i had thought there was something extra that had
to be done to get the beta, like create a new 71a directory or something
now i've got the beta i
On 5/7/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
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
On 5/8/07, Yakov Lerner [EMAIL PROTECTED] wrote:
On 5/8/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 5/5/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Announcing: Vim (Vi IMproved) version 7.1a BETA
I compared runtime files form ftp [1] and from svn [2].
Both
On 5/8/07, scott [EMAIL PROTECTED] wrote:
i was surpised by the fact that simply running 'svn update' bumped me up to
7.1a -- from previous posts i had thought there was something extra that had
to be done to get the beta, like create a new 71a directory or something
now i've got the beta i
On 5/7/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
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
On 5/8/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
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
On 5/7/07, François Pinard [EMAIL PROTECTED] 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]
On 5/7/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
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.
On 5/6/07, Yakov Lerner [EMAIL PROTECTED] wrote:
On 5/6/07, Martin Krischik [EMAIL PROTECTED] wrote:
Am Sonntag 06 Mai 2007 schrieb Yakov Lerner:
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.
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 :)
Yes, I admit that you are right. But
Hi Bram,
On 11/22/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
[...]
I didn't forget it, I just had to go away while waiting for the previous
version to be tagged. Tagging all the files for a specific version is
quite slow, it's currently the main bottleneck in sending out patched
versions.
///
Best regards,
Edward L. Fox
some weeks ago. Could you please include his change
in this patch? We can have these three things to be done in this
patch:
1. Add gbk and gb18030 as aliases of cp936;
2. Merge the translation patch of thinelephat.
3. Delete the scriptencoding line in the translation file.
Best regards,
Edward L
On 8/15/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Edward -
As the problem is caused by iconv and we won't be able to fix the
problem soon, and this problem influences gb2312 - cp936 (gbk)
converting only, so I suggest to remove this line from
runtime/lang/menu_zh_cn.gb2312.vim:
On 8/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
[...]
Edward had it on Windows. From :help encoding-values I gather that
Chinese and prc are alias to cp936 / euc-cn. Maybe gbk and gb18030
can be added to the family?
I'm using Debian Etch. But I had a look at the Windoze system and
found
On 8/13/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
[removed the Vim maillist, this is development only]
Edward L. Fox wrote:
On 8/12/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
[...]
You may have uncovered a bug that went unnoticed so far. Please try to
discover what causes
. So... Maybe it is still iconv's fault.
Sorry all. I did more tests and searched more documents and found that
it was a bug of libiconv, not gvim. The problem occurs only when
converting gb2312 to gbk. I'm trying to debug libiconv...
[...]
Ashamed
Edward L. Fox
this problem. I can't guess why the last character
is messed up, looks strange.
In fact this bug was noticed years before. But most of the Chinese
people decided to tolerate this situation. Anyway, I'm going to work
on~
[...]
Regards,
Edward L. Fox
by
* casting the second argument to void *. */
if (iconv(vcp-vc_fd, (void *)from, fromlen, to, tolen)
Best Regards,
Edward L. Fox
Patch Unofficial
Problem:Menu and toolbar: Doesn't display properly when using
zh_CN.GBK encoding under Linux.
Solution: Use gb2312 to generate the menu and toolbar to get proper
display, then use cp936 instead of GBK which is a correct alias under
Linux.
Files: runtime/menu.vim
***
as soon as I solve the problem. Hope you
can offer me some hints, too. :-)
[...]
Regards,
Edward L. Fox
On 7/20/06, Edward L. Fox [EMAIL PROTECTED] wrote:
Hi VIMmers,
The default sh indent script in VIM7 indent the following sample file this way:
8
#!/bin/sh
SYSTEM=`uname -s`
case $SYSTEM in
Linux)
echo My system is Linux
echo Do Linux
On 5/13/06, Brandt, Servatius [EMAIL PROTECTED] wrote:
[...]
So I suggest to use a svn:eol-style setting of LF instead of
native.
Previously when I didn't set the svn:eol-style property, all text
files were using LF as end-of-line character. Bill complained so I
change the end-of-line
- although that is indeed a good one, since every
Windows user has it and it is frequently a default in
Explorer.
Hopefully, the gentleman maintaining the svn repository
(Edward L Fox) will talk to the gentleman who properly
marked the files in CVS.
Well, well, well... I prop-setted most of the file
of sourceforge. But if this problem could
not be resolved, I'll try to sync the code with the patches manually.
Thanks,
Gautam
--
'Common' Proof Techniques:
12. Proof by obfuscation -- A long plotless sequence of true and/or
meaningless syntactically related statements.
Regards,
Edward L. Fox
On 5/5/06, Edward L. Fox [EMAIL PROTECTED] wrote:
Hi VIMmers,
I'm sorry that I'm not able to sync the SVN repository with the CVS
repository on time today, because the network is suffering some
problems. I had tried different routes but all failed. Maybe there is
something wrong with the main
Hi VIMmers,
I'm sorry that I'm not able to sync the SVN repository with the CVS
repository on time today, because the network is suffering some
problems. I had tried different routes but all failed. Maybe there is
something wrong with the main gateways of the whole country. :-(
I'll sync the
switching to svn will
cost more effect. Any way, I'll try my best to switch the whole
project to svn, without disturbing the other developers too much.
-Original Message-
From: Edward L. Fox [mailto:[EMAIL PROTECTED]
Maybe we should go to Subversion at SourceForge after all, since
41 matches
Mail list logo
