Re: Start Working Today

On Mon, Mar 26, 2012 at 16:30, Marc Weber 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 in many differen

Please help remove "Vim from SVN" from vim.org

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

[Patch] Fix the E329 error under Japanese locale

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

Re: Patch 7.2.432

use it for completion and :emenu. >            (Edward L. Fox / Liang Peng / Bezetek James) > Files:      src/menu.c, src/structs.h To Bram: Thanks a lot for reviewing and including this patch. To Liang: Big congratulations for that your first patch got accepted by Vim. And, many thanks fo

Re: Patch: make "emenu" accept the unlocalized menu names

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 understandi

Re: Patch: make "emenu" accept the unlocalized menu names

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 d

Re: Patch: make "emenu" accept the unlocalized menu names

On Mon, May 3, 2010 at 13:43, Tony Mechelynck 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. >>

Patch: make "emenu" accept the unlocalized menu names

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

Re: Planning Vim 7.3: Python3 support?

On Thu, Apr 29, 2010 at 20:27, Bram Moolenaar 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 without p

Re: Planning Vim 7.3

On Sun, Apr 11, 2010 at 04:33:31PM +0200, Bram Moolenaar wrote: > > Hello Vim users! > > [...] > > Mercurial is going to be the primary method for distribution. I'll > drop CVS, it slows me down too much. Someone else might be able to > mirror the Mercurial repository in CVS, like it's done fo

回复： Re: Patch 7.2.330

SVN repo will catch up with CVS next Wednesday. Sorry for the delay. 在 2010-1-18 上午5:17，"Hisashi T Fujinaka" 编写： 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 Unicode cas... Hi

Re: Patch 7.2.148

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.

Re: Patch 7.2.148

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 m

Re: Patch 7.2.148

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 l

Re: Can we still edit the patches list on google groups?

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

Re: List of Vim patches

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 some

Re: Vim version 7.2a ready for BETA testing

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

Re: Vim version 7.2a ready for BETA testing

s/vim7.2/ In the top level 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 mai

Re: Vim 7.2a in CVS

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 tra

Re: Vim 7.2a in CVS

On Wed, Jun 25, 2008 at 8:00 AM, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > There is something wrong with what CVS did to the files. Especially in > runtime/tutor. Might take a day to sort out. > > Sigh. Why can't I just tell CVS that this is the tree of files I want > to have in the repos

Re: Patch 7.1.298

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 f

Re: test42 failure

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 r

Re: GSoC : Make Vim work as a plugin with Eclipse

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 > > here

Re: test42 failure

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

Re: How to save a UTF-8 file on Windows using a non-ASCII name

Hi Fan, On Jan 21, 2008 1:30 PM, Fan Decheng <[EMAIL PROTECTED]> wrote: > > [...] > > Now every write to the file is OK. However after exiting gvim, the > swap > file is still there. Although your solution seems to solve part of your problem, but I still want to admit that modifying the "encodi

Re: How to save a UTF-8 file on Windows using a non-ASCII name

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 sho

Re: How to save a UTF-8 file on Windows using a non-ASCII name

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 losin

Re: How to save a UTF-8 file on Windows using a non-ASCII name

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

When will 7.2 come out?

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 -~-

Re: Patch 7.1.177

src/globals.h I didn't see 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 -~--~~~~--~~--~--~---

Re: About patch 7.1.130

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

Re: vim and git

e a better choice in such situation because most of its commands are identical to SVN. And their repository format are all the same. So I can easily build up a WebSVN right upon my SVK repository. > > Nico > > > > > Best regards, Edward L. Fox --~--~-~--~~

Re: vim and git

he version control will be modified if you compile Vim in your local working directory. They are always a major trouble to me. Many developers complained for many times, trying to persuade Bram to remove those files out of the version control system, but they did no help at all. That it. > &

Re: patch 7.1.108

rc/if_cscope.c > > [...] I'm sorry 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 --~--~-~--~~--

Re: Handling Unicode codepoints outside the BMP

or Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ > \\\download, build and distribute -- http://www.A-A-P.org /// > \\\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 -~--~~~~--~~--~--~---

Re: Handling Unicode codepoints outside the BMP

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 O

Re: Handling Unicode codepoints outside the BMP

buf[textlen].byte1 = first >> 8; +buf[textlen].byte2 = first; +++textlen; +buf[textlen].byte1 = second >> 8; +buf[textlen].byte2 = second; +} +#endif p += utf_ptr2len(p);

Re: Handling Unicode codepoints outside the BMP

On 9/11/07, Edward L. Fox <[EMAIL PROTECTED]> wrote: > Hi Bram, > > On 9/11/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > [...] > > Thanks for looking into this. Looks good. Except that a check for > > UNICODE16 is needed, if that is defined then we

Re: Handling Unicode codepoints outside the BMP

