At 11:06 Uhr +0900 2000-02-26, david craig wrote:
>Thanks for clarifying; it's appreciated.  A question
>I meant to ask in my first post: Do the version numbers
>of the respective applications have anything to do
>with one another?

Yes.

>I suppose that the presumption would
>be that the application version number refers to that
>of the port, then?

Right

>(To say it another way, would versions
>5.6 of these two implementations of VIM have, in theory,
>an essential parity in VIM features, differing primarily
>in how the authors went about implementing them, and
>perhaps what goodies above and beyond VIM itself the
>authors throw in?)

Correct.

MacVim on my page was compiled before 5.6 was available and I left my
compiler just after putting it on my homepage. In the meantime Dany took
the 5.6 release, fixed some bugs and released it on his page.

When I'm back in Germany I will download 5.6 release (+patches) and Dany's
patches and build a new version which I will put on my homepage.

The main differences are:
Dany's version is FAT, I have separate binaries for 68k and PPC
My 68k version has syntax disabled, don't know about Dany's.
My version is compiled with CWPro2 Dany's with CW9 (IIRC).

The rule of thump is:
Whoever has time puts a binary on his page.

Axel

who would be surprised to see this on the list, becuase I'm writing from a
different address than my subscribe address.

--
Adults get far more pleasure from adultery
than children do from infancy

Dear Asai-san,

* ASAI Kenichi <asai@...> [000307 09:06]:
> Dear Mr. Sven Guckes, Thank you for compiling vim on MacOS.

You are welcome!  But the credit for this goes to other people.

> I have downloaded it and now trying to use it on my PowerBook.
> One thing that is quite important for me is multi-byte support.
> Would it be possible to ask you re-compile vim with
> --enable-multibyte and --enable-fontset options?
>
> If it cannot be done without subtle code modification, please ignore
> this e-mail.  I do not want to make you trouble with this when you
> have other things to fix.  If it can be done easily without changing
> code, however, may I ask you to re-compile with those options?
> (I have no compiler with me here...)
> It would be very helpful for me to use my language on vim.

