Hi,

[bug report]

ATOK X (XIM) doesn't work with Vim 6.0 on Linux.  With Vim 5.8, it works
well.

--
Takuhiro Nishioka mailto:takuhiro@...

Takuhiro Nishioka wrote:

> [bug report]
>
> ATOK X (XIM) doesn't work with Vim 6.0 on Linux.  With Vim 5.8, it works
> well.

Well, I have no idea what causes this or how to fix it.  Hopefully you
or someone else can provide additional information.

--
BRIDGEKEEPER: What is your favorite editor?
GAWAIN:       Emacs ...  No Viiiiiiiiiiimmmmmmm!
            "Monty Python and the Holy editor wars" PYTHON (MONTY) SOFTWARE LTD

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
(((   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   )))
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

Hi,

>> ATOK X (XIM) doesn't work with Vim 6.0 on Linux.  With Vim 5.8, it works
>> well.
>
>Well, I have no idea what causes this or how to fix it.  Hopefully you
>or someone else can provide additional information.

OS:                 Turbo Linux 6.1
IM server:          kinput2x
Conversion server:  atok12x
Vim version:        Vim 6.0.11

[bug]

Vim hangs up when using fFtT command with XIM.

[how to reproduce the bug]

1. compile Vim with these options:
     --enable-multibyte --enable-fontset --enable-xim --with-x
2. options value that related with XIM
     iminsert = 0
     imsearch = 0
     imactivatekey=s-space
3. start gvim.
4. enter insert mode.
5. turn on XIM pressing <S-Space>.
6. go back to normal mode pressing <Esc>.
7. press f to find a character.
8. enter a character to search forward.

--
Takuhiro Nishioka mailto:takuhiro@...

Takuhiro Nishioka wrote:

> >> ATOK X (XIM) doesn't work with Vim 6.0 on Linux.  With Vim 5.8, it works
> >> well.
> >
> >Well, I have no idea what causes this or how to fix it.  Hopefully you
> >or someone else can provide additional information.
>
> OS:                 Turbo Linux 6.1
> IM server:          kinput2x
> Conversion server:  atok12x
> Vim version:        Vim 6.0.11
>
> [bug]
>
> Vim hangs up when using fFtT command with XIM.
>
> [how to reproduce the bug]
>
> 1. compile Vim with these options:
>     --enable-multibyte --enable-fontset --enable-xim --with-x
> 2. options value that related with XIM
>     iminsert = 0
>     imsearch = 0
>     imactivatekey=s-space
> 3. start gvim.
> 4. enter insert mode.
> 5. turn on XIM pressing <S-Space>.
> 6. go back to normal mode pressing <Esc>.
> 7. press f to find a character.
> 8. enter a character to search forward.

I can use XIM in my own environment, and it works OK here.  I can't use
the environment you mention.

Hopefully you or someone else can track down this problem and suggest a
good solution.  First thing to do is to find out if it's really Vim that
is the problem, or perhaps the XIM or something else.

--
A parent can be arrested if his child cannot hold back a burp during a church
service.
		 [real standing law in Nebraska, United States of America]

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
(((   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   )))
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

Hi,

>I can use XIM in my own environment, and it works OK here.  I can't use
>the environment you mention.
>
>Hopefully you or someone else can track down this problem and suggest a
>good solution.  First thing to do is to find out if it's really Vim that
>is the problem, or perhaps the XIM or something else.

I'm exchanging some Japanese e-mails with Matsumoto-san
(mattn_jp@...) about this.  I'm not sure that Vim is the problem.
Matsumoto-san said kinput2 version 2 works well. kinput2 version 3 with some
modification doesn't work well.

--
Takuhiro Nishioka mailto:takuhiro@...

There have been a few remarks on the Vim license.  I have attempted to
adjust the license to make more people happy with how Vim can be
distributed.  If you care about this, please read the draft below and
let me know if you have a problem with it.  If a discussion is
necessary, let's do that in the vim-dev maillist.

The main difference is that the license should now be GPL-compatible
(this is not yet confirmed by the FSF though).  This avoids that linking
with a GPL'ed library makes it impossible to distribute Vim.  Debian had
a problem with this.

To make this possible I had to add the possibility to distribute Vim
within a small group of people, without the requirement to send the
maintainer a copy of changes, when asked for.

The result is that the Vim license is more "free" than before.  If you
have contributed code to Vim and do not agree with this new license,
this is the time to speak up.

==============================================================================

SUMMARY

Vim is Charityware.  You can use and copy it as much as you like, but you are
encouraged to make a donation for needy children in Uganda.  Please see |kcc|
below or visit the ICCF web site, available at these mirrors:

	 http://iccf-holland.org/ 	 *iccf* *ICCF*
	 http://www.vim.org/iccf/
	 http://www.iccf.nl/

The Open Publication License applies to the Vim documentation, see
|manual-copyright|.


LICENSE DETAILS

I)  There are no restrictions on distributing unmodified copies of Vim except
     that they must include this license text.  You can also distribute
     unmodified parts of Vim, likewise unrestricted except that they must
     include this license text.  You are also allowed to include executables
     that you made from the unmodified Vim sources, plus your own usage
     examples and Vim scripts.

II) It is allowed to distribute a modified version of Vim, with executables
     and/or source code, when the following four conditions are met:
     1) This license text must be included unmodified.
     2) The modified Vim must be distributed in one of the following five ways:
        a) If you make changes to Vim, you must clearly describe in the
	   distribution how to contact you.  When the maintainer asks you (in
	   any way) for a copy of the modified Vim you distributed, you must
	   make your changes, including source code, available to the
	   maintainer without fee.  The maintainer reserves the right to
	   include your changes in the official version of Vim.  What the
	   maintainer will do with your changes and under what license they
	   will be distributed is negotiable.  If there has been no
	   negotiation, then this license also applies to your changes.
	   The current maintainer is Bram Moolenaar <Bram@...>.  If this
	   changes it will be announced in appropriate places (most likely
	   vim.sf.net, www.vim.org and/or comp.editors).  When it is completely
	   impossible to contact the maintainer, the obligation to send him
	   your changes ceases.  Once the maintainer has confirmed that he
	   has received your changes they will not have to be sent again.
        b) If you have received a modified Vim that was distributed as
	   mentioned under a) you are allowed to further distribute it
	   unmodified, as mentioned at I).  If you make additional changes the
	   text under a) applies to those changes.
        c) Provide all the changes, including source code, with every copy of
	   the modified Vim you distribute.  This may be done in the form of a
	   context diff.  You can choose what license to use for new code you
	   add.  The changes and their license must not restrict others from
	   making their own changes to the official version of Vim.
        d) When you have a modified Vim which includes all changes, as
	   mentioned under c), you can distribute it without the source code
	   for the changes if the following three conditions are met:
	   - The license that applies to the changes permits you to distribute
	     the changes to the Vim maintainer without fee or restriction, and
	     permits the Vim maintainer to include the changes in the official
	     version of Vim without fee or restriction.
	   - You keep the changes for at least three years after last
	     distributing the corresponding modified Vim.  When the maintainer
	     or someone who you distributed the modified Vim to asks you (in
	     any way) for the changes within this period, you must make them
	     available to him.
	   - You clearly describe in the distribution how to contact you.  This
	     contact information must remain valid for at least three years
	     after last distributing the corresponding modified Vim, or as long
	     as possible.
        e) When the GNU General Public License (GPL) applies to the changes,
	   you can distribute the modified Vim under the GNU GPL.
     3) A message must be added, at least in the output of the ":version"
        command and in the intro screen, such that the user of the modified Vim
        is able to see that it was modified.  When distributing as mentioned
        under 2)e) adding the message is only required for as far as this does
        not conflict with the license used for the changes.
     4) The contact information as mentioned under 2) must not be removed or
        changed, except that the person himself can make corrections.

