regards,
Martin
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGs6agEtBnr8BYnZ4RAhfQAKDqnkTzdOprjBHlJm52x7g+jFdYIACggDip
f0+bVpeBWfMWw6en+vgDUFY=
=DGJa
-END PGP SIGNATURE-
Regards,
Edward L. Fox
--~--~-~--~~~---~--~~
You
developers without
any more complaint.
[...]
Be In Peace,
Edward L. Fox
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
On 8/12/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Patch 7.1.066
Problem:When 'bomb' is set or reset the file should be considered
modified. (Tony Mechelynck)
Solution: Handle like 'endofline'. (Martin Toft)
Wow! Thanks very much for your wonderful work, Martin! I'm
On 8/16/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Xiaozhou Liu wrote:
Patch 7.1.071 adds test64 into src/testdir/. But it is not there
as I browse the subversion repository below. Is there any problem
or am I wrong?
Incredible! I'll borrow a Mac to try out your amazing work tomorrow.
Thanks very much for your hard work this summer, Jiang! I think I
should be ashamed that I've done nothing that I had promised for Vim
this summer. How long will it take for this patch merging into the
official version?
On
Reporter id: chenkw
Community: newsmth
Hi developers,
Steps to reproduce:
Vim 7.0 has a problem jumping between matching brackets in the following case:
Foo()
{
// {
}
The % command jumps between the close bracket and the open one in the comment
rather than at the right beginning of
On 8/25/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Suresh Govindachar wrote:
make -f Make_ming.mak clean
does not remove if_perl.c
You are supposed to use:
make -f Make_ming.mak -D PERL clean
You also need to add the choices for GUI or not and debugging or not,
Hi Bram
On 8/31/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Patch 7.1.094
Problem:When checking if syntax highlighting is present, looking in the
current buffer instead of the specified one.
Solution: Use buf instead of curbuf.
Files: src/syntax.c
[...]
When will
On 8/31/07, Tony Mechelynck [EMAIL PROTECTED] wrote:
Edward L. Fox wrote:
Hi Bram
On 8/31/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Patch 7.1.094
Problem:When checking if syntax highlighting is present, looking in the
current buffer instead of the specified one
On 8/31/07, David Anthony Terei [EMAIL PROTECTED] wrote:
Hi Adam,
Thanks for the feedback, just fixed the bug you mentioned then, Ill try to
get a new release out soon.
As for embedding, by default the plugin launches Vim externally, you need to
go into the preferences page ('Eeedit
On 8/31/07, Georg Dahn [EMAIL PROTECTED] wrote:
Do as I did: grab Bram's email, save as in EML format, and remove the
headers. If (like me) you got it in 8bit Content-Transfer-Encoding, it's
usable as is for input to the patch program.
Or fetch it from CVS, as I always do. This is much
I'll fix it 9 hours later. Sorry for top-posting because WAP only support this.
On 9/10/07, Nico Weber [EMAIL PROTECTED] wrote:
Hi,
`set cursorline` seems to override the background colors even for
characters that are in group Error. With the default color scheme,
this makes Errors
I'll fix it 9 hours later. Sorry for top-posting because WAP only supports this.
On 9/10/07, Nico Weber [EMAIL PROTECTED] wrote:
Hi,
`set cursorline` seems to override the background colors even for
characters that are in group Error. With the default color scheme,
this makes Errors
On 9/10/07, Ingo Karkat [EMAIL PROTECTED] wrote:
[...]
Okay, but how often (and with how many colorschemes) does this actually
occur? I
personally would rather encounter an occasional weird line (a mere nuisance,
but still fully readable) than barely readable text (as reported with the
On 9/10/07, Tony Mechelynck [EMAIL PROTECTED] wrote:
[...]
The default.vim colorscheme simply invokes the Vim or gvim defaults, whatever
they may be in the Vim version currently running; it has no :highlight
statements: so the patch won't go into the default colorscheme
;
+buf[textlen].byte2 = second;
+}
+#endif
p += utf_ptr2len(p);
width += utf_char2cells(c);
}
Regards,
Edward L. Fox
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more
Hi Tony, thanks for your reply! But we are not talking about the
coverage of UTF-16, we just want to make sure whether X11 uses
UTF-16, or only UCS-16, which only supports BMP. I'm afraid I'll have
no time to test that until this Thursday, so I hope any one could
help. Best regards, Edward Fox
///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
Regards,
Edward L. Fox
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
to inform that I have to pending this patch from submitting
it to the SVN repository until next Monday due to the power failure
last night. Everything will be OK since then so just don't panic.
Regards,
Edward L. Fox
--~--~-~--~~~---~--~~
You received this message from
On 10/2/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Patch 7.1.130
Problem:Crash with specific order of undo and redo. (A.Politz)
Solution: Clear and adjust pointers properly. Add u_check() for
debugging.
Files:src/undo.c, src/structs.h
I shouldn't send out
this patch on the FTP site. Could you please re-upload
it? Thanks a lot!
[...]
Regards,
Edward L. Fox
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Hi Bram,
There are already more than 200 patches. When will 7.2 come out? Any plans?
Regards,
Edward Leap Fox
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
Hi Fan,
On Jan 20, 2008 3:03 PM, Fan Decheng [EMAIL PROTECTED] wrote:
Here I mean on the Windows platform, using Vim 6.4 or 7.1.
I've encountered this problem several times, but don't know whether
there is a
solution:
1. Use gvim to open a file with Chinese characters in its name. For
Hi Tony,
On Jan 21, 2008 11:41 AM, Tony Mechelynck [EMAIL PROTECTED] wrote:
Linxiao wrote:
[...]
Tt, tt, tt... If 'encoding' is other than UTF-8 (or GB18030), Vim cannot
represent all Unicode codepoints in memory; therefore, if you try to edit a
UTF-8 file you run the risk of losing part
Hi Fan,
2008/1/21 Fan Decheng [EMAIL PROTECTED]:
[...]
Here is a snippet from the Vim's reference:
NOTE: Changing this option will not change the encoding of the
existing text in Vim. It may cause non-ASCII text to become
invalid.
It should normally be
Hi all,
On Thu, Mar 27, 2008 at 3:49 AM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Edward, can you please verify that the src/test42.in file is correct in
SVN? It was corrupt in CVS, because the patch command failed to
handle the binary stuff in the diff. You may have had the same
Hi Adrien,
On Thu, Mar 27, 2008 at 3:49 AM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Adrien Lemaire wrote:
Hi Bram,
I'm student in second year in SUPINFO, French informatic engineer school in
5 years. It's You can see more details about this school
Hi all,
On Fri, Mar 28, 2008 at 6:16 AM, Markus Heidelberg
[EMAIL PROTECTED] wrote:
Edward L. Fox, 27.03.2008:
[...]
The repository seems not to be updated. svn status -u doesn't indicate a
new
revision. It's still r916 from patch 7.1.263.
Oh, I just updated the trunk
Hi Bram,
On Sun, May 11, 2008 at 4:16 AM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Patch 7.1.298 (after 7.1.295)
Problem:src/gvimtutor is not distributed.
Solution: Add it to the list of distributed files.
Files: Filelist
Please re-upload this patch to the FTP. I don't find it.
On Wed, Jun 25, 2008 at 1:51 PM, Christian MICHON
[EMAIL PROTECTED] wrote:
[...]
this is the exact reason why I started using git and dropped cvs/svn...
now that you're putting the focus on releasing a collection of files
and not tracking them individually so much anymore (you're tracking a
of your checking-out directory to switch to 7.2
branch.
Note: https://vim.svn.sourceforge.net/svnroot/vim/vim7 will still
point to the 7.1 branch until 7.2 is finally release.
[...]
Happy Vimming!
Subversion mirror maintainer,
Edward L. Fox
On Wed, Jun 25, 2008 at 11:26 PM, Bill McCarthy [EMAIL PROTECTED] wrote:
On Wed 25-Jun-08 2:05am -0600, Edward L. Fox wrote:
[...]
svn co
https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.2/
In the top level of your checking-out directory to switch to 7.2
branch.
Note: https
Why not simply create a certain number of branches in the Subversion
repository for those semi-official patches? That'll be easier for the
end users to check out the patched code or merge the changes from
multiple branches. The patches' developers will also benefit because
we can easily use
On Sun, Nov 16, 2008 at 17:56, Markus Heidelberg
[EMAIL PROTECTED] wrote:
björn, 15.11.2008:
[...]
Avoiding these conflicts is more important than having nice commit logs. But
there should be a way to get both. Edward, do you know why the trunk branch
doesn't have nice commit logs and is
On Mon, Mar 26, 2012 at 16:30, Marc Weber marco-owe...@gmx.de wrote:
[...]
So does anybody have an idea whether this is a (badly written) real job
offer by Bram or whether it is what it looks like: spam?
It is SPAM. Just Google for jobdayseu.com and you'll see many
similar job offer letters
Hi Bram,
A few years ago, we created Subversion mirror of Vim repository
because CVS lacks some important features, such as changeset
management, atomic commit, etc. Nowadays, as we have already switched
to Mercurial, which is a very advanced distributed version control
system as powerful as Git
On Fri, Mar 20, 2009 at 12:33:25PM +0100, Bram Moolenaar wrote:
Tony Mechelynck wrote:
On 18/03/09 19:07, Bram Moolenaar wrote:
Patch 7.2.148
Problem:When searching for $ while 'hlsearch' is set, highlighting
the
character after the line does not work in the
On Wed, Mar 25, 2009 at 12:33:51AM +0100, Tony Mechelynck wrote:
On 25/03/09 00:23, Hisashi T Fujinaka wrote:
I hate to ask dumb questions, but is there some reason this isn't in the
svn repository yet? Is my checkout hosed up somehow?
Thanks.
The SVN repository may lag by up to
On Wed, Mar 25, 2009 at 09:59:27AM +0100, Tony Mechelynck wrote:
On 25/03/09 08:35, Edward L. Fox wrote:
[...]
Looks like the problem is similar to what happened before:
ftp://ftp.vim.org/vol/2 (which is on the chain of softlinked directories
to ftp://ftp.vim.org/pub/vim/) has drwx
SVN repo will catch up with CVS next Wednesday. Sorry for the delay.
在 2010-1-18 上午5:17，Hisashi T Fujinaka ht...@twofifty.com编写：
Anyone know why svn hasn't caught up to this patch (or 328 or 329) yet?
Thanks.
On Tue, 12 Jan 2010, Bram Moolenaar wrote: Patch 7.2.330 Problem:
Tables for
On Thu, Apr 29, 2010 at 20:27, Bram Moolenaar b...@moolenaar.net wrote:
Roland Puntaier wrote:
since I had to set up windows I updated the patch for the python3 support
to vim trunk 7.2.411.
It is attached.
Thanks. I didn't hear about anybody using the patch. That might mean
it works
Hi Bram,
Here's a small patch provided by Liang Peng, alias Bezetek James. He
has fixed the problem in menu/unmenu/emenu series commands.
As my understanding, emenu is designed for scripts to access some
menu items. However, emenu only accepts the localized menu names.
For example, you can use
On Mon, May 3, 2010 at 13:43, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
On 03/05/10 05:55, Edward L. Fox wrote:
Hi Bram,
Here's a small patch provided by Liang Peng, alias Bezetek James. He
has fixed the problem in menu/unmenu/emenu series commands.
As my understanding, emenu
On Mon, May 03, 2010 at 04:51:27PM +0200, Tony Mechelynck wrote:
On 03/05/10 07:50, Edward L. Fox wrote:
[...]
This patch makes both localized and unlocalized menu items appear in
the wild menu. I think it's reasonable because both of them works.
What do you think?
If they are selectable
On Fri, May 07, 2010 at 04:17:36PM +0200, Bram Moolenaar wrote:
Edward L. Fox wrote:
Here's a small patch provided by Liang Peng, alias Bezetek James. He
has fixed the problem in menu/unmenu/emenu series commands.
As my understanding, emenu is designed for scripts to access some
Problem: after 7.2.432, Vim shows E329 error during start up.
Reason: Japanese translation adds a few Japanese-specific menu items
using Japanese paths. Those Japanese paths prevent the correct
English paths from being inserted.
Solution: modify the root menu name back to English when inserting
46 matches
Mail list logo
