headers
Edward L. Fox | 1 Sep 2007 06:52
Picon

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 <Bram <at> moolenaar.net> 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)
cp936 => "GBK" (Chinese)
cp949 => "euc-kr" (Korean) ??? Is this correct?
cp950 => "Big5" (Taiwanese)

Are those above correct? If so, I'll make the "official" patch soon.

> [...]

Regards,

Edward

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bram Moolenaar | 1 Sep 2007 14:10
Picon

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


Edward L. Fox wrote:

> Hi all Chinese, Taiwanese, Japanese and Korean users,
> 
> (cross-posting to vim_multibyte)
> 
> On 9/1/07, Bram Moolenaar <Bram <at> moolenaar.net> 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)
> cp936 => "GBK" (Chinese)
> cp949 => "euc-kr" (Korean) ??? Is this correct?
> cp950 => "Big5" (Taiwanese)
> 
> Are those above correct? If so, I'll make the "official" patch soon.

We already recognize cp949 and cp936.  cp932 was just added, I suggested
recognizing cp950 as "big5".

--

-- 
This is an airconditioned room, do not open Windows.

 /// Bram Moolenaar -- Bram <at> Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
(Continue reading)

Permalink | Reply | 0 comments |
headers
Edward L. Fox | 2 Sep 2007 17:37
Picon

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


Hi Matsumoto and Bram,

On 9/1/07, Bram Moolenaar <Bram <at> moolenaar.net> wrote:
>
> Edward L. Fox wrote:
>
> > Hi all Chinese, Taiwanese, Japanese and Korean users,
> >
> > (cross-posting to vim_multibyte)
> >
> > On 9/1/07, Bram Moolenaar <Bram <at> moolenaar.net> 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)
> > cp936 => "GBK" (Chinese)
> > cp949 => "euc-kr" (Korean) ??? Is this correct?
> > cp950 => "Big5" (Taiwanese)
> >
> > Are those above correct? If so, I'll make the "official" patch soon.
>
> We already recognize cp949 and cp936.  cp932 was just added, I suggested
> recognizing cp950 as "big5".

Here is a quite-simple-and-small patch according to your request.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bram Moolenaar | 4 Sep 2007 10:34
Picon

Searching for Vim scripts


Hello Vim users,

So far we only had the possibility to search for scripts on the Vim
website.  Of course you could use your favorite search engine, but then
you would find any type of file, not just Vim scripts.

I have now added a search box to the search page on www.vim.org where
you can specifically search for Vim scripts, anywhere on the internet.
This uses Google Code Search.  It not only finds individual "*.vim"
files but also scripts inside archives.  E.g., in the Vim distribution.

There is one extra special thing: You search with a regexp pattern.
Thus what you type in the search box are not keywords, it is different
from a normal Google search.  For example, you can search for
"python.*indent" and find matches in "Python indent", "GetPythonIndent"
and "python_highlight_indent_errors".  The regexp synax used is Posix,
it's different from Vim regexp.

Try it out on the Vim search page (second box from the top):
       http://www.vim.org/search.php

Happy Vimming!

--

-- 
A successful man is one who makes more money than his wife can spend.
A successful woman is one who can find such a man.

 /// Bram Moolenaar -- Bram <at> Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
(Continue reading)

Permalink | Reply | 0 comments |
headers
Suresh Govindachar | 5 Sep 2007 02:27
Picon
Favicon

Patch for if_perl.xs


Patch for if_perl.xs attached below.

--Suresh

  *** vim7\src\if_perl.xs	Tue Sep 04 17:12:39 2007
  --- patched\if_perl.xs	Tue Sep 04 16:28:12 2007
  ***************
  *** 40,45 ****
  --- 40,67 ----
    #    define PERL_SUBVERSION SUBVERSION
    #endif

  + /* 
  +  * Quoting Jan Dubois of Active State: 
  +  *
  +  *    ActivePerl build 822 still identifies itself as 5.8.8 but already
  +  *    contains many of the changes from the upcoming Perl 5.8.9 release.
  +  *    
  +  * The changes include addition of two symbols (Perl_sv_2iv_flags, 
  +  * Perl_newXS_flags) introduced in not present in earlier releases.
  +  *
  +  * Jan Dubois suggested the following guarding scheme:
  +  *
  +  */
  + #if (ACTIVEPERL_VERSION >= 822)
  + #  define PERL589_OR_LATER
  + #endif
  + #if (PERL_REVISION == 5) && (PERL_VERSION == 8) && (PERL_SUBVERSION >= 9)
  + #  define PERL589_OR_LATER
(Continue reading)

Permalink | Reply | 4 comments |
headers
Tony Mechelynck | 5 Sep 2007 03:44
Picon
Gravatar

Re: Patch for if_perl.xs