III) If you distribute a modified version of Vim, you are encouraged to use
      the Vim license for your changes and make them available to the
      maintainer, including the source code.  The preferred way to do this is
      by e-mail or by uploading the files to a server and e-mailing the URL.
      If the number of changes is small (e.g., a modified Makefile) e-mailing a
      context diff will do.  The e-mail address to be used is
      <maintainer@...>

IV)  It is not allowed to remove this license from the distribution of the Vim
      sources, parts of it or from a modified version.  You may use this
      license for previous Vim releases instead of the license that they came
      with, at your option.

=== end of license ===

Note:

- If you are happy with Vim, please express that by reading the rest of this
   file and consider helping needy children in Uganda.

- If you link Vim with a library that goes under the GNU GPL, this limits
   further distribution to the GNU GPL.  Also when you didn't actually change
   anything in Vim.

==============================================================================

--
SOLDIER: What? A swallow carrying a coconut?
ARTHUR:  It could grip it by the husk ...
                  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
(((   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   )))
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

Financial Report

As you all know, Vim users are asked to help needy children in Uganda.
Most of the donations and sponsorships are handled by the ICCF Holland
foundation.  The financial report for 2001 is now available here:

	 http://iccf-holland.org/2001.html
	 http://www.vim.org/iccf/2001.html
	 http://www.iccf.nl/2001.html

I'm glad to see that we have been able to send more money to Uganda than
ever before.  This is very much needed, since the project keeps on
growing.  Recently the clinic was extended with a laboratory.  In
January the school will be extended with two more classes.  This means
there are about fifty more children to be sponsored.  If you were
thinking of sponsoring, this is a good moment to start!


Amazon

The sales of the Vim book and other items through Amazon was a new
source of income in 2001.  Please consider using the links on these
pages if you buy something at Amazon USA, UK, DE or FR.  Then ICCF
Holland gets 5% or 15% of the sales and it doesn't cost you anything!

	 http://iccf-holland.org/click.html
	 http://www.vim.org/iccf/click.html
	 http://www.iccf.nl/click.html

--
hundred-and-one symptoms of being an internet addict:
31. You code your homework in HTML and give your instructor the URL.

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
(((   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   )))
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

There have been a few remarks on the updated Vim license.  Although only
details have been changed, this could still change the meaning of the
license.  Therefore I consider it necessary to again ask all Vim
developers to check out this new version.

The intention of this new license is to make more people happy about how
Vim can be distributed.

The main difference is that the license should now be GPL-compatible
(this is not yet confirmed by the FSF though).  This avoids that linking
with a GPL'ed library makes it impossible to distribute Vim.  Debian had
a problem with this.

To make this possible I had to add the possibility to distribute Vim
without the requirement to send the maintainer a copy of changes, when
asked for.  This distribution should then be done with the source code
being available or under the GNU GPL.

The result is that the Vim license is more "free" than before.  If you
have contributed code to Vim and do not agree with this new license,
this is the time to speak up!

If a discussion is necessary, let's do that in the vim-dev maillist.
Replying to the vim-announce maillist won't work.

==============================================================================

SUMMARY

Vim is Charityware.  You can use and copy it as much as you like, but you are
encouraged to make a donation for needy children in Uganda.  Please see |kcc|
below or visit the ICCF web site, available at these mirrors:

	 http://iccf-holland.org/ 	 *iccf* *ICCF*
	 http://www.vim.org/iccf/
	 http://www.iccf.nl/

The Open Publication License applies to the Vim documentation, see
|manual-copyright|.

=== begin of license ===

VIM LICENSE

I)  There are no restrictions on distributing unmodified copies of Vim except
     that they must include this license text.  You can also distribute
     unmodified parts of Vim, likewise unrestricted except that they must
     include this license text.  You are also allowed to include executables
     that you made from the unmodified Vim sources, plus your own usage
     examples and Vim scripts.

II) It is allowed to distribute a modified version of Vim, including
     executables and/or source code, when the following four conditions are
     met:
     1) This license text must be included unmodified.
     2) The modified Vim must be distributed in one of the following five ways:
        a) If you make changes to Vim, you must clearly describe in the
	   distribution how to contact you.  When the maintainer asks you (in
	   any way) for a copy of the modified Vim you distributed, you must
	   make your changes, including source code, available to the
	   maintainer without fee.  The maintainer reserves the right to
	   include your changes in the official version of Vim.  What the
	   maintainer will do with your changes and under what license they
	   will be distributed is negotiable.  If there has been no
	   negotiation, then this license also applies to your changes.
	   The current maintainer is Bram Moolenaar <Bram@...>.  If this
	   changes it will be announced in appropriate places (most likely
	   vim.sf.net, www.vim.org and/or comp.editors).  When it is completely
	   impossible to contact the maintainer, the obligation to send him
	   your changes ceases.  Once the maintainer has confirmed that he
	   has received your changes they will not have to be sent again.
        b) If you have received a modified Vim that was distributed as
	   mentioned under a) you are allowed to further distribute it
	   unmodified, as mentioned at I).  If you make additional changes the
	   text under a) applies to those changes.
        c) Provide all the changes, including source code, with every copy of
	   the modified Vim you distribute.  This may be done in the form of a
	   context diff.  You can choose what license to use for new code you
	   add.  The changes and their license must not restrict others from
	   making their own changes to the official version of Vim.
        d) When you have a modified Vim which includes changes as mentioned
	   under c), you can distribute it without the source code for the
	   changes if the following three conditions are met:
	   - The license that applies to the changes permits you to distribute
	     the changes to the Vim maintainer without fee or restriction, and
	     permits the Vim maintainer to include the changes in the official
	     version of Vim without fee or restriction.
	   - You keep the changes for at least three years after last
	     distributing the corresponding modified Vim.  When the maintainer
	     or someone who you distributed the modified Vim to asks you (in
	     any way) for the changes within this period, you must make them
	     available to him.
	   - You clearly describe in the distribution how to contact you.  This
	     contact information must remain valid for at least three years
	     after last distributing the corresponding modified Vim, or as long
	     as possible.
        e) When the GNU General Public License (GPL) applies to the changes,
	   you can distribute the modified Vim under the GNU GPL version 2 or
	   any later version.
     3) A message must be added, at least in the output of the ":version"
        command and in the intro screen, such that the user of the modified Vim
        is able to see that it was modified.  When distributing as mentioned
        under 2)e) adding the message is only required for as far as this does
        not conflict with the license used for the changes.
     4) The contact information as mentioned under 2) must not be removed or
        changed, except that the person himself can make corrections.