Well, I am sure it can be done.
Both Axel Kielhorn and Dany St-Amant have released a binary -
maybe they can also maintain a binary with those features.
Axel?  Dany?  [I'll CC this to the Vim Mac mailing list.]

Sven

--
Sven Guckes guckes@...  | vim-mac@...: Maillist for "Vim on MacOS"
VIMMAC Info on current development: http://www.vim.org/macs.html

Dear VimMac developpers,

Thank you very much for making vim for MacOS, and thank you, Mr. Sven
Guckes, for replying very promptly.  Before the vim I requested is
compiled, I would like to ask another options (if it is possible).

In my previous mail, I requested the following two options:

--enable-multibyte
--enable-fontset options

These two options are quite important for non-English support.  Added
to this, I would like to ask the following two options.

+langmap (or HAVE_LANGMAP); around line 70 of feature.h
--enable-perlinterp
something equivalent to --enable-xim (i.e., control on Macintosh Input
Metohd)

The +langmap option is also very important when we *input* non-English
languages.  Namely, when going into insert mode, the language input
method is turned on, and when going back, off.

The latter two is my hope that vim on Macintosh will support them in
the future.  I think you need subtle code change to achieve them, so I
do not insist on them very much.  But if they can be done very easily,
I want them quite much.  (When these features are available, I think I
can read my e-mails perfectly on my PowerBook...)

Thank you in advance.

# Is it easy to compile VIM if I buy CodeWarrior Pro?  I might
# consider compiling it by myself.  VimMac can be the most important
# application on my PowerBook...

Sincerely,

---
Kenichi Asai


---------------------------------------------------------------------
>Date: Tue, 7 Mar 2000 16:58:04 +0100
>From: Sven Guckes <guckes@...>
>To: ASAI Kenichi <asai@...>
>Cc: VIM on MacOS Development <vim-mac@...>
>Subject: Re: vim on MacOS with multi-byte available?
>
>Dear Asai-san,
>
>* ASAI Kenichi <asai@...> [000307 09:06]:
>> Dear Mr. Sven Guckes, Thank you for compiling vim on MacOS.
>
>You are welcome!  But the credit for this goes to other people.
>
>> I have downloaded it and now trying to use it on my PowerBook.
>> One thing that is quite important for me is multi-byte support.
>> Would it be possible to ask you re-compile vim with
>> --enable-multibyte and --enable-fontset options?
>>
>> If it cannot be done without subtle code modification, please ignore
>> this e-mail.  I do not want to make you trouble with this when you
>> have other things to fix.  If it can be done easily without changing
>> code, however, may I ask you to re-compile with those options?
>> (I have no compiler with me here...)
>> It would be very helpful for me to use my language on vim.
>
>Well, I am sure it can be done.
>Both Axel Kielhorn and Dany St-Amant have released a binary -
>maybe they can also maintain a binary with those features.
>Axel?  Dany?  [I'll CC this to the Vim Mac mailing list.]
>
>Sven
>
>--
>Sven Guckes guckes@...  | vim-mac@...: Maillist for "Vim on MacOS"
>VIMMAC Info on current development: http://www.vim.org/macs.html

Hey All!

I've seen a couple of messages come through on this list so I thought
I'd go ahead and pop out my own personal issue.

What will it require to have working Python support in VIM on the mac?
I'd love for that to work and I'd be happy to help on the Python side,
if it's needed.

Second to that, I was thinking it would be SOoo cool, if we could
*simulate* some command line kinds of tools.  Things like when the user
says ':!ls' that it would go, get the listing for the current directory
and display it.  That would be so helpful.  Now, if it does that some
way that I haven't seen, let me know.  :)

Thanks all!  And I echo the statement from the message today.  vim is
easily the most important application on my powerbook.  I use it
constantly!

--p

--
Patrick Curtain, Husband & Father      ( i also write software )
503 781 6199    patrick@...  http://www.swdev.com/

* Patrick Curtain <patrick@...> [000309 20:47]:
> Second to that, I was thinking it would be SOoo cool,
> if we could *simulate* some command line kinds of tools.
> Things like when the user says ':!ls' that it would go, get the listing
> for the current directory and display it.  That would be so helpful.
> Now, if it does that some way that I haven't seen, let me know.  :)

Yeah, let's emulate all the Unix stuff and
this other command line tool - "emacs".  NOT!

Face it - Macs are no Unix machines.
Hint:  MkLinux, BeOS.  Nuff said.

Sven

Quoting Sven Guckes (guckes@...):
> * Patrick Curtain <patrick@...> [000309 20:47]:
> > Second to that, I was thinking it would be SOoo cool,
> > if we could *simulate* some command line kinds of tools.
> > Things like when the user says ':!ls' that it would go, get the listing
> > for the current directory and display it.  That would be so helpful.
> > Now, if it does that some way that I haven't seen, let me know.  :)
>
> Yeah, let's emulate all the Unix stuff and
> this other command line tool - "emacs".  NOT!
>
> Face it - Macs are no Unix machines.
> Hint:  MkLinux, BeOS.  Nuff said.

What he really wants to do is take the source and hack on it
until the text mode version builds with the MacOS specifics
still intact to build a MPW tool version of vim.  Well, I don't
know whether MPW supports a real terminal emulation similar to
xterm in its editor windows and it'd be a bit strange to put
an editor as an application into an editor's window...

But then since MPW went out of fashion but MPW tools continued
to be useful (things like awk or perl) there is the "ToolServer"
application that can be used as a shell to wrap around MPW tools
w/o having the whole shell and editor around.  It can be used
from CodeWarrior for example to run MPW tools and scripts.  It
would be major cool to but the code into MacOS's port of vim to
interface to the ToolServer application.  This involves implementing
Apple Events for vim.

If done properly, any shell escape could be sent to the ToolServer.
Don't expect the MPW scripting language to be compatible to /bin/sh
though.  It's similar but quite different, making use of many of
the special characters in the Mac's character encoding.  Things
like double-tilde for filename globbing for example.

Gruß,
				 Ripley

--
H. Eckert, 10777 Berlin, Germany, http://www.in-berlin.de/User/nostromo/
ISO 8859-1: Ä=Ae, Ö=Oe, Ü=Ue, ä=ae, ö=oe, ü=ue, ß=sz.
"(Technobabbel)" (Jetrel) - "Müssen wir uns diesen Schwachsinn wirklich
anhören?" (Neelix)

The binary for Vim version 5.6 is now also available for the Macintosh.  It
was compiled and packed by Dany St-Amant.

Directory: ftp://ftp.vim.org/pub/vim/mac

You will need StuffIt Expander 5.x to extract the files.

  SIZE    FILE                 CONTENTS
1688291  vim5.6.full.fat.sit  Vim 5.6, FAT application + runtime files
  298138  vim5.6.68k.sit       Vim 5.6, 68k application only
  624790  vim5.6.fat.sit       Vim 5.6, FAT application only
  333697  vim5.6.ppc.sit       Vim 5.6, PowerPC application only

For more information on the Macintosh version, go to:

		 http://www3.sympatico.ca/dany.stamant/vim/

For discussions about the Macintosh version, use the vim-mac maillist.  Send a
message to vim-help@... to find out how to subscribe.


Another note: ftp.vim.org has been moved to another (faster) machine.
I have not been able to upload files until today.  Sorry for the delay.
It appears to work OK now.  Let me know if you have persistent problems.

--
BLACK KNIGHT: I'm invincible!
ARTHUR:       You're a looney.
                  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

/-/-- Bram Moolenaar --- Bram@... --- http://www.moolenaar.net --\-\
\ \   Vim: http://www.vim.org      ICCF Holland: http://www.vim.org/iccf   / /

Hello All!

Just thought of this after downloading the new 5.6.  And *FIRST OFF*, a
very big THANK YOU to Dany for putting out the latest binary.  Thank
you.

Here's what I'm checking.  The mac vim page mentions python support with
this limitation:

- The first Python command must be :python from vim import *

When I check :version, it says that the 5.6 release was compiled with
'-python' and '-perl', which tells me there isn't python support (or
perl) at all.  Trying to run that command, or any other, fails with the
notice:

Sorry, this command is not implemented.

Most of coding nowadays is being done in python.  Where's the code at in
supporting having python compiled in with the mac version.

Thanks all!
--p

--
Patrick Curtain, Husband & Father      ( i also write software )
503 781 6199    patrick@...  http://www.swdev.com/

* Bram Moolenaar <Bram@...> [000318 21:05]:
> The binary for Vim version 5.6 is now also available for the
> Macintosh.  It was compiled and packed by Dany St-Amant.

http://www.math.fu-berlin.de/~guckes/vim/macs.html is updated.
Mirror www.vim.org should catch up tonight.

Is Dany's version the official version now?  Just wondering.

Sven

Hi all,

I run into a strange problem with the latest Vim.  After editing and
closing a file on Vim, I will sometimes see one or more leftover files
generated by Vim named ".1", ".2", and so forth.  This is more noticable
when the files are located on the Desktop.  Is this a known bug?  Or
could there be something wrong in my _gvimrc file?


--
Eugene Lee
eugene@...

Guten Abend.

After asking this question on four newsgroups, including
comp.editors and comp.lang.python, and a few mailing lists,
is there really no one using Python with Vim on the Mac or
with Win32?

I'm _really_ interested in a Python-enabled Vim binary for
the Macintosh and Win32. _All_ of the links at vim.org which
I tried point to a release compiled w/o the +python option.

Cheers,
Nils
--
nika@... (preferred)
4kassube@...

For what it's worth, I'm using vim on the mac daily, and most of the
coding is for Python.  I'd be enormously interested in having +python as
well.

--p

Nils Kassube wrote:

> Guten Abend.
>
> After asking this question on four newsgroups, including
> comp.editors and comp.lang.python, and a few mailing lists,
> is there really no one using Python with Vim on the Mac or
> with Win32?
>
> I'm _really_ interested in a Python-enabled Vim binary for
> the Macintosh and Win32. _All_ of the links at vim.org which
> I tried point to a release compiled w/o the +python option.
>
> Cheers,
> Nils
> --
> nika@... (preferred)
> 4kassube@...

--
Patrick Curtain, Husband & Father      ( i also write software )
503 781 6199    patrick@...  http://www.swdev.com/

All it takes is a compiler and a web page.  I can supply the
latter, if no one else will, although Axel Kielhorn is the more natural
candidate.  He should be back at his computer soon...

					 --Benji Fisher

Patrick Curtain wrote:
>
> For what it's worth, I'm using vim on the mac daily, and most of the
> coding is for Python.  I'd be enormously interested in having +python as
> well.
>
> --p
>
> Nils Kassube wrote:
>
> > Guten Abend.
> >
> > After asking this question on four newsgroups, including
> > comp.editors and comp.lang.python, and a few mailing lists,
> > is there really no one using Python with Vim on the Mac or
> > with Win32?
> >
> > I'm _really_ interested in a Python-enabled Vim binary for
> > the Macintosh and Win32. _All_ of the links at vim.org which
> > I tried point to a release compiled w/o the +python option.
> >
> > Cheers,
> > Nils

Benji Fisher wrote:

>      All it takes is a compiler and a web page.  I can supply the
> latter, if no one else will, although Axel Kielhorn is the more natural
> candidate.  He should be back at his computer soon...

Finally some progress :-)