Suresh Govindachar wrote:
> 
> 
> Patch for if_perl.xs attached below.
> 
> --Suresh
> 
> 
>   *** vim7\src\if_perl.xs	Tue Sep 04 17:12:39 2007
>   --- patched\if_perl.xs	Tue Sep 04 16:28:12 2007
>   ***************
>   *** 40,45 ****
>   --- 40,67 ----
>     #    define PERL_SUBVERSION SUBVERSION
>     #endif
>     
>   + /* 
>   +  * Quoting Jan Dubois of Active State: 
>   +  *
>   +  *    ActivePerl build 822 still identifies itself as 5.8.8 but already
>   +  *    contains many of the changes from the upcoming Perl 5.8.9 release.
>   +  *    
>   +  * The changes include addition of two symbols (Perl_sv_2iv_flags, 
>   +  * Perl_newXS_flags) introduced in not present in earlier releases.
>   +  *
>   +  * Jan Dubois suggested the following guarding scheme:
>   +  *
>   +  */
>   + #if (ACTIVEPERL_VERSION >= 822)
(Continue reading)

Permalink | Reply | 2 comments |
headers
Suresh Govindachar | 5 Sep 2007 04:04
Picon
Favicon

RE: Patch for if_perl.xs


  Tony asked:
  > Suresh Govindachar wrote:
  >>
  >> + #if (ACTIVEPERL_VERSION >= 822)
  >> + #  define PERL589_OR_LATER
  >> + #endif
  >> + #if (PERL_REVISION == 5) && (PERL_VERSION == 8) && (PERL_SUBVERSION >= 9)
  >> + #  define PERL589_OR_LATER
  >> + #endif
  >> + #if (PERL_REVISION == 5) && (PERL_VERSION >= 10)
  > 
  > -------------------------------------------------^
  > shouldn't this be (PERL_VERSION >= 9)?  
  > Otherwise Perl 5.9.x won't be regarded as "5.8.9 or later"

  Good catch but I think there is something about perl's 
  version's middle number being even always.  Or it is the 
  case that there will not be any 5.9 at all.  

  (I heard that both 5.8.9 and 5.10 are expected in a few months
   http://www.slideshare.net/acme/whats-new-in-perl-510 .)

  --Suresh

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
(Continue reading)

Permalink | Reply | 1 comment |
headers
Tony Mechelynck | 5 Sep 2007 04:35
Picon
Gravatar

Re: Patch for if_perl.xs


Suresh Govindachar wrote:
>   Tony asked:
>   > Suresh Govindachar wrote:
>   >>
>   >> + #if (ACTIVEPERL_VERSION >= 822)
>   >> + #  define PERL589_OR_LATER
>   >> + #endif
>   >> + #if (PERL_REVISION == 5) && (PERL_VERSION == 8) && (PERL_SUBVERSION >= 9)
>   >> + #  define PERL589_OR_LATER
>   >> + #endif
>   >> + #if (PERL_REVISION == 5) && (PERL_VERSION >= 10)
>   > 
>   > -------------------------------------------------^
>   > shouldn't this be (PERL_VERSION >= 9)?  
>   > Otherwise Perl 5.9.x won't be regarded as "5.8.9 or later"
>  
>   Good catch but I think there is something about perl's 
>   version's middle number being even always.  Or it is the 
>   case that there will not be any 5.9 at all.  
> 
>   (I heard that both 5.8.9 and 5.10 are expected in a few months
>    http://www.slideshare.net/acme/whats-new-in-perl-510 .)
> 
>   --Suresh
> 
> 
> 

well, (PERL_VERSION > 8) then? Some versioning schemes use even numbers for
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bram Moolenaar | 5 Sep 2007 21:47
Picon

patch 7.1.095


Patch 7.1.095
Problem:    The FocusLost and FocusGained autocommands are triggered
	    asynchronously in the GUI.  This may cause arbitrary problems.
Solution:   Put the focus event in the input buffer and handle it when ready
	    for it.
Files:	    src/eval.c, src/getchar.c, src/gui.c, src/gui_gtk_x11.c,
	    src/keymap.h

*** ../vim-7.1.094/src/eval.c	Thu Aug 30 11:10:38 2007
--- src/eval.c	Mon Sep  3 22:48:09 2007
***************
*** 9912,9929 ****

      ++no_mapping;
      ++allow_keys;
!     if (argvars[0].v_type == VAR_UNKNOWN)
! 	/* getchar(): blocking wait. */
! 	n = safe_vgetc();
!     else if (get_tv_number_chk(&argvars[0], &error) == 1)
! 	/* getchar(1): only check if char avail */
! 	n = vpeekc();
!     else if (error || vpeekc() == NUL)
! 	/* illegal argument or getchar(0) and no char avail: return zero */
! 	n = 0;
!     else
! 	/* getchar(0) and char avail: return char */
! 	n = safe_vgetc();
      --no_mapping;
      --allow_keys;
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bram Moolenaar | 5 Sep 2007 23:08
Picon

Re: Patch for if_perl.xs


Suresh Govindachar wrote:

> Patch for if_perl.xs attached below.

Thanks!

Let me know if someone experiences a problem with this.

--

-- 
"Never be afraid to tell the world who you are."
                                        -- Anonymous

 /// Bram Moolenaar -- Bram <at> Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor 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    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |

Gmane