Hi Bram, On 9/11/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > [...] > Thanks for looking into this. Looks good. Except that a check for > UNICODE16 is needed, if that is defined then we really can use only 16 > bits. Do you mean this? Index: src/screen.c ===

Re: Errors unreadable with cursorline in default color scheme

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 > ($VIMRUNTIM

Re: Errors unreadable with cursorline in default color scheme

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

Re: Errors unreadable with cursorline in default color scheme

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

Re: Errors unreadable with cursorline in default color scheme

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

Re: svn/cvs checkout hangs

On 9/9/07, Suresh Govindachar <[EMAIL PROTECTED]> wrote: > What is the nature of the problem? If there is something wrong > with co from that location, why doesn't update delete files _all_ > the time? Because Bram wants to have /vim/vim7/ always points to the latest stable version. But sv

Re: svn/cvs checkout hangs

On 9/9/07, denis <[EMAIL PROTECTED]> wrote: > > > On Sep 8, 3:10 pm, Bill McCarthy <[EMAIL PROTECTED]> wrote: > > On Sat 8-Sep-07 2:06pm -0600, denis wrote: > > Ah, I remember that - I had to run svn around 5 times before > > ok. i finally synced. Probably after order of 20 times... Yes, that's t

Re: svn/cvs checkout hangs

On 9/9/07, Bill McCarthy <[EMAIL PROTECTED]> wrote: > [...] > svn co https://vim.svn.sourceforge.net/svnroot/vim/vim7 vim7_svn Well, although Bram recommended to checkout from /svnroot/vim/vim7, I'm regretful to say, you may encounter a circumstance that all files in your svn working directory

Re: Proposal: "Modes" for Vim

On 9/2/07, krischik <[EMAIL PROTECTED]> wrote: > > On Sep 2, 4:58 pm, "Richard Hartmann" <[EMAIL PROTECTED]> > wrote: > > On 31/08/07, krischik <[EMAIL PROTECTED]> wrote: > > > > > On Aug 30, 2:46 pm, [EMAIL PROTECTED] wrote: > > > > PS: As "mode" already means something in Vim context, I do not r

Re: 2html make 'charset' when encodig is 'cp932'

Hi Matsumoto and Bram, On 9/1/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > Edward L. Fox wrote: > > > Hi all Chinese, Taiwanese, Japanese and Korean users, > > > > (cross-posting to vim_multibyte) > > > > On 9/1/07, Bram Moolenaar <[EMAIL PRO

Re: 2html make 'charset' when encodig is 'cp932'

On 9/1/07, 范德成 <[EMAIL PROTECTED]> wrote: > [...] > > I know on Windows cp936 is mostly the same as GBK. Yes. In fact cp936 *is* GBK. I'm caring about the remaining code pages' charset names, especially Korean, I'm quite uncertain about that. > > -- >

Re: 2html make 'charset' when encodig is 'cp932'

Hi all Chinese, Taiwanese, Japanese and Korean users, (cross-posting to vim_multibyte) On 9/1/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > [...] > Looks OK to me. > > Can we do the same for cp950, considering it equal to big5? Please help me checking these: cp932 => "Shift_JIS" (Japanese) c

Re: can't update vimscripts with getscript.vim on win32

Hi Charles, On 8/31/07, Charles E Campbell Jr <[EMAIL PROTECTED]> wrote: > > mattn wrote: > > >My home directory is located at "C:\Documents and Settings\mattn\vimfiles" > > on my windows. > >This cause an error while running ":GetLatestVimScripts". > >I made a patch for this problem. Please chec

Re: Buglist

On 8/31/07, Yegappan Lakshmanan <[EMAIL PROTECTED]> wrote: > > Hi, > > On 8/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Hello, > > is there an up-to-date buglist apart from the one which is in the vim > > distribution, > > to look for known bugs first before posting them ? > > > >

Re: can't update vimscripts with getscript.vim on win32

Hi 松本, On 8/31/07, mattn <[EMAIL PROTECTED]> wrote: > Hi, bram and all. > > My home directory is located at "C:\Documents and Settings\mattn\vimfiles" > on my windows. > This cause an error while running ":GetLatestVimScripts". > I made a patch for this problem. Please check and include. I don'

Re: 2html make 'charset' when encodig is 'cp932'

Hi 松本, On 8/31/07, mattn <[EMAIL PROTECTED]> wrote: > Hi, bram and all. > > 2html.vim does not make a 'charset' attribute on 'link' tag > when encoding is 'cp932'. > Most japanese user should specify the encoding as 'cp932' on windows. > (If they want to use 'Shift_JIS' charset.) > > I made a pa

Re: Buglist

On 8/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hello, > is there an up-to-date buglist apart from the one which is in the vim > distribution, > to look for known bugs first before posting them ? So far as I know, there is no such list. But I really want to create one, using Trac (h

Re: patch 7.1.094

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

Re: Announcing Eeedit - Vim plug-in for Eclipse.

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

Re: patch 7.1.094

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 highligh

Re: patch 7.1.094

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 > > [.

Re: Make clean does not remove if_perl.c

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 debug

Re: Bug report: '%' jumps problem

On 8/25/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > Edward L. Fox wrote: > > > Hi developers, > > > > > > Steps to reproduce: > > > > Vim 7.0 has a problem jumping between matching brackets in the > > following case: > > Foo()

Bug report: '%' jumps problem

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 functio

Re: vim-cocoa source code for GSoC final evaluation

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 8/21

Re: test64?

On 8/16/07, Xiaozhou Liu <[EMAIL PROTECTED]> wrote: > > Hi Edward, > > 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? I see... Thanks very much for your report. As I'm not able to access the In

Re: test64?

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? > > > > https://vim.svn.sourceforge.net/svnroot/vim/branc

Re: Small GvimExt patch

Hi Tony, On 8/16/07, Tony Mechelynck <[EMAIL PROTECTED]> wrote: > > Chris Sutcliffe wrote: > > Replied direct to Bram instead of the list... > > > > On 8/15/07, Chris Sutcliffe wrote: > >>> Adding (char *) casts for things that are already character strings? > >>> Isn't this a problem in gcc? > >

Re: patch 7.1.066

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!

Re: Issue with latest w32api and Make_ming.mak

On 8/9/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > Chris Sutcliffe wrote: > > > With the latest version of the w32api that I just released (part of > > the MinGW suite of packages) there is now proper handling of > > __IID_DEFINED__. As a result the Make_ming.mak file in CVS will not > >

Re: Issue with latest w32api and Make_ming.mak

On 8/8/07, Chris Sutcliffe <[EMAIL PROTECTED]> wrote: > > Hey Bram, > > With the latest version of the w32api that I just released (part of > the MinGW suite of packages) there is now proper handling of > __IID_DEFINED__. As a result the Make_ming.mak file in CVS will not > work with the latest w

Re: Fixing bugs in Vim

ould rather join the Yzis team than branch out because the former is much more exciting. OK, I admit that I don't have such ability so I would just continue doing my own work here - supporting the intelligent 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 -~--~~~~--~~--~--~---

Re: Fixing bugs in Vim

you like. I will be a good IT supporter. :-) > > http://gsoc.martintoft.dk/ > > Enjoy :-) > > Best regards, > Martin > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQFGs6agEtBnr8BYnZ4RAhfQAKDqnkTzdOprjBHlJm

Using imactivatekey option for IME users (was: VIM 7.1 compilation error)

g into normal mode from input mode". > Respectfully, > Shawn Y. Kim. > [...] Regards, Edward L. Fox --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---

Re: Fwd: VIM 7.1 compilation error

gnal or something, for me, > it is just more appreciated using hangulinput feature. :-) Just type ":help imactivatekey" and read this part of the manual, maybe it's useful for you. :-) > > [...] In peace, Edward L. Fox --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---

Re: VIM 7.1 compilation error

rasterized, highly- > optimized fonts like sun-gothic + fixed combination. By the way, I guess that Gothic was a Japanese font... Three widely used Korean fonts are named "BatangChe", "DotumChe", "Gulim" and "GulimChe". Maybe I am wrong... > > Any way, good look. > > BRGD. > Shawn from Seoul ;-) Shalom, Edward L. Fox --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---

Fwd: VIM 7.1 compilation error

uot; from now on. And if possible, we could also supply a Hangul input method by using the keymap mechanism, just like the kana (Japanese letters) keymap ported by me. I know nothing about Korean so I hope any Korean friend could help me with this issue. Best regards, Edward L. Fox -- Forwarde

Re: VIM 7.1 compilation error

ring you. I'm just first time here. Just feel free to post any thing here. All people here are very friendly. But you should obey the basic rules and the principles here. For example, bottom-posting. :-) > > Best regards, > Kiwon Um > [...] Cheers, Edward L. Fox --~--~

Re: VIM 7.1 compilation error

ui_mch_set_fontset(GuiFontset fontset) { -gui.current_font = fontset; +gui.fontset = fontset; } #endif > [...] By the way, please always use bottom-posting or interlaced-posting in this mailing list. Bram hates top-posting. Regards, Edward L. Fox --~--~-~--~~~

Re: Handling Unicode codepoints outside the BMP

On 7/29/07, Tony Mechelynck <[EMAIL PROTECTED]> wrote: > [...] > I don't feel up to modifying this platform-dependent code, but I hope that > with the above, someone will be willing. Any takers? I think this work is worth doing. If Bram permits me to mess up the svn trunk, maybe I could set up an

Re: patch 7.1.033

On 7/24/07, Chris Sutcliffe <[EMAIL PROTECTED]> wrote: > > > Patch 7.1.033 > > Problem:A buffer is marked modified when it was first deleted and then > > added again using a ":next" command. (John Mullin) > > Solution: When checking if a buffer is modified use the BF_NEVERLOADED