I can offer space on two web sites, but I don't have a recent
version of CodeWarrior, otherwise this already would have
happened.

Cheers,
Nils
--
nika@... (preferred)
4kassube@...

Same limitation here.  No codewarrior in-house.

Was there any other issue, related to getting a link to the python
interpreter or anything?  That's where I *thought* the hold-ups resided.

--p

Nils Kassube wrote:

> Benji Fisher wrote:
>
> >      All it takes is a compiler and a web page.  I can supply the
> > latter, if no one else will, although Axel Kielhorn is the more natural
> > candidate.  He should be back at his computer soon...
>
> Finally some progress :-)
>
> I can offer space on two web sites, but I don't have a recent
> version of CodeWarrior, otherwise this already would have
> happened.
>
> Cheers,
> Nils
> --
> nika@... (preferred)
> 4kassube@...

--
Patrick Curtain, Husband & Father      ( i also write software )
503 781 6199    patrick@...  http://www.swdev.com/

Sven Guckes wrote:
>
> * Bram Moolenaar <Bram@...> [000318 21:05]:
> > The binary for Vim version 5.6 is now also available for the
> > Macintosh.  It was compiled and packed by Dany St-Amant.
>
> http://www.math.fu-berlin.de/~guckes/vim/macs.html is updated.
> Mirror www.vim.org should catch up tonight.
>
> Is Dany's version the official version now?  Just wondering.
>
> Sven

      I think that whatever Bram uploads to ftp.vim.org is the "official