III) If you distribute a modified version of Vim, you are encouraged to use
      the Vim license for your changes and make them available to the
      maintainer, including the source code.  The preferred way to do this is
      by e-mail or by uploading the files to a server and e-mailing the URL.
      If the number of changes is small (e.g., a modified Makefile) e-mailing a
      context diff will do.  The e-mail address to be used is
      <maintainer@...>

IV)  It is not allowed to remove this license from the distribution of the Vim
      sources, parts of it or from a modified version.  You may use this
      license for previous Vim releases instead of the license that they came
      with, at your option.

=== end of license ===

Note:

- If you are happy with Vim, please express that by reading the rest of this
   file and consider helping needy children in Uganda.

- If you link Vim with a library that goes under the GNU GPL, this limits
   further distribution to the GNU GPL.  Also when you didn't actually change
   anything in Vim.

- Once a change is included that goes under the GNU GPL, this forces all
   further changes to also be made under the GNU GPL or a compatible license.

- If you distribute a modified version of Vim, you can include your name and
   contact information with the "--with-modified-by" configure argument or the
   MODIFIED_BY define.

==============================================================================

--
SOLDIER: What? A swallow carrying a coconut?
ARTHUR:  It could grip it by the husk ...
                  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
(((   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   )))
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

I have been attempting to use gvim 6.0 on Windows to type mixed Hebrew
and English text and not having great success.  After setting the
encoding=utf8; the Hebrew keymap and righttoleft mode (set rl), I can
type in logical order and get the Hebrew. Then leaving right to left
mode (set norl), the Hebrew remains in the correct direction. However,
if I put the cursor on each Hebrew letter,  the text will reverse.
Actually, each character that the cursor is placed on displays the
character in the same position in the reverse order (e.g., if in logical
text order a line consists of aleph bet gimel putting the curser on the
gimel will cause it to display aleph in that position. ^L will restore
it. If one then attempts to insert latin characters, the hebrew becomes
permanently reverse.

I am trying to write Perl scripts that will deal with modifying Hebrew
text and will need to mix English (actually Perl code) with the Hebrew.

Are there known bugs and have any been fixed?  Is there a more recently
patched binary for the Windows Gvim?

Thanks.

Stephen Fleischman <sfleisch@...> writes:
>I have been attempting to use gvim 6.0 on Windows to type mixed Hebrew
>and English text and not having great success.  After setting the
>encoding=utf8; the Hebrew keymap and righttoleft mode (set rl), I can
>type in logical order and get the Hebrew. Then leaving right to left
>mode (set norl), the Hebrew remains in the correct direction. However,
>if I put the cursor on each Hebrew letter,  the text will reverse.
>Actually, each character that the cursor is placed on displays the
>character in the same position in the reverse order (e.g., if in logical
>text order a line consists of aleph bet gimel putting the curser on the
>gimel will cause it to display aleph in that position. ^L will restore
>it. If one then attempts to insert latin characters, the hebrew becomes
>permanently reverse.
>
>I am trying to write Perl scripts that will deal with modifying Hebrew
>text and will need to mix English (actually Perl code) with the Hebrew.
>
>Are there known bugs and have any been fixed?  Is there a more recently
>patched binary for the Windows Gvim?
>
>Thanks.

This is an old bug; what exact version of 6.0 are you using, on what version
of Windows?

Ron

It is the Gvim build version 6.0 built on September 26, 2001. Its the
latest Gvim build that I could find for Windows. I'm running on Windows
2000  :-[ (my other computer runs Linux).
Here's the output from the version command:

VIM - Vi IMproved 6.0 (2001 Sep 26, compiled Sep 26 2001 17:12:46)
MS-Windows 32 bit GUI version with OLE support
Big version with GUI.  Features included (+) or not (-):
+autocmd -balloon_eval +browse ++builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments
+cryptv -cscope +dialog_gui +diff +digraphs -ebcdic +emacs_tags +eval
+ex_extra
+extra_search +farsi +file_in_path +find_in_path +folding -footer
+gettext/dyn
-hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall
+linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname
+mouse +mouseshape +multi_byte_ime/dyn +multi_lang +ole -osfiletype
+path_extra
+perl/dyn -postscript +printer +python/dyn +quickfix +rightleft -ruby
+scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax
+tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse
+textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup
-xfontset -xim -xterm_save
    system vimrc file: "$VIM\vimrc"
      user vimrc file: "$HOME\_vimrc"
  2nd user vimrc file: "$VIM\_vimrc"
       user exrc file: "$HOME\_exrc"
   2nd user exrc file: "$VIM\_exrc"
   system gvimrc file: "$VIM\gvimrc"
     user gvimrc file: "$HOME\_gvimrc"
VIM - Vi IMproved 6.0 (2001 Sep 26, compiled Sep 26 2001 17:12:46)
MS-Windows 32 bit GUI version with OLE support
Big version with GUI.  Features included (+) or not (-):
+autocmd -balloon_eval +browse ++builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments
+cryptv -cscope +dialog_gui +diff +digraphs -ebcdic +emacs_tags +eval
+ex_extra
+extra_search +farsi +file_in_path +find_in_path +folding -footer
+gettext/dyn
-hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall
+linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname
+mouse +mouseshape +multi_byte_ime/dyn +multi_lang +ole -osfiletype
+path_extra
+perl/dyn -postscript +printer +python/dyn +quickfix +rightleft -ruby
+scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax
+tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse
+textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup
-xfontset -xim -xterm_save
    system vimrc file: "$VIM\vimrc"
      user vimrc file: "$HOME\_vimrc"
  2nd user vimrc file: "$VIM\_vimrc"
       user exrc file: "$HOME\_exrc"
   2nd user exrc file: "$VIM\_exrc"
   system gvimrc file: "$VIM\gvimrc"
     user gvimrc file: "$HOME\_gvimrc"

I'm not about to start building on Windows. However, when I get a
chance, hopefully sometime this week, I'll get a patched version of VIM
on Linux and try it out.

Thank you for your quick response.

Stephen Fleischman

Ron Aaron wrote:

>Stephen Fleischman <sfleisch@...> writes:
>
>>I have been attempting to use gvim 6.0 on Windows to type mixed Hebrew
>>and English text and not having great success.  After setting the
>>encoding=utf8; the Hebrew keymap and righttoleft mode (set rl), I can
>>type in logical order and get the Hebrew. Then leaving right to left
>>mode (set norl), the Hebrew remains in the correct direction. However,
>>if I put the cursor on each Hebrew letter,  the text will reverse.
>>Actually, each character that the cursor is placed on displays the
>>character in the same position in the reverse order (e.g., if in logical
>>text order a line consists of aleph bet gimel putting the curser on the
>>gimel will cause it to display aleph in that position. ^L will restore
>>it. If one then attempts to insert latin characters, the hebrew becomes
>>permanently reverse.
>>
>>I am trying to write Perl scripts that will deal with modifying Hebrew
>>text and will need to mix English (actually Perl code) w
>>ith the Hebrew.
>>
>>Are there known bugs and have any been fixed?  Is there a more recently
>>patched binary for the Windows Gvim?
>>
>>Thanks.
>>
>
>This is an old bug; what exact version of 6.0 are you using, on what version
>of Windows?
>
>Ron
>
>.
>

Announcing:  Vim (Vi IMproved) version 6.1a BETA
     Author:  Bram Moolenaar et al.


Announcement
------------

This is a bugfix release of Vim.  Since Vim 6.0 many reported problems
have been fixed.  For people who don't compile Vim, this is the first
chance to get all the bug fixes for Vim 6.0.

Also included are new and updated syntax files, translated menus and
messages.  The Vim license has been made compatible with the GNU GPL.

Most of the fixes have already been tested by several people.  But there
might still be a few new problems, that's why this is a BETA version.
If there are no serious problems, the 6.1 release will follow in a
couple of weeks.

Please try out this version and report any problems you encounter.

Once you have installed 6.1a you can find details about the changes
since Vim 6.0 with ":help version-6.1".


What is Vim?
------------

Vim is an almost 100% compatible version of the UNIX editor Vi.  Many new
features have been added: Multi level undo, syntax highlighting, command line
history, filename completion, block operations, etc.  Those who don't know Vi
can probably skip this message, unless you are prepared to learn something new
and useful.  Vim is especially recommended for editing programs.

Vim runs on almost any Unix flavor, MS-DOS, MS-Windows 3.1, MS-Windows
95/98/ME/NT/2000/XP, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and
Amiga.

For more information, see http://vim.sf.net.  This is also a great place
to find Vim tips and scripts!


Where to get it
---------------

Information about which files to download for what system:

         http://vim.sf.net/download.php

The links are for Vim 6.0 though, you need to use the names from below
instead.  All files can be found below this directory:

         ftp://ftp.vim.org/pub/vim/unstable/

NOTE: The "UNRELEASED" directory was used for versions upto 6.0, now
it's "UNSTABLE"!  Avoids the confusion about finding a beta release in
the unreleased directory.

An overview of the files:

Unix:
unix/vim-6.1a.tar.bz2  sources + runtime files, bzip2 compressed
unix/vim-6.1a-rt1.tar.gz runtime files part 1
unix/vim-6.1a-rt2.tar.gz runtime files part 2
unix/vim-6.1a-src1.tar.gz sources part 1
unix/vim-6.1a-src2.tar.gz sources part 2
unix/vim-6.0-6.1a.diff.gz diff between 6.0 and 6.1a

Various:
extra/vim-6.1a-extra.tar.gz  extra files
extra/vim-6.1a-lang.tar.gz  multi-language files
extra/vim-6.0-6.1a-extra.diff.gz extra diff
extra/vim-6.0-6.1a-lang.diff.gz  multi-lang diff
doc/vim61ahtml.zip 	 help files converted to HTML

MS-Windows:
pc/gvim61a.exe 	 self-installing, includes runtime files
pc/vim61art.zip 	 runtime files (all of them)
pc/vim61art1.zip  runtime files (part 1)
pc/vim61art2.zip  runtime files (part 2)
pc/vim61alang.zip  extra files for translated messages and menus
pc/gvim61a.zip 	 GUI binary for Windows 95/98/NT/2000
pc/gvim61aole.zip  GUI binary with OLE support
pc/gvim61a_s.zip  GUI binary for Windows 3.1
pc/vim61ad16.zip  16 bits real mode - works on any system
pc/vim61ad32.zip  32 bits protected mode - needs 386 and DPMI
pc/vim61aw32.zip  console version for Windows NT/2000/XP
pc/vim61asrc.zip  sources for PC (with CR-LF)

Amiga:
amiga/vim61art.tgz  runtime files (always needed)
amiga/vim61abin.tgz  binaries
amiga/vim61asrc.tgz  sources packed for Amiga

OS/2:
Sorry, my OS/2 installation no longer works after installing a new
graphics card.  Hopefully someone else can generate the OS/2 binaries.


Mailing lists
-------------

For user questions you can turn to the Vim mailing list.  There are a lot of
tips, scripts and solutions.  You can ask your Vim questions, but only if you
subscribe.  See http://www.vim.org/mail.html.  An archive is kept at
http://groups.yahoo.com/group/vim.

If you want to help developing Vim or get the latest patches, subscribe to
the vim-dev mailing list.  An archive is kept at
http://groups.yahoo.com/group/vimdev.

Subject specific lists:
Multi-byte issues: vim-multibyte  http://groups.yahoo.com/group/vim-multibyte
Macintosh issues:  vim-mac        http://groups.yahoo.com/group/vim-mac


Reporting bugs
--------------

Send them to <bugs@...>.  Please describe the problem precisely.  All the
time spent on answering mail is subtracted from the time that is spent on
improving Vim!  Always give a reproducable example and try to find out which
settings or other things influence the appearance of the bug.  Try starting
without your own vimrc file: "vim -u NONE -U NONE".  Try different machines
if possible.  See ":help bugs" in Vim.  Send me a patch if you can!

If something needs discussing with other developers, send a message to the
vim-dev mailing list.  You need to subscribe first.


Happy Vimming!

--
hundred-and-one symptoms of being an internet addict:
26. You check your mail. It says "no new messages." So you check it again.

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
///   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   \\\
\\\           Project leader for A-A-P -- http://www.a-a-p.org           ///
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

Announcing:  Vim (Vi IMproved) version 6.1b BETA
     Author:  Bram Moolenaar et al.


Announcement
------------

This is a bugfix release of Vim.  Since Vim 6.0 many reported problems
have been fixed.  For people who don't compile Vim, this is a good
opportunity to get all the bug fixes for Vim 6.0.  Since the 6.1a beta
release more problems have been fixed.

Also included are new and updated syntax files, translated menus and
messages.  The Vim license has been made compatible with the GNU GPL.

Most of the fixes have already been tested by several people.  But there
might still be a few new problems, that's why this is a BETA version.
If there are no serious problems, the 6.1 release will follow in a
couple of weeks.

Please try out this version and report any problems you encounter.

Once you have installed 6.1b you can find details about the changes
since Vim 6.0 with ":help version-6.1".  The changes since version 6.1a
can be seen by using vimdiff on the version6.txt help files of the two
versions.


What is Vim?
------------

Vim is an almost 100% compatible version of the UNIX editor Vi.  Many new
features have been added: Multi level undo, syntax highlighting, command line
history, filename completion, block operations, etc.  Those who don't know Vi
can probably skip this message, unless you are prepared to learn something new
and useful.  Vim is especially recommended for editing programs.

Vim runs on almost any Unix flavor, MS-DOS, MS-Windows 3.1, MS-Windows
95/98/ME/NT/2000/XP, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and
Amiga.

For more information, see http://vim.sf.net.  This is also a great place
to find Vim tips and scripts!


Where to get it
---------------

Information about which files to download for what system:

         http://vim.sf.net/download.php

The links are for Vim 6.0 though, you need to use the names from below
instead.  All files can be found below this directory:

         ftp://ftp.vim.org/pub/vim/unstable/

NOTE: The "UNRELEASED" directory was used for versions upto 6.0, now
it's "UNSTABLE"!  Avoids the confusion about finding a beta release in
the unreleased directory.

An overview of the files:

Unix:
unix/vim-6.1b.tar.bz2  sources + runtime files, bzip2 compressed
unix/vim-6.1b-rt1.tar.gz runtime files part 1
unix/vim-6.1b-rt2.tar.gz runtime files part 2
unix/vim-6.1b-src1.tar.gz sources part 1
unix/vim-6.1b-src2.tar.gz sources part 2
unix/vim-6.1a-6.1b.diff.gz diff between 6.1a and 6.1b

Various:
extra/vim-6.1b-extra.tar.gz  extra files
extra/vim-6.1b-lang.tar.gz  multi-language files
extra/vim-6.1a-6.1b-extra.diff.gz extra diff
extra/vim-6.1a-6.1b-lang.diff.gz multi-lang diff
doc/vim61bhtml.zip 	 help files converted to HTML

MS-Windows:
pc/gvim61b.exe 	 self-installing, includes runtime files
pc/vim61brt.zip 	 runtime files (all of them)
pc/vim61brt1.zip  runtime files (part 1)
pc/vim61brt2.zip  runtime files (part 2)
pc/vim61blang.zip  extra files for translated messages and menus
pc/gvim61b.zip 	 GUI binary for Windows 95/98/NT/2000
pc/gvim61bole.zip  GUI binary with OLE support
pc/gvim61b_s.zip  GUI binary for Windows 3.1
pc/vim61bd16.zip  16 bits real mode - works on any system
pc/vim61bd32.zip  32 bits protected mode - needs 386 and DPMI
pc/vim61bw32.zip  console version for Windows NT/2000/XP
pc/vim61bsrc.zip  sources for PC (with CR-LF)

Amiga:
amiga/vim61brt.tgz  runtime files (always needed)
amiga/vim61bbin.tgz  binaries
amiga/vim61bsrc.tgz  sources packed for Amiga

OS/2:
os2/vim61bos2.zip  binaries
os2/vim61brt.zip  runtime files (same as for pc)


Mailing lists
-------------

For user questions you can turn to the Vim mailing list.  There are a lot of
tips, scripts and solutions.  You can ask your Vim questions, but only if you
subscribe.  See http://www.vim.org/mail.html.  An archive is kept at
http://groups.yahoo.com/group/vim.

If you want to help developing Vim or get the latest patches, subscribe to
the vim-dev mailing list.  An archive is kept at
http://groups.yahoo.com/group/vimdev.

Subject specific lists:
Multi-byte issues: vim-multibyte  http://groups.yahoo.com/group/vim-multibyte
Macintosh issues:  vim-mac        http://groups.yahoo.com/group/vim-mac


Reporting bugs
--------------

Send them to <bugs@...>.  Please describe the problem precisely.  All the
time spent on answering mail is subtracted from the time that is spent on
improving Vim!  Always give a reproducable example and try to find out which
settings or other things influence the appearance of the bug.  Try starting
without your own vimrc file: "vim -u NONE -U NONE".  Try different machines
if possible.  See ":help bugs" in Vim.  Send me a patch if you can!

If something needs discussing with other developers, send a message to the
vim-dev mailing list.  You need to subscribe first.


Happy Vimming!

--
hundred-and-one symptoms of being an internet addict:
227. You sleep next to your monitor.  Or on top of it.

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
///   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   \\\
\\\           Project leader for A-A-P -- http://www.a-a-p.org           ///
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

Yuheng Xie wrote:

>     In gvim 6.x (till 6.1b), when switch to insert mode the second time,
> XIM cannot be evoked.
>     For example, the first time I press "i" and come to insert mode, I could
> press "Ctrl+Space" to evoke my XIM and input Chinese. Then I press "Esc"
> and press "i" again, from now on, "Ctrl+Space" will input a space instead
> of calling out the XIM.
>     Vim in RXVT, gvim for win32, gvim 5.8 and other XWindow programs
> don't have this problem.

I don't know what causes this problem.  I'll forward the message to the
vim-multibyte list.

--
I'd like to meet the man who invented sex and see what he's working on now.

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
///   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   \\\
\\\           Project leader for A-A-P -- http://www.a-a-p.org           ///
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

Bram Moolenaar wrote:
>
> Yuheng Xie wrote:
>
> >     In gvim 6.x (till 6.1b), when switch to insert mode the second time,
> > XIM cannot be evoked.
> >     For example, the first time I press "i" and come to insert mode,
> > I could press "Ctrl+Space" to evoke my XIM and input Chinese. Then I
> > press "Esc" and press "i" again, from now on, "Ctrl+Space" will
> > input a space instead of calling out the XIM.
> >     Vim in RXVT, gvim for win32, gvim 5.8 and other XWindow programs
> > don't have this problem.
>
> I don't know what causes this problem.  I'll forward the message to the
> vim-multibyte list.

I met such a problem when the next variables were introduced (gvim
tries to control IM status, but there was some issue... uhmm...).
Now I have no problem with these setting. It might help you.

     set noimdisable noimcmdline imsearch=0 iminsert=0
     set imactivatekey=S-space

Or recent Yasuhiro's patch (imactivatekey related) might help?
I didn't try that patch.

Regards,
namsh

Announcing:  Vim (Vi IMproved) version 6.1
     Author:  Bram Moolenaar et al.


Announcement
------------

This is a bugfix release of Vim.  Since Vim 6.0 many reported problems
have been fixed.  Also included are new and updated syntax files,
translated menus and messages.  The Vim license has been made compatible
with the GNU GPL.

The past few weeks beta testing has been done by many people.  This is
the most stable Vim ever made.

Once you have installed 6.1 you can find details about the changes
since Vim 6.0 with ":help version-6.1".  There is a long list of fixed
bugs.


What is Vim?
------------

Vim is an almost 100% compatible version of the UNIX editor Vi.  Many new
features have been added: Multi level undo, syntax highlighting, command line
history, filename completion, block operations, etc.  Those who don't know Vi
can probably skip this message, unless you are prepared to learn something new
and useful.  Vim is especially recommended for editing programs.

Vim runs on almost any Unix flavor, MS-DOS, MS-Windows 3.1, MS-Windows
95/98/ME/NT/2000/XP, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and
Amiga.

For more information, see http://vim.sf.net.  This is also a great place
to find Vim tips and scripts!


Where to get it
---------------

Information about which files to download for what system:

         http://vim.sf.net/download.php

All files can be found below this directory:

         ftp://ftp.vim.org/pub/vim/

An overview of the files:

UNIX:
unix/vim-6.1.tar.bz2  sources + runtime files, bzip2 compressed
   unix/vim-6.1-rt1.tar.gz   runtime files part 1
   unix/vim-6.1-rt2.tar.gz   runtime files part 2
   unix/vim-6.1-src1.tar.gz   sources part 1
   unix/vim-6.1-src2.tar.gz   sources part 2
unix/vim-6.0-6.1.diff.gz diff between 6.0 and 6.1

VARIOUS:
extra/vim-6.1-extra.tar.gz extra files
extra/vim-6.1-lang.tar.gz multi-language files
extra/vim-6.0-6.1-extra.diff.gz extra files diff
doc/vim61html.zip  help files converted to HTML

MS-WINDOWS:
pc/gvim61.exe 	 self-installing, includes runtime files
pc/vim61rt.zip 	 runtime files (all of them)
   pc/vim61rt1.zip 	  runtime files (part 1)
   pc/vim61rt2.zip 	  runtime files (part 2)
pc/vim61lang.zip  extra files for translated messages and menus
pc/gvim61.zip 	 GUI binary for Windows 95/98/NT/2000
pc/gvim61ole.zip  GUI binary with OLE support
pc/gvim61_s.zip 	 GUI binary for Windows 3.1
pc/vim61d16.zip 	 16 bits real mode - works on any system
pc/vim61d32.zip 	 32 bits protected mode - needs 386 and DPMI
pc/vim61w32.zip 	 console version for Windows NT/2000/XP
pc/vim61src.zip 	 sources for PC (with CR-LF)

AMIGA:
amiga/vim61rt.tgz  runtime files (always needed)
amiga/vim61bin.tgz  binaries
amiga/vim61src.tgz  sources packed for Amiga

OS/2:
os2/vim61os2.zip  binaries
os2/vim61rt.zip 	 runtime files (same as for pc)


Mailing lists
-------------

For user questions you can turn to the Vim mailing list.  There are a lot of
tips, scripts and solutions.  You can ask your Vim questions, but only if you
subscribe.  See http://www.vim.org/mail.html.  An archive is kept at
http://groups.yahoo.com/group/vim.

If you want to help developing Vim or get the latest patches, subscribe to
the vim-dev mailing list.  An archive is kept at
http://groups.yahoo.com/group/vimdev.

Subject specific lists:
Multi-byte issues: vim-multibyte  http://groups.yahoo.com/group/vim-multibyte
Macintosh issues:  vim-mac        http://groups.yahoo.com/group/vim-mac


Reporting bugs
--------------

Send them to <bugs@...>.  Please describe the problem precisely.  All the
time spent on answering mail is subtracted from the time that is spent on
improving Vim!  Always give a reproducable example and try to find out which
settings or other things influence the appearance of the bug.  Try starting
without your own vimrc file: "vim -u NONE -U NONE".  Try different machines
if possible.  See ":help bugs" in Vim.  Send me a patch if you can!

If something needs discussing with other developers, send a message to the
vim-dev mailing list.  You need to subscribe first.


Happy Vimming!

--
Any resemblance between the above views and those of my employer, my terminal,
or the view out my window are purely coincidental.  Any resemblance between
the above and my own views is non-deterministic.  The question of the
existence of views in the absence of anyone to hold them is left as an
exercise for the reader.  The question of the existence of the reader is left
as an exercise for the second god coefficient.  (A discussion of
non-orthogonal, non-integral polytheism is beyond the scope of this article.)
						 (Ralph Jennings)

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
///   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   \\\
\\\           Project leader for A-A-P -- http://www.a-a-p.org           ///
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

hello bram and all.

I can turn preeditstate for OnTheSpot with this patch.
I tested on kinput2 version3.1beta4.

Thanks.

BTW)
The sent file was wrapped in the e-mail.
Sorry.


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx

Yasuhiro Matsumoto wrote:

> I can turn preeditstate for OnTheSpot with this patch.
> I tested on kinput2 version3.1beta4.

Thanks.

I wonder how safe it is to include this.  I suppose it should at least
be tested with other input methods.

--
Often you're less important than your furniture.  If you think about it, you
can get fired but your furniture stays behind, gainfully employed at the
company that didn't need _you_ anymore.
				 (Scott Adams - The Dilbert principle)

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
///   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   \\\
\\\           Project leader for A-A-P -- http://www.a-a-p.org           ///
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

Hello, VIM-gurus!

I have a multibyte-related question. Is this the right place to ask
such kind of questions?

There it is:

On certain files, after trying to perform file encoding conversion (:e
++enc=cp866, for example), I receive "Not converted" error, and the
file remains in wrong encoding. (VIM 6.1, iconv.dll - 423.640,
09.03.01 04:49, WinXP)

There is a small example: I can't open this two-line file (attached)
in VIM in the right encoding (cp866) and performing ":e ++enc=cp866"
command fails. It's interesting, that if I delete two chars from this
file (line 1 col 57 and line 2 col 40), and reload it after saving
changes (or use ":e ++enc=cp866" command) the file will be shown in
right encoding (cp866).

Can anyone explain me what's wrong there? If there are ways to _force_
file encoding conversion?

Thank you!

--
Best regards,
  Valery Kondakoff                  mailto:strauss@...
  http://www.nbk.orc.ru             Ne Bey Kopytom
  http://www.nbk.orc.ru/mtb         MTB riding in Moscow

In general, they do what you want, unless you want consistency.
--Larry Wall

* Исправлен глюк, когда полностью закрашенное символом '█' знакоместо
   на графике T-Hist заменял на символ '▐').

Valery Kondakoff <strauss@...> writes:
>Hello, VIM-gurus!

Hello, Valery.

>I have a multibyte-related question. Is this the right place to ask
>such kind of questions?

Indeed it is!

>There it is:
>
>On certain files, after trying to perform file encoding conversion (:e
>++enc=cp866, for example), I receive "Not converted" error, and the
>file remains in wrong encoding. (VIM 6.1, iconv.dll - 423.640,
>09.03.01 04:49, WinXP)
...
>Can anyone explain me what's wrong there? If there are ways to _force_
>file encoding conversion?

You are doing things correctly, but it appears you have a defective iconv.dll.
You should download mine:

     http://www.mossbayeng.com/~ron/vim/iconv.dll

which should be the libiconv 1.7.0.1.  Try and see if it fixes your problem;
for me, trying on Windows Me, it worked fine with your example file.

Best regards,

Ron

Hello, Ron!

7 └яЁхы№ 2002 у., you wrote to me:


>>On certain files, after trying to perform file encoding conversion (:e
>>++enc=cp866, for example), I receive "Not converted" error, and the
>>file remains in wrong encoding. (VIM 6.1, iconv.dll - 423.640,
>>09.03.01 04:49, WinXP)

RA> You are doing things correctly, but it appears you have a defective
iconv.dll.
RA> You should download mine:
RA>     http://www.mossbayeng.com/~ron/vim/iconv.dll
RA> which should be the libiconv 1.7.0.1.  Try and see if it fixes your problem;
RA> for me, trying on Windows Me, it worked fine with your example file.

Thank you for your answer. I downloaded your iconv.dll and replaced
the previous one (downloaded from http://vim.sourceforge.net/, BTW the
both files are the same size) but the problem still remains. :(

There are my settings (default encoding is cp1251):
set fileencodings=cp866,koi8-r,cp1251

When I'm opening the file "ru_cp866.txt" (:e ru_cp866.txt) it is open
in cp1251 encoding. Then I'm trying to perform force encoding (:e
++enc=cp866), after pressing <enter> on command line I see report:
"ru_cp866.txt" [NOT converted] 2L, 116C" and the file remains in wrong
cp1251 encoding.

But when I delete two chars from this file (they are ASCII graphics:
Col 57, Line 1 and Col 40 Line 2), the file opens in right encoding
(cp866).

Do you have any idea - what may be wrong?

--
Best regards,
  Valery Kondakoff                  mailto:strauss@...
  http://www.nbk.orc.ru             Ne Bey Kopytom
  http://www.nbk.orc.ru/mtb         MTB riding in Moscow

*** The previous line contains the naughty word "$&".
if /(ibm|apple|awk)/; # :-)
--Larry Wall

Hello, Ron!

7 └яЁхы№ 2002 у., you wrote to me:

>>Thank you for your answer. I downloaded your iconv.dll and replaced
>>the previous one (downloaded from http://vim.sourceforge.net/, BTW the
>>both files are the same size) but the problem still remains. :(

RA> Sorry, try again.  I had an older iconv.dll there.  The newer one is in its
RA> place.

Thank you.

I (re)downloaded updated file... Unfortunately, the problem still exist.
:(
I can reproduce this problem on two machines (at home and at work),
both running WinXP (currently I have no access to any PC, that runs
Win9* or WinME).

Example file that I send in my previous message is displayed
correctly in all the editors (Bred2, FAR internal editor/viewer,
Windows internal command-line "Edit"), but, unfortunately, not in VIM...

I'm very new to VIM-world. Maybe I'm doing smth wrong? Smth with VIM
settings?

BTW, I have another one "encoding"-related problem. There it is:
currently I need to view/edit files in three encodings - cp1251
(windows default), cp866 (DOS) and koi8-r (Unix one). When trying to
perform some kind of (semi)automatic encoding detection I wrote in my
vimrc: "set fileencodings=cp866,koi8-r,cp1251".

This setting works as expected - in most cases files are opened in
correct encoding, but there is an additional drawback: most files with
no local letters (with no russian language inside) are opened in cp866
(the first one mentioned in "fileencodings") encoding instead of the
default cp1251. And if I'm changing the encoding order to "set
fileencodings=cp1251,cp866,koi8-r" the other two encodings are not
(auto)detected anymore, becouse they are "stealed" with cp1251...

Please, let me understand - if there is smth I can do with atomatic
encoding detection? I just want to open _all_ files in cp1251, except
files that are encoded in cp866 or koi8-r... Is it possible?

Thank you!

--
Best regards,
  Valery Kondakoff                  mailto:strauss@...
  http://www.nbk.orc.ru             Ne Bey Kopytom
  http://www.nbk.orc.ru/mtb         MTB riding in Moscow

[End of diatribe. We now return you to your regularly scheduledprogramming...]
--Larry Wall

Hello, vim-gurus!

   I'm very new to VIM-world, but I like the editor very much and I
   _really_ want to set it up to work with multiple file encodings.

   There is what I need: I'm from Russia, and I'm working under WinXP
   (GVIM 6.1). I need to set up VIM to work with three encodings:
   cp1251 (windows default), cp866 (DOS), koi8-r (unix).

   First I was trying to set default VIM encoding to 'cp1251' and
   fileencodings to cp866, koi8-r and cp1251:

       set encoding=cp1251
       set fileencodings=cp866,koi8-r,cp1251

   Very well, I can read and write most files in these encodings, but
   some of files are _not_ converted to the 'right' encoding.

   After some research it was found (with great help of Ron Aaron -
   thank you a lot) that "force" file encoding (':e ++enc=cp866', for
   example) works correctly _only_ if 'encoding' is set to 'utf-8'.

   OK. With help of Ron and after hours of reading the docs I have set
   up my 'vimrc' like this:

       let &termencoding = &encoding
       set encoding=utf-8
       set fileencodings=ucs-bom,cp1251,cp866,koi8-r
       set guifont=courier_new:h11

   Now I can read and write in all of the mentioned encodings and
   convert between them.

   But there are another two problems (they become apparent only when
   default encoding was set to 'utf-8':

       first:

   when I switch the keyboard layout from English to Russian all the
   keyboard shortcuts in Normal mode ('i' for entering Insert mode, 'v'
   to enter Visual mode etc) stops working. When I was using 'set
   encoding=cp1251' I was able to set langmap with all the needed
   character pairs for cp1251 encoding.

   How can I do smth like this for utf-8 encoding?

   There is what is saying about utf-8 langmaps in docs:
>       This only works for 8-bit characters.  The value of 'langmap' may be
>       specified with multi-byte characters (e.g., UTF-8), but only the lower
>       8 bits of each character will be used

   Does it means that it is impossible to me to use langmaps? Am I
   forced to use keymaps instead of langmaps?

       second (this is far more important):

   when I set up VIM to use 'utf-8' as default encoding it is
   _impossible_ to copy Russian text from VIM to another Windows
   application (and vice versa: from another Windows app to VIM).
   Russian text is pasted as garbage. (There are no problems, when I'm
   copying Russian text between VIM buffers).

   What setting controls the encoding of the text in the clipboard?

   So - there are my question: is it possible to set up VIM to _work_
   with multiple file encodings? Please, help me understand what I'm
   doing wrong, and how do I need to set up VIM.

   (Please, excuse my ugly English, I'm trying to be as clear as
   possible. I'm ready to give all additional info you need, or perform
   needed testing).

   Thank you!

--
Best regards,
  Valery Kondakoff                  mailto:strauss@...
  http://www.nbk.orc.ru             Ne Bey Kopytom
  http://www.nbk.orc.ru/mtb         MTB riding in Moscow

I think it's a new feature. Don't tell anyone it was an accident. :-)
--Larry Wall

np: Gus Gus - Acid Milk (This Is Normal) [stopped]

On Mon, Apr 08, 2002 at 10:50:38PM +0400, Valery Kondakoff wrote:
>   when I set up VIM to use 'utf-8' as default encoding it is
>   _impossible_ to copy Russian text from VIM to another Windows
>   application (and vice versa: from another Windows app to VIM).
>   Russian text is pasted as garbage. (There are no problems, when I'm
>   copying Russian text between VIM buffers).
>
>   What setting controls the encoding of the text in the clipboard?

I get this, too; pasting non-ASCII text to and from gvim doesn't work
for me.

In UTF-8, I can't copy "├б" or "уБЛ" to *or* from gvim.

In latin1, I can paste "├б" *to* gvim, but *from* gives garbage.

Strangely, "sjis" doesn't appear to work at all: both pasting, IM'ing
and reading "уБЛ" from a file breaks.  (Pasting and IMing result in a
default "?"; reading results in garbage.) I'm not sure why this is
happening, but I can't test pasting out of gvim in sjis due to it.

This happens with UCS2, as well (very strange), but not with UCS4.  If I
already have "уБЛ" onscreen, and change to UCS2, it stays (and copying it
to the clipboard does not work), but if I change to SJIS, it's converted
to garbage.  There's something weird going on.

By the way, I noticed something else: gvim is defaulting to IME input the
first time I do a search.  (Subsequent searches are fine--back to English
input--and this doesn't happen with :commands, just /searches.) This has
been happening a while, I think, but I forgot to investigate it at first
and I've since apparently habitually worked around it and so completely
forgot about it.  I'll poke at this later; it's probably the same kind
of problem we dealt with earlier.

VIM - Vi IMproved 6.1 (2002 Mar 24, compiled Mar 24 2002 16:04:44)
MS-Windows 32 bit GUI version with OLE support
Big version with GUI.  Features included (+) or not (-):
+autocmd -balloon_eval +browse ++builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+cryptv -cscope +dialog_gui +diff +digraphs -ebcdic +emacs_tags +eval +ex_extra
+extra_search +farsi +file_in_path +find_in_path +folding -footer +gettext/dyn
-hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall
+linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname
+mouse +mouseshape +multi_byte_ime/dyn +multi_lang +ole -osfiletype +path_extra
+perl/dyn -postscript +printer +python/dyn +quickfix +rightleft -ruby
+scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax
+tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse
+textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup
-xfontset -xim -xterm_save

Hmm; dynamic iconv loading.  Is there any wsy to tell if it's
successfully loaded it or not?  I tried renaming my iconv.dll, loading Vim
and setting encoding=sjis, and nothing changed, so I'm suspicious that
it's really loading iconv.  (I'd expect that, if it didn't have iconv
available, it'd not know that "sjis" is a valid encoding, however--"set
encoding=nothing" does give an error.)

--
Glenn Maynard

Glenn Maynard wrote:

> I get this, too; pasting non-ASCII text to and from gvim doesn't work
> for me.
>
> In UTF-8, I can't copy "├б" or "уБЛ" to *or* from gvim.

The Win32 clipboard code in Vim doesn't do conversion of encoding and
doesn't indicate what encoding is being used.  This suggests something
is missing here.  Hopefully someone who knows about Win32 clipboard
stuff can look into this.

> This happens with UCS2, as well (very strange), but not with UCS4.

For both encodings Vim uses UTF-8 internally, thus it's strange this
makes a difference.

> By the way, I noticed something else: gvim is defaulting to IME input the
> first time I do a search.  (Subsequent searches are fine--back to English
> input--and this doesn't happen with :commands, just /searches.) This has
> been happening a while, I think, but I forgot to investigate it at first
> and I've since apparently habitually worked around it and so completely
> forgot about it.  I'll poke at this later; it's probably the same kind
> of problem we dealt with earlier.

Something with the 'imsearch' option?

--
hundred-and-one symptoms of being an internet addict:
157. You fum through a magazine, you first check to see if it has a web
      address.

  ///  Bram Moolenaar -- Bram@... -- http://www.moolenaar.net  \\\
///   Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim   \\\
\\\           Project leader for A-A-P -- http://www.a-a-p.org           ///
  \\\  Help me helping AIDS orphans in Uganda - http://iccf-holland.org  ///

On Thu, Apr 11, 2002 at 11:29:07PM +0400, Valery Kondakoff wrote:
> 11 └яЁхы№ 2002 у., you wrote to me:

What?  Your encoding is wrong, I think.

> Excuse me, if I'm wrong, but I was thinking, that the best way to
> solve this issue is to convert win32 clipboard to '&termencoding'
> value.
>
> So, when I'm setting IM like this:
>
>     let &termencoding = &encoding              " this is 'cp1251'
>     set encoding=utf-8
>     set fileencodings=ucs-bom,cp1251,cp866,koi8-r
>
> The clipboard will always be converted to the encoding, I'm using for
> _writing_ text.

I don't think termencoding should do anything when in a GUI.  I think
that on NT systems, at least, the clipboard should *always* be Unicode,
so there's no loss.  I don't know about 9x, though.  (I also know little
about the clipboard; I'll consider checking it out.)

--
Glenn Maynard

Hello, Bram!

11 └яЁхы№ 2002 у., you wrote to me:

>> I get this, too; pasting non-ASCII text to and from gvim doesn't work
>> for me.

BM> The Win32 clipboard code in Vim doesn't do conversion of encoding and
BM> doesn't indicate what encoding is being used.  This suggests something
BM> is missing here.  Hopefully someone who knows about Win32 clipboard
BM> stuff can look into this.

Thank you for your reply (and one more thank for VIM).

Excuse me, if I'm wrong, but I was thinking, that the best way to
solve this issue is to convert win32 clipboard to '&termencoding'
value.

So, when I'm setting IM like this:

     let &termencoding = &encoding              " this is 'cp1251'
     set encoding=utf-8
     set fileencodings=ucs-bom,cp1251,cp866,koi8-r

The clipboard will always be converted to the encoding, I'm using for
_writing_ text.

What do you think? Is this reasonable? Or am I wrong?

Please, please, multibyte developers, do somethig with this! :)
It's almost impossible to use a text editor without an ability to
exchange text with other apps using clipboard!

And one more question: why file encoding conversion works properly
_only_ when 'encoding' is set to 'utf-8'? And after setting 'encoding',
for example to 'cp1251', I can't convert file encoding for the same
files, that were successfully converted using 'set encoding=utf-8'?
Or (maybe) this is a bug?

Thank you once again!

--
Best regards,
  Valery Kondakoff                  mailto:strauss@...
  http://www.nbk.orc.ru             Ne Bey Kopytom
  http://www.nbk.orc.ru/mtb         MTB riding in Moscow

Chip Salzenberg sent me a complete patch to add System V IPC (msg, sem andshm
calls), so I added them. If that bothers you, you can always undefinethem in
config.sh. :-)
--Larry Wall

np: Belly - Untogether (Star)

Hello,

The UTF8_STRING atom lets me copy and paste between mozilla
and xterm. Do we intend to support it in vim?

Noah

On Thu, Apr 11, 2002 at 08:22:29PM +0200, Bram Moolenaar wrote:
> Something with the 'imsearch' option?

Setting imsearch=0 fixed this.  (The oddity of the IME turning off was
due to a forgotten IME keybinding I made: ^U in the IME turns it off.  I
was hitting ^U in Vim, to clear the IME input, but it was really the IME
keybinding.)

I'd suggesting documenting the fact that iminsert and imsearch follow
the IME status regardless of how it's turned on or off.  Most IME2K
users are likely to use IME bindings to toggle it, not Vim bindings (as
they're system-wide).

"Note that this option changes when the input method is toggled
in Insert mode, such as with CTRL-^ |c_CTRL-^|."  (Or something
clearer.)

I'd still like to see iminsert (and now imsearch) default to 0 rather
than 2 when using this IME.  (Or, perhaps, default to the state the IME
was in when Vim loads; that might help to give Vim the same IME behavior
in input mode as other applications give with other IMEs.)

--
Glenn Maynard

hello bram and all.

clear_next_cell don't work correctly.
on some case, following text will be erased.
this happend with text included underline.

old text:
   [][][]

new text:(override)
   [][][]
   |
   v
   []
   ~~  <= underline

following patch will be fix this.
this patch made by AIDA Shinra.
thanks.

diff -Nru ../vim.old/src/screen.c src/screen.c
--- ../vim.old/src/screen.c Wed Mar 13 04:59:15 2002
+++ src/screen.c Sat Apr 13 10:02:33 2002
@@ -5168,11 +5168,14 @@
		  * cell.  Also when overwriting the left halve of a two-cell
		  * char with the right halve of a two-cell char. */
		 if (has_mbyte && ptr[mbyte_blen] == NUL
+ 	 && !clear_next_cell
			 && ((mbyte_cells == 1 && (*mb_off2cells)(off) > 1)
			     || (mbyte_cells == 2
				 && (*mb_off2cells)(off) == 1
				 && (*mb_off2cells)(off + 1) > 1)))
		     clear_next_cell = TRUE;
+  else
+ 	    clear_next_cell = FALSE;
#endif
		 ScreenLines[off] = *ptr;
		 ScreenAttrs[off] = attr;
@@ -5216,10 +5219,7 @@
		 col += mbyte_cells;
		 ptr += mbyte_blen;
		 if (clear_next_cell)
-  {
		     ptr = (char_u *)" ";
- 	    clear_next_cell = FALSE;
-  }
	     }
	     else
#endif


_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com