version."

      Axel Kielhorn has been away from his computer for a while :( .  He
left before vim 5.6 was released.  At some point, Dany St. Amant posted
a binary for vim-mac 5.6 but never announced it.  I noticed it and
pointed it out to Bram.  He was having trouble uploading to the new
ftp.vim.org; when that got resolved, he posted the binaries and
announced it.

      When I got my copy, it was packaged with a rather non-standard
vimrc file.  Has this survived to the version on ftp.vim.org?

					 --Benji Fisher

On Mon, Mar 27, 2000 at 10:20:57PM -0500, Benji Fisher wrote:

[Vim 5.6 for MacOS]

:     When I got my copy, it was packaged with a rather non-standard
:vimrc file.  Has this survived to the version on ftp.vim.org?

I think so.  I saw Bram's posting and downloaded it, then realized that
it was Dany's January build.  But the non-standard vimrc file is part of
the MacOS distribution.  All the command-key map bindings were commented
out; I uncommented most of them without problems, but there are two that
I've left out because they don't work right with cut-and-paste commands.

Now if only the cursor could blink in MacOS...


--
Eugene Lee
eugene@...

As you all know (or should know), Vim is distributed under the charityware
concept: If you like using Vim, you are requested to help a childrens centre
in Uganda.  In March I visited the project to see how they are doing.  Below
is my report.  Hopefully this inspires you to (continue) support for the
project.  I will certainly do that myself!  You can also read it on the net,
with a couple of pictures:

	 http://www.vim.org/iccf/news.html

Also go there for more information on the project.  If you have any remaining
questions, ask me.


Clinic

There is a small clinic at the project, which has been improved over the last
couple of years. More and more villagers know how to find the place. I was
there on a market day, when over a hundred patients came for medical help. It
was really crowded with patients waiting for treatment. On other days there
are around thirty patients. Overall there are more than two hundred patients
each week. Thus the clinic is providing a very important service to the
community. I have spoken with a few locals, who said they are very happy with
the medical help.

The patients pay a small fee for treatment and medicine. This doesn't cover
the actual cost though. Only through donations can we keep the clinic running,
since the patients are not able to pay a higher fee. The Lisbloem school in
Lisse (The Netherlands) raised a large amount, which has been used to buy a
solar powered fridge. It stores the medicines that have to be kept in a cool
place. The picture shows assistant nurse Boaz with the new fridge. Boaz is one
of the orphans that grew up at the centre while I was working there in 94/95.
He has been able to get an education through the sponsorship program.  I was
happy to see he is now working for the centre.

There is one Ugandan nurse working full time, and a doctor visiting on market
days. Hopefully the quality of the service provided can be improved the coming
year. A small laboratory would be very useful, and more educated staff.


School

The vocational school had just been extended with a tailoring section. I
watched the pupils enjoying their first lessons. It is in a new building,
together with the carpentry section which started last year. The school now
goes from kindergarten, through primary and secondary to the vocational
school. All teachers are now Ugandans and have proper training. There is a
total of about four hundred children, who are enjoying the high quality of
this school.

Besides running the school in Kibaale, attention is given to teachers in
schools of nearby villages. Many of these have had no more training than
primary school themselves. Teacher training is now organised to improve their
knowledge and teaching abilities. The teacher resource centre provides them
with materials.

I really enjoyed watching the children going to school. And they stay until
late in the afternoon to play football and netball. Quite an improvement
compared to the situation in 1993, when I first visited the project. Only
three classes back then, and most teachers were not trained. Now the school is
an example for the area.


Sponsorship

Many children cannot afford to pay their school fees. Therefore sponsors pay
monthly to support them. I have visited eight of the sponsored children at
their homes. The picture shows Nabasagi Morine, one of our youngest children.
She is six years old and goes to the kindergarten class.

Generally, these families are only just able to manage their household. They
have the basic things like a house, some clothes and grow their own food.
Nothing more than that. One family was below the average level though. Their
house is leaking, there are no blankets for the children and no mattresses. I
have asked the manager to give them at least a couple of blankets. Hopefully
we find a way for them to be able to take care of themselves. That is better
than have them depend on our gifts.

There are still a lot of children who are not sponsored. Hopefully we will
find more sponsors this year. The office that takes care of the sponsored
children, called Kibaale Childrens Fund (KCF) is running very well. There are
two Ugandans, who visit the children, managed by a Canadian volunteer. They
make sure the children are able to attend school, visit them at home and take
them to hospital when needed. I accompanied three children to hospital,
together with an assistant nurse. The garden of the hospital looks great, but
the quality of the medical care is low. But there is no other place with a
qualified doctor and a laboratory. We might try to improve our own clinic to
work around this problem.


Conclusion

I can see quite a bit of improvement since my last visit in 1998. Roads have
been fixed, there is more traffic and business.  The Kibaale Childrens Centre
is running very well and mainly with Ugandan staff. The school is operating
very well, and the clinic provides health care to many patients. The coming
time will be focused on maintaining the project and further improving the
quality. I will certainly support that.

- Bram Moolenaar

--
Any sufficiently advanced technology is indistinguishable from magic.
					 Arthur C. Clarke

/-/-- Bram Moolenaar --- Bram@... --- http://www.moolenaar.net --\-\
\-\-- Vim: http://www.vim.org ---- ICCF Holland: http://www.vim.org/iccf --/-/

Dear Vim-Mac developpers,

# I have just joined this mailing list.

It seems that I succeeded in making Japanese version of Vim 5.6 on
Macintosh.  Here I would like to report what I did.

Summary:

- I compiled Vim 5.6 + patch 1-14 + macpatch 01 on MacOS J1-8.1 (not
Japanese Language Kit) on PowerBook G3 using CodeWarrior Professional
(educational) following the instruction described at:

http://www3.sympatico.ca/dany.stamant/vim/version56.mac01.html

- The required changes are available at:

http://www.is.s.u-tokyo.ac.jp/~asai/macvim/macvim.tar.gz, or
http://www.is.s.u-tokyo.ac.jp/~asai/macvim/macvim.lzh, or
the following eight diff files:
http://www.is.s.u-tokyo.ac.jp/~asai/macvim/os_mac.h.diff
http://www.is.s.u-tokyo.ac.jp/~asai/macvim/edit.c.diff
http://www.is.s.u-tokyo.ac.jp/~asai/macvim/feature.h.diff
http://www.is.s.u-tokyo.ac.jp/~asai/macvim/gui_mac.c.diff
http://www.is.s.u-tokyo.ac.jp/~asai/macvim/ex_docmd.c.diff
http://www.is.s.u-tokyo.ac.jp/~asai/macvim/multbyte.c.diff
http://www.is.s.u-tokyo.ac.jp/~asai/macvim/screen.c.diff
http://www.is.s.u-tokyo.ac.jp/~asai/macvim/charset.c.diff

I now describe these changes in detail.

- os_mac.h, edit.c

I supported Macintosh equivalent of +xim.  Namely, when you go into
insert mode, the Input Method is enabled, and when going back to
command mode, it is disabled.

Because I think only is_dbcs people want this function, it might be
better to insert: "if (is_dbcs)" to each change in edit.c, or define a
new compiler directive like MACINTOSH_IM_CONTROL.

- feature.h

I just turned #define MULTI_BYTE on.

- gui_mac.c

I changed gui_mch_draw_sting so that when the character on the cursor
is multibyte, the size of cursor is doubled.  Because this change is
universal to all platforms (I think), the change could be made in
gui.c, too.  I actually did this at first, but since I do not
comprehend all the platforms, I moved the changes into gui_mac.c.  For
your reference, I put my original change in gui.c at:

http://www.is.s.u-tokyo.ac.jp/~asai/macvim/gui.c.diff

- ex_docmd.c

For this patch, I just posted it to vim-multibyte@....  Here is
the description:

When multibyte charcters are used in ex command such as

set guifont=<font name using multibyte>

and if the multibyte contains "|" (0x7c) in its trail byte, this "|"
is mistakenly interpreted as the separation of ex commands.

(The patches up to here are patches that seem to be ok.  The patches
from here on are required for me to use Japanese, but they are not
very clean nor general.  Thus, you should not incorporate them
immediately.)

- multbyte.c

I changed the IsLeadByte so that if MSB is on, it returns true.
CodeWarrior does not seem to support mblen properly.  (Even when we
use Japanese, this is not always true, and better solution should be
persued here.)

- screen.c

I needed a patch for handling non-printable characters when they are a
lead byte.  I hear that Japanese port of Windows GVIM does not need
this change, which means that I might be able to find better solution
to this.

I also made a change on the ruler dispaly.  When the cursor is on
multibyte characters, the ruler shows 2 bytes as its character code.

- charset.c

I needed to change the required length for each character in chartab.
This change is probably wrong, but without this change, character
count for Japanese text goes wrong.  Some thorough solution required.


This is it.  With these patches, I could somehow use Japanese on vim
on macintosh (although it's far from perfect).  I hope this helps the
development of multibyte vim on Macintosh.


Finally, several other things:

- I would like to distribute the binary for this Japanese vim on my
homepage, because there seems to be some people who actually want to
use it.  Would this be possible?

- Do I need any statement on copyright?  I do not need any copyright
on the diff files I made, so please use it in anyway (but without any
warranty).

- I requested several things a few weeks ago (--enable-multibyte,
--enable-fontset, --enable-langmap, --perlinterp, and
--enable-xim-equivalent), but most of them are resolved now.  So now,
I would like to ask one thing: any way to launch application (like
launch(filename) and launch_background(filename)).  Since we have
AppleScript, if we can launch an application, we can do wide variety
of things.  (Currently, I know nothing about inter-process
communication on Macintosh...)

Sincerely,

---
Kenichi Asai

PS.

Axel said:
>I'm currently in Hamamatsu and have only my PowerBook with me. My plan is
>to return to germany at the end of april and then I will work at the Mac
>port again.

Oops!  What a coincidence.  I was in Hamamatsu from March 20-22.  I
might have seen you there...

Dear Mac-Vim developpers,

I received an e-mail asking the exact release of my CodeWarrior
compiler.  It is:

CodeWarrior Professional (Academic) Release 5

Although I bought a Japanese version, I believe I installed only
English version.  (To install Japanese version, I first have to
install English version, and then Japanese version on top of it (which
I did not do)).  This is all the information my package says.  If this
information is not sufficient, please ask me again (together with
how to find it).

I was also advised to read ":help copying" to see about copyright and
binary distribution.  As I understand, it is OK to distribute the
binaries I made as long as the changes are available, so I made them
available in my homepage at:

http://www.is.s.u-tokyo.ac.jp/~asai/macvim-e.html

If you noticed any problem, please let me know.

Sincerely,

---
Kenichi Asai

Kenichi Asai wrote:

> It seems that I succeeded in making Japanese version of Vim 5.6 on
> Macintosh.  Here I would like to report what I did.

That is very nice.  I looked through your changes and it they appear to be
small.  However, a few changes look like they might cause problems when used
in another environment (not Macintosh or not multi-byte).

I suggest distributing this as a patch on top of the available Vim version for
a while.  Perhaps you can improve it further if remarks are made.  I can
include the changes in the main Vim distribution after some confidence is
build up.

Your detailed description of the changes is very good!  Please update it when
making further changes.

For people in vim-multibyte who want to see the original message, go to the
vim-mac archive: http://www.egroups.com/group/vim-mac

> - I would like to distribute the binary for this Japanese vim on my
> homepage, because there seems to be some people who actually want to
> use it.  Would this be possible?

Vim can be distributed freely.  That also applies to modified versions.

> - Do I need any statement on copyright?  I do not need any copyright
> on the diff files I made, so please use it in anyway (but without any
> warranty).

I would not worry about copyright.  If you would not want others to use this,
you would not have send it to this list.

--
Living on Earth includes an annual free trip around the Sun.

/-/-- Bram Moolenaar --- Bram@... --- http://www.moolenaar.net --\-\
\-\-- Vim: http://www.vim.org ---- ICCF Holland: http://www.vim.org/iccf --/-/

Dear Vim-Mac developpers,

Summary:

- I found that "set isprint=@,~-255" makes some changes unnecessary
that I made before.
- I had a small problem with patch 5.6.061 when compiling with CodeWarrior.
- I updated my release of Japanese Vim 5.6.  It is available at:
http://www.is.s.u-tokyo.ac.jp/~asai/macvim-e.html

In my previous e-mails, I reported that changes on screen.c and
chartab.c were necessary to use Japanese.  It turned out that by
setting

set isprint=@,~-255

those changes are unnecessary.  (On Windows, the above setting is the
default.  On Macintosh, it isn't.  It might be a good idea to set it
default on Macintosh, too, but I do not understand its consequence
very much.)  Here goes the detailed description on my current patches.

- os_mac.h.diff, edit.c.diff, feature.h.diff

Same as before.

- gui_mac.c.diff

Almost the same as before.  I changed it a little bit so that I can
manage the case where the first byte is LeadByte and the second byte
is null.

- multbyte.c.diff

Same as before.  (Still need further consideration.)

- screen.c

The changes are only for displaying a ruler:

>I also made a change on the ruler dispaly.  When the cursor is on
>multibyte characters, the ruler shows 2 bytes as its character code.

- term.c

CodeWarrior complians that it cannot cast
(char *) p->bt_string
into
(char_u *).

- ex_docmd.c

This is incorporated as 5.6.052.

- chartab.c

No changes required any more.  My previous patch for chartab.c was removed.

Sincerely,

---
Kenichi Asai

Oleg Raisky has updated his Vim reference guide to Vim version 5.6.  This is
the best Vim reference booklet I know.  It is about 50 pages and contains a
short note for almost every Vim command and feature.

More info can be found on Oleg's Vim page:
	 http://physlab.sci.ccny.cuny.edu/~orycc/vim-main.html

You can download the reference guide from ftp://ftp.vim.org/pub/vim/doc/.
It comes in four files, each containing the same guide in a different format:

200794  vimguide-0.7-bkl.a4.tar.bz2    booklet, A4 format
200673  vimguide-0.7-bkl.let.tar.bz2   booklet, letter format
176449  vimguide-0.7-pln.a4.tar.bz2    plain, A4 format
175999  vimguide-0.7-pln.let.tar.bz2   plain, letter format

You will need the "bzip2" or "bunzip2" program to uncompress the files.

Thanks to Oleg for creating this!

--
Microsoft is to software what McDonalds is to gourmet cooking

/-/-- Bram Moolenaar --- Bram@... --- http://www.moolenaar.net --\-\
\-\-- Vim: http://www.vim.org ---- ICCF Holland: http://www.vim.org/iccf --/-/

At 17:30 Uhr +0900 2000-04-11, Kenichi Asai wrote:
>Dear Vim-Mac developpers,

>In my previous e-mails, I reported that changes on screen.c and
>chartab.c were necessary to use Japanese.  It turned out that by
>setting
>
>set isprint=@,~-255
>
>those changes are unnecessary.  (On Windows, the above setting is the
>default.  On Macintosh, it isn't.)

This is a bug, 128 - 160 are printable, will be fixed in the next
non-japanese release that I hope to prepare over the easter break.

>This is incorporated as 5.6.052.

Axel, 5 patches behind

--
Adults get far more pleasure from adultery
than children do from infancy

From: Jean-Pierre Giacalone <j-giacalone@...>
To: guckes@...
Subject: VIM 5.6 for MAC (OS 8.6) crashes with Dislock
Date: Mon, 08 May 2000 22:05:37 +0200
Message-ID: <39171E08.179659C0@...>
X-Mailer: Mozilla 4.5 [fr] (Macintosh; I; PPC)

I installed Dislock from PowerON Software (Disk protection and
password locking software) on my PowerMAC G3 on MacOS 8.6.

The last version of VIM, VIM5.6 for PPC is now crashing
as soon as I type in characters or crashes when loading.
Do you know where this is coming from?
Is there a patch that corrects this?

Thanks for your help.

Best regards,
Jean-Pierre.

--
Jean-Pierre Giacalone
Wireless Communication Business Unit - Texas Instruments
email: j-giacalone@...
tel: +33-4-93-22-21-17
GSM: +33-4-80-38-81-76

I had some feedback from Jean-Pierre and
it seems that the problem has been solved:

I took a "wild guess" at the use of swapfiles -
and Jean-Pierre said that "unset swapfiles"
solves the problem with "Vim-5.6 vs Dislock".

However, dropping swap files just to make
Vim usuable on a Macintosh seems bad.
Is there a way to solve this problem?

Bram - please add a note on "Dislock" as
an example for a program which makes Vim
unusable when you use swapfiles.  Thanks!
(probably with ":help mac-vimrc").

Sven

> From: Jean-Pierre Giacalone <j-giacalone@...>
> Subject: VIM 5.6 for MAC (OS 8.6) crashes with Dislock
> Date: Mon, 08 May 2000 22:05:37 +0200
> Message-ID: <39171E08.179659C0@...>
> X-Mailer: Mozilla 4.5 [fr] (Macintosh; I; PPC)
>
> I installed Dislock from PowerON Software (Disk protection and
> password locking software) on my PowerMAC G3 on MacOS 8.6.
>
> The last version of VIM, VIM5.6 for PPC is now crashing
> as soon as I type in characters or crashes when loading.
> Do you know where this is coming from?
> Is there a patch that corrects this?

* Axel Kielhorn <Axel.noSpam@...> [000416 15:23]:
> >In my previous e-mails, I reported that changes on screen.c and
> >chartab.c were necessary to use Japanese.  It turned out that by
> >setting "set isprint=@,~-255" those changes are unnecessary.  (On
> >Windows, the above setting is the default.  On Macintosh, it isn't.)
> This is a bug, 128 - 160 are printable, will be fixed in the next
> non-japanese release that I hope to prepare over the easter break.

Well, was it possible for you to produce a new version?

Also, could we please decide on a
MacVim to be *the* official one?

I am getting sick of telling people this stuff:

   MacVim is available from every ftp mirror.
   However, there are three sites with updates:
   Obe by Dany St-Amant, obe by Axel Kielhorn,
   and one by Kenichi Asai ("MacVim Japanese").
   Please let me know which version you are using.

For me it means more work altogether:
Maintain more info, keep more links,
keep contact with ebern more people,
and confuse the hell out of the users.

I'd *really* appreciate if you guys would get
your stuff together and decide on *one* person
to maintain *the* MacVim on ftp.vim.org.

I know this won't solve the requests for
"please make me a binary with +perl"
but then again it's Apple's problem that
there they don't supply a free compiler..

Sven

Pardon the dumb question, but is there a single list I could
look at to show the differences between VIM and VI? Or are my
own differences likely due to something I've inadvertently set?
As an example, I'm used to marking a line and then deleting to
that mark, as in "ma"  then move to another spot, and "d'a",
which doesn't work in my VIM. Any other differences?

Mark


Sven Guckes wrote:

> * Axel Kielhorn <Axel.noSpam@...> [000416 15:23]:
> > >In my previous e-mails, I reported that changes on screen.c and
> > >chartab.c were necessary to use Japanese.  It turned out that by
> > >setting "set isprint=@,~-255" those changes are unnecessary.  (On
> > >Windows, the above setting is the default.  On Macintosh, it isn't.)
> > This is a bug, 128 - 160 are printable, will be fixed in the next
> > non-japanese release that I hope to prepare over the easter break.
>
> Well, was it possible for you to produce a new version?
>
> Also, could we please decide on a
> MacVim to be *the* official one?
>
> I am getting sick of telling people this stuff:
>
>   MacVim is available from every ftp mirror.
>   However, there are three sites with updates:
>   Obe by Dany St-Amant, obe by Axel Kielhorn,
>   and one by Kenichi Asai ("MacVim Japanese").
>   Please let me know which version you are using.
>
> For me it means more work altogether:
> Maintain more info, keep more links,
> keep contact with ebern more people,
> and confuse the hell out of the users.
>
> I'd *really* appreciate if you guys would get
> your stuff together and decide on *one* person
> to maintain *the* MacVim on ftp.vim.org.
>
> I know this won't solve the requests for
> "please make me a binary with +perl"
> but then again it's Apple's problem that
> there they don't supply a free compiler..
>
> Sven

I think this is more appropriate for the vim-mac mailing list than
the plain vim one, so I am replying here.

      I had similar problems, except that (1) I do not have MacsBug
(whatever that is) (2) nothing serious seemed to happen when vim died
(3) I may have misdiagnosed the problem.  The behavior seemed to depend
on the name of the folder containing VimPPC but maybe that only matters
because it affects the setting of $VIM and therefore what files get
sourced.  I also find that both versions crash when I do

:let $VIM=getcwd()

      Conclusion:  we are not yet "ready for prime time"!

					 --Benji Fisher

Eugene Lee wrote:
>
> I have a serious problem with this MacVim 5.6.70.  When I started it up,
> it would always die and drop into MacsBug.  It's very difficult to exit
> the app from there.  Most of the time, it wouldn't and I'd have to
> reboot (usually via MacsBug, but sometimes ctrl-cmd-pwr) .  If it does
> exit, it does so with a Type 2 error.  I can provide MacsBug logs if
> that can help trace the problem.
>
> I've isolated it to a single line that has worked flawlessly in previous
> versions:
>
>         let $Desktop = substitute($VIM,":.*",":Desktop Folder","")
>
> If I start up with a vimrc file containing only this line, MacVim bombs.
> If I start up MacVim without the offending line, then type this line at
> the command prompt, it works fine.
>
> This on MacOS 8.6.  Increasing MacVim's memory partition doesn't help
> (and I have mine set to 10 MB).  I've also tried running it with only
> MacOS 8.6 base extensions on, no go.
>
> Also, there seems to be a problem with syntax highlighting, because
> files that have an appropriate syntax file take 3-4 times longer to
> display than the previous patchlevel 68 version.
>
> On Sat, May 06, 2000 at 10:15:19PM +0200, Axel Kielhorn wrote:
> :
> :This message is send to all known MacVim users, if you don't want to get
> :this message, please send me a mail.
>
> Please add me to your list of known MacVim users.  Thanks!
>
> :I finally updated my environment and I'm now able to compile Vim with all
> :of Dany's patches included.
> :
> :I have updated the Vim core to patch 70, fixing a bug with with the "go"
> :command when editing DOS files.
> :
> :There is one incompatible change:
> :This version no longer supports rc-files starting with a "." or "_". This
> :may remove some crashes reported by Wes Palmer. Please use "vimrc" "gvimrc"
> :and "exrc" on the Mac.
> :
> :Please test this version because this is the version I want Bram to put on
> :the official vim site. Should I provide a fat version as well, maybe in a
> :separate archive?
> :
> :As always you will find the newest version on:
> :
> :http://www.tu-bs.de/~i0080108/macvim.html
> :
> :Axel
> :
> :--
> :Adults get far more pleasure from adultery
> :than children do from infancy
> :
>
> --
> Eugene Lee
> eugene@...

Sven Guckes wrote:

> I had some feedback from Jean-Pierre and
> it seems that the problem has been solved:
>
> I took a "wild guess" at the use of swapfiles -
> and Jean-Pierre said that "unset swapfiles"
> solves the problem with "Vim-5.6 vs Dislock".
>
> However, dropping swap files just to make
> Vim usuable on a Macintosh seems bad.
> Is there a way to solve this problem?
>
> Bram - please add a note on "Dislock" as
> an example for a program which makes Vim
> unusable when you use swapfiles.  Thanks!
> (probably with ":help mac-vimrc").

Hmm, I rather would see the problem further investigated, and solved!
Very strange that using a swap file doesn't work when another program is
running.  Why can this be?

--
ARTHUR: (as the MAN next to him is squashed by a sheep) Knights!  Run away!
    Midst echoing shouts of "run away" the KNIGHTS retreat to cover with the odd
    cow or goose hitting them still.  The KNIGHTS crouch down under cover.
                  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

/-/-- Bram Moolenaar --- Bram@... --- http://www.moolenaar.net --\-\
\-\-- Vim: http://www.vim.org ---- ICCF Holland: http://www.vim.org/iccf --/-/