At 22:59 Uhr +0200 2003-04-28, Bram Moolenaar wrote:
>You better fix the Mac version soon, because I'm planning to get a
>Powerbook.  Wouldn't be very happy if Vim doesn't run properly on it!


But you will probably use MacOS X and not OS 9.
On OS X you have no problems with strange line endings and even
stranger ways to write a path.

Axel

I will be attending the O'Reilly Open Source Convention.  This is a big
conference with up to 15 parallel tracks.  The convention is taking
place in Portland, OR, USA on July 7-11.  Many of the top guys in the
world of open source software will be there, including Larry Wall and
Guido van Rossum.
	 http://conferences.oreillynet.com/os2003/

The main reason for me to go there is that I'm doing a presentation on
the A-A-P project:
	 http://conferences.oreillynet.com/cs/os2003/view/e_sess/4026

There will also be a BOF session on A-A-P, just after the one on SCons.
I good occasion to talk about modern software build tools.
	 http://conferences.oreillynet.com/cs/os2003/view/e_sess/4348

I'm sure there will also be plenty of time to talk about Vim.  Looking
forward to meet Vim users and developers there!


PS:
For people in the Netherlands: You can also meet me and Guido van Rossum
at the NLUUG conference "Web Applications":
	 http://www.nluug.nl/events/vj03/

--
hundred-and-one symptoms of being an internet addict:
220. Your wife asks for sex and you tell her where to find you on IRC.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html ///

Hi,

When I am working with several files, I prefer to run several Vim
applications instead of working with Vim's windows.

When I start Vim from the command like, I have it. Each Vim runs as a
separate process and I have what I would like to have.

How to reach the same behavior from Finder? Well, as far as I
understand, this is more an Apple-related question, but it may be
someone on this list already solved it.

Best wishes,

Evgenii Rudnyi
--
Institut fuer Mikrosystemtechnik IMTEK
Mikrosystemsimulation
Universitaet  Freiburg
Georges-Koehler-Allee, Geb. 103
D-79110 Freiburg
Germany
Tel. (+49 761) 203 7383
Fax  (+49 761) 203 7382
http://www.imtek.de/simulation/

On Wed, May 14, 2003 at 01:10:29PM +0200, Evgenii Rudnyi wrote:
} When I am working with several files, I prefer to run several Vim
} applications instead of working with Vim's windows.
}
} When I start Vim from the command like, I have it. Each Vim runs as a
} separate process and I have what I would like to have.
}
} How to reach the same behavior from Finder? Well, as far as I
} understand, this is more an Apple-related question, but it may be
} someone on this list already solved it.

The simplest and easiest way is to create a shell script with the .sh
extension that calls vim as you would on the commandline. Make sure it is
executable, and you should be able to double-click it.

} Best wishes,
} Evgenii Rudnyi
--Greg

> You might also want to put it in your $PATH so you can type "gvim"
> from the terminal to fire off a new gvim / vim.
>
> Different question : when I run vim in a terminal with a "big" font,
> it displays with the same font - when I run gvim (note gvim, not vim)
> in its own window, the window size and font size are tiny... I'd like
> to increase them but I don't know how - does anyone know?
>
> cheers
>
> .s
>
>
> On Wednesday, May 14, 2003, at 12:26  pm, Gregory Seidman wrote:
>
>> On Wed, May 14, 2003 at 01:10:29PM +0200, Evgenii Rudnyi wrote:
>> } When I am working with several files, I prefer to run several Vim
>> } applications instead of working with Vim's windows.
>> }
>> } When I start Vim from the command like, I have it. Each Vim runs as
>> a
>> } separate process and I have what I would like to have.
>> }
>> } How to reach the same behavior from Finder? Well, as far as I
>> } understand, this is more an Apple-related question, but it may be
>> } someone on this list already solved it.
>>
>> The simplest and easiest way is to create a shell script with the .sh
>> extension that calls vim as you would on the commandline. Make sure
>> it is
>> executable, and you should be able to double-click it.
>>
>> } Best wishes,
>> } Evgenii Rudnyi
>> --Greg
>>
>

On Wed, May 14, 2003 at 12:43:37PM +0100, simon wrote:
[...]
} Different question : when I run vim in a terminal with a "big" font,
} it displays with the same font - when I run gvim (note gvim, not vim)
} in its own window, the window size and font size are tiny... I'd like
} to increase them but I don't know how - does anyone know?

This is a FAQ. Indeed, I seem to be responsible for having answered it. See
the third item at http://macvim.swdev.org/OSX/#FAQ

} cheers
} .s
--Greg

Thank you for replies. However, I was not clear enough in my original
message.

  >The simplest and easiest way is to create a shell script with the .sh
  >extension that calls vim as you would on the commandline. Make sure it
is
  >executable, and you should be able to double-click it.

This works. Well, by default the extension should be .command. In order
to make .sh working, one has to configure Finder in Open With.

The question is how to open Vim as a separate process by
double-clicking a document in Finder? You cannot place file.command to
the program part of the Dock. Finder considers it as a document for
Terminal and not as a program.

I was able to achieve it in Midnight Commander by configuring EDITOR
variable, but in addition it would be good to have it also in Finder.
Apple's Terminal does not support mouse. One can run Midnight Commander
in xterm but this is already too messy.

Best wishes,

Evgenii Rudnyi
--
Institut fuer Mikrosystemtechnik IMTEK
Mikrosystemsimulation
Universitaet  Freiburg
Georges-Koehler-Allee, Geb. 103
D-79110 Freiburg
Germany
Tel. (+49 761) 203 7383
Fax  (+49 761) 203 7382
http://www.imtek.de/simulation/

Announcing:  Vim (Vi IMproved) version 6.2e BETA
     Author:  Bram Moolenaar et al.


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

This is a test version of Vim.  Since Vim 6.1 many reported problems
have been fixed.  Also included are new and updated syntax files,
translated menus and messages.

Main new features:
- Support for GTK 2. (Daniel Elstner)
- Support for editing Arabic text. (Nadim Shaikli & Isam Bayazidi)
- ":try" command and friends. (Servatius Brandt)
- Support for the neXtaw GUI toolkit (mostly like Athena). (Alexey Froloff)
- Cscope support for Win32. (Sergey Khorev)
- Support for PostScript printing in various 8-bit encodings. (Mike Williams)

The coming weeks beta testing will take place.  Please report any
problems that you discover!

Once you have installed 6.2e you can find details about the changes
since Vim 6.1 with ":help version-6.2".  There is a very 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://www.vim.org.  This is also a great
place to find Vim tips and scripts!


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

All files can be found below this directory:

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

An overview of the files:

UNIX:
unix/vim-6.2e.tar.bz2  sources + runtime files, bzip2 compressed
   unix/vim-6.2e-rt1.tar.gz   runtime files part 1
   unix/vim-6.2e-rt2.tar.gz   runtime files part 2
   unix/vim-6.2e-src1.tar.gz   sources part 1
   unix/vim-6.2e-src2.tar.gz   sources part 2

VARIOUS:
extra/vim-6.2e-extra.tar.gz extra files
extra/vim-6.2e-lang.tar.gz multi-language files
doc/vim62ehtml.zip  help files converted to HTML

MS-WINDOWS:
pc/gvim62e.exe 	 self-installing, includes runtime files

pc/vim62ert.zip 	 runtime files (for following binaries)
pc/vim62elang.zip  extra files for translated messages and menus

pc/gvim62e.zip 	 GUI binary for Windows 95/98/NT/2000
pc/gvim62eole.zip  GUI binary with OLE support
pc/vim62ed16.zip  16 bits real mode - works on any system
pc/vim62ed32.zip  32 bits protected mode - needs 386 and DPMI
pc/vim62ew32.zip  console version for Windows NT/2000/XP

pc/vim62esrc.zip  sources for PC (with CR-LF)

AMIGA:
amiga/vim62ert.tgz  runtime files (always needed)
amiga/vim62ebin.tgz  binaries
amiga/vim62esrc.tgz  sources packed for Amiga


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/maillist.php.  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!

--
BLACK KNIGHT:  Come on you pansy!
     [hah] [parry thrust]
     [ARTHUR chops the BLACK KNIGHT's right arm off]
ARTHUR:        Victory is mine!  [kneeling]
                We thank thee Lord, that in thy merc-
     [Black Knight kicks Arthur in the head while he is praying]
                                   The Quest for the Holy Grail (Monty Python)

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html ///

On Sunday, May 18, 2003, Evgenii Rudnyi wrote:

>> The simplest and easiest way is to create a shell script with the .sh
>> extension that calls vim as you would on the commandline. Make sure
>> it is executable, and you should be able to double-click it.
>
> The question is how to open Vim as a separate process by
> double-clicking
> a document in Finder?

This can be done with DropScript
<http://www.advogato.org/proj/DropScript/>
and the aforementioned shell script, though it would be nicer, of
course,
if similar functionality could be incorporated into Vim.app itself.

I can post or email a DropGVim.app (~25K) if you'd rather not tackle
this yourself.

Peter

Hi,

    Could someone test the following patch on MacOS 9?
    The patch is over 6.2d

    Patch purpose:

    make :winpos and :winpos x y use the same coordinate set (the frame
of the window)


Dany

The system didn't like my attachement. Back to the old cut'n'paste.

Le lundi, 19 mai 2003, à 16:42 Canada/Eastern,
dany.stamant@... a écrit :

> Hi,
>
>   Could someone test the following patch on MacOS 9?
>   The patch is over 6.2d
>
>   Patch purpose:
>
>   make :winpos and :winpos x y use the same coordinate set (the frame
> of the window)
>
>
> Dany

*** gui_mac.c.orig      Mon May 19 16:25:39 2003
--- gui_mac.c   Mon May 19 16:02:56 2003
***************
*** 2874,2879 ****
--- 2874,2900 ----
        /* TODO:  Should make sure the window is move within range
         *              e.g.: y > ~16 [Menu bar], x > 0, x < screen width
         */
+
+     /* Since MoveWindow use the "kWindowContentRgn" location,
+      * and that Vim wants to refer to the "kWindowStructureRgn"
+      * location, we need to tune the value
+      */
+ #ifdef USE_CARBONIZED
+     Rect      cont_bounds;
+     Rect      struct_bounds;
+     OSStatus  status_cont;
+     OSStatus  status_struct;
+
+     /* Carbon >= 1.0.2, MacOS >= 8.5 */
+     status_cont = GetWindowBounds (gui.VimWindow, kWindowContentRgn,
&cont_bounds);
+     status_struct = GetWindowBounds (gui.VimWindow,
kWindowStructureRgn, &struct_bounds);
+
+     if ((status_cont == noErr) && (status_struct == noErr))
+     {
+       x += (cont_bounds.left - struct_bounds.left);
+       y += (cont_bounds.top - struct_bounds.top);
+     }
+ #endif
        MoveWindow(gui.VimWindow, x, y, TRUE);
    }

Finally you can join your favorite drink with your favorite editor:
It's the Vim reference mug!

Besides the Vim logo there are a dozens of Vim commands explained. We
tried adding all the commands, but realized it's difficult to drink
coffee from a bath tub...

You can order the Vim mug with rootshop.de
(http://rootshop.de/produkte/tassen/220132/).
Note: the site is in German and orders can be made from Europe only.

As a nice touch half a euro of each mug goes to ICCF Holland
(http://iccf-holland.org/).

--
"Software is like sex... it's better when it's free."
		 -- Linus Torvalds, initiator of the free Linux OS
Makes me wonder what FSF stands for...?

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html ///

At 16:54 Uhr -0400 2003-05-19, dany.stamant@... wrote:
>The system didn't like my attachement. Back to the old cut'n'paste.
>
>Le lundi, 19 mai 2003, à 16:42 Canada/Eastern,
>dany.stamant@... a écrit :
>
>>Hi,
>>
>>   Could someone test the following patch on MacOS 9?
>>   The patch is over 6.2d

Sorry, I can't generate Carbon code, my codewarrior is too old.
But if someone can provide a carbon binary, I can test it on 8.6

Axel

Axel Kielhorn wrote:
> At 16:54 Uhr -0400 2003-05-19, dany.stamant@... wrote:
>
>> The system didn't like my attachement. Back to the old cut'n'paste.
>>
>> Le lundi, 19 mai 2003, à 16:42 Canada/Eastern,
>> dany.stamant@... a écrit :
>>
>>> Hi,
>>>
>>>   Could someone test the following patch on MacOS 9?
>>>   The patch is over 6.2d
>>
>
> Sorry, I can't generate Carbon code, my codewarrior is too old.
> But if someone can provide a carbon binary, I can test it on 8.6
>
> Axel

       Does that mean you can use a Carbon binary compiled on OS X?

					 --Benji Fisher

Announcing:  Vim (Vi IMproved) version 6.2f BETA
     Author:  Bram Moolenaar et al.


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

This is a test version of Vim.  Since Vim 6.1 many reported problems
have been fixed.  Also included are new and updated syntax files,
translated menus and messages.

Main new features:
- Support for GTK 2. (Daniel Elstner)
- Support for editing Arabic text. (Nadim Shaikli & Isam Bayazidi)
- ":try" command and friends. (Servatius Brandt)
- Support for the neXtaw GUI toolkit (mostly like Athena). (Alexey Froloff)
- Cscope support for Win32. (Sergey Khorev)
- Support for PostScript printing in various 8-bit encodings. (Mike Williams)

The coming week beta testing will continue.  Please report any problem
that you discover!

Once you have installed 6.2f you can find details about the changes
since Vim 6.1 with ":help version-6.2".  There is a very 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://www.vim.org.  This is also a great
place to find Vim tips and scripts!


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

All files can be found below this directory:

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

An overview of the files:

UNIX:
unix/vim-6.2f.tar.bz2  sources + runtime files, bzip2 compressed
   unix/vim-6.2f-rt1.tar.gz   runtime files part 1
   unix/vim-6.2f-rt2.tar.gz   runtime files part 2
   unix/vim-6.2f-src1.tar.gz   sources part 1
   unix/vim-6.2f-src2.tar.gz   sources part 2

VARIOUS:
extra/vim-6.2f-extra.tar.gz extra files
extra/vim-6.2f-lang.tar.gz multi-language files
doc/vim62fhtml.zip  help files converted to HTML

MS-WINDOWS:
pc/gvim62f.exe 	 self-installing, includes runtime files

pc/vim62frt.zip 	 runtime files (for following binaries)
pc/vim62flang.zip  extra files for translated messages and menus

pc/gvim62f.zip 	 GUI binary for Windows 95/98/NT/2000
pc/gvim62fole.zip  GUI binary with OLE support
pc/vim62fd16.zip  16 bits real mode - works on any system
pc/vim62fd32.zip  32 bits protected mode - needs 386 and DPMI
pc/vim62fw32.zip  console version for Windows NT/2000/XP

pc/vim62fsrc.zip  sources for PC (with CR-LF)

AMIGA:
amiga/vim62frt.tgz  runtime files (always needed)
amiga/vim62fsrc.tgz  sources packed for Amiga


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/maillist.php.  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!

--
THEOREM: VI is perfect.
PROOF: VI in roman numerals is 6.  The natural numbers < 6 which divide 6 are
1, 2, and 3. 1+2+3 = 6.  So 6 is a perfect number.  Therefore, VI is perfect.
QED
						     -- Arthur Tateishi

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html ///

Vim-dev and Vim-mac:

       I apologize for the cross-posting, but I think this is the best hope for
solving this before the release of vim 6.2.  I tried to compile vim 6.2f on Mac
OS X and I got the following linking errors below.  Judging from the names of
the undefined symbols, I guess this has to do with the try/catch mechanism.  Any
suggestions?  If I am right, how do I compile without try/catch?

					 --Benji Fisher

cc -lncurses  -framework Carbon ObjX_UNIX/buffer.o ObjX_UNIX/charset.o
ObjX_UNIX/diff.o ObjX_UNIX/digraph.o ObjX_UNIX/edit.o ObjX_UNIX/eval.o
ObjX_UNIX/ex_cmds.o ObjX_UNIX/ex_cmds2.o ObjX_UNIX/ex_docmd.o
ObjX_UNIX/ex_getln.o ObjX_UNIX/fileio.o ObjX_UNIX/fold.o ObjX_UNIX/getchar.o
ObjX_UNIX/gui_mac.o ObjX_UNIX/gui.o ObjX_UNIX/main.o ObjX_UNIX/mark.o
ObjX_UNIX/memfile.o ObjX_UNIX/memline.o ObjX_UNIX/menu.o ObjX_UNIX/message.o
ObjX_UNIX/misc1.o ObjX_UNIX/misc2.o ObjX_UNIX/move.o ObjX_UNIX/mbyte.o
ObjX_UNIX/normal.o ObjX_UNIX/ops.o ObjX_UNIX/option.o ObjX_UNIX/os_macosx.o
ObjX_UNIX/pathdef.o ObjX_UNIX/pty.o ObjX_UNIX/quickfix.o ObjX_UNIX/regexp.o
ObjX_UNIX/screen.o ObjX_UNIX/search.o ObjX_UNIX/syntax.o ObjX_UNIX/tag.o
ObjX_UNIX/term.o ObjX_UNIX/ui.o ObjX_UNIX/undo.o ObjX_UNIX/version.o
ObjX_UNIX/window.o -o Vim.x_unix
ld: Undefined symbols:
_aborting
_aborted_in_try
_cleanup_conditionals
_report_make_pending
_should_abort
_discard_current_exception
_do_errthrow
_do_intthrow
_do_throw
_ex_break
_ex_catch
_ex_continue
_ex_else
_ex_endfunction
_ex_endif
_ex_endtry
_ex_endwhile
_ex_finally
_ex_if
_ex_throw
_ex_try
_ex_while
_has_while_cmd
_cause_errthrow
make: *** [Vim.x_unix] Error 1

Benji,

It appears that you just have ex_eval.c missing from the
OS X makefile.

Vince

> -----Original Message-----
> From: Benji Fisher [SMTP:benji@...]
> Sent: Tuesday, May 27, 2003 4:30 PM
> To: vim-dev@...; vim-mac@...
> Subject: link errors:  vim 6.2f on Mac OS X
>
> Vim-dev and Vim-mac:
>
>       I apologize for the cross-posting, but I think this is the best hope
> for
> solving this before the release of vim 6.2.  I tried to compile vim 6.2f
> on Mac
> OS X and I got the following linking errors below.  Judging from the names
> of
> the undefined symbols, I guess this has to do with the try/catch
> mechanism.  Any
> suggestions?  If I am right, how do I compile without try/catch?
>
> 				 --Benji Fisher
>
> cc -lncurses  -framework Carbon ObjX_UNIX/buffer.o ObjX_UNIX/charset.o
> ObjX_UNIX/diff.o ObjX_UNIX/digraph.o ObjX_UNIX/edit.o ObjX_UNIX/eval.o
> ObjX_UNIX/ex_cmds.o ObjX_UNIX/ex_cmds2.o ObjX_UNIX/ex_docmd.o
> ObjX_UNIX/ex_getln.o ObjX_UNIX/fileio.o ObjX_UNIX/fold.o
> ObjX_UNIX/getchar.o
> ObjX_UNIX/gui_mac.o ObjX_UNIX/gui.o ObjX_UNIX/main.o ObjX_UNIX/mark.o
> ObjX_UNIX/memfile.o ObjX_UNIX/memline.o ObjX_UNIX/menu.o
> ObjX_UNIX/message.o
> ObjX_UNIX/misc1.o ObjX_UNIX/misc2.o ObjX_UNIX/move.o ObjX_UNIX/mbyte.o
> ObjX_UNIX/normal.o ObjX_UNIX/ops.o ObjX_UNIX/option.o
> ObjX_UNIX/os_macosx.o
> ObjX_UNIX/pathdef.o ObjX_UNIX/pty.o ObjX_UNIX/quickfix.o
> ObjX_UNIX/regexp.o
> ObjX_UNIX/screen.o ObjX_UNIX/search.o ObjX_UNIX/syntax.o ObjX_UNIX/tag.o
> ObjX_UNIX/term.o ObjX_UNIX/ui.o ObjX_UNIX/undo.o ObjX_UNIX/version.o
> ObjX_UNIX/window.o -o Vim.x_unix
>
Legal Disclaimer: Any views expressed by the sender of this message are
not necessarily those of Application Solutions Ltd. Information in this
e-mail may be confidential and is for the use of the intended recipient
only, no mistake in transmission is intended to waive or compromise such
privilege. Please advise the sender if you receive this e-mail by mistake.

Try attached file.  I have placed same one at:
   http://www.kaoriya.net/testdir/osx_buildset-6.2f.006.tar.bz2

Extract all files and set those in src directory and do:
$ make -f Make_osx.mak

I propose these files to be included in the release package, but is it
too late?
----
MURAOKA Taro  <koron@...>

MURAOKA Taro wrote:
> Try attached file.  I have placed same one at:
>   http://www.kaoriya.net/testdir/osx_buildset-6.2f.006.tar.bz2
>
> Extract all files and set those in src directory and do:
> $ make -f Make_osx.mak
>
> I propose these files to be included in the release package, but is it
> too late?
> ----
> MURAOKA Taro  <koron@...>

       Thanks to Muraoka Taro and Vince Negri.  I am trying this solution first.
   I now get the errors below.  If I read them correctly, the typedef for iconv_t
has somehow been missed.

       If it makes a difference, I think I have upgraded my OS to 10.2.6 but am
still using the Developer Tools from my original Jaguar CD (unless that also got
updated by Software Update).

					 --Benji Fisher


os_macosx.c: At top level:
os_macosx.c:273: parse error before "iconv_open"
os_macosx.c:274: warning: return type defaults to `int'
os_macosx.c: In function `iconv_open':
os_macosx.c:276: `iconv_t' undeclared (first use in this function)
os_macosx.c:276: (Each undeclared identifier is reported only once
os_macosx.c:276: for each function it appears in.)
os_macosx.c:276: parse error before "cd"
os_macosx.c:286: `cd' undeclared (first use in this function)
os_macosx.c:286: parse error before "alloc"
os_macosx.c:324: warning: implicit declaration of function `iconv_close'
os_macosx.c: At top level:
os_macosx.c:335: parse error before "cd"
os_macosx.c: In function `null_conv':
os_macosx.c:338: `inbuf' undeclared (first use in this function)
os_macosx.c:339: `outbuf' undeclared (first use in this function)
os_macosx.c:343: `inbytesleft' undeclared (first use in this function)
os_macosx.c:344: `outbytesleft' undeclared (first use in this function)
os_macosx.c: At top level:
os_macosx.c:372: parse error before "cd"
os_macosx.c: In function `iconv':
os_macosx.c:381: `cd' undeclared (first use in this function)
os_macosx.c:387: `inbuf' undeclared (first use in this function)
os_macosx.c:387: `inbytesleft' undeclared (first use in this function)
os_macosx.c:387: `outbuf' undeclared (first use in this function)
os_macosx.c:387: `outbytesleft' undeclared (first use in this function)
os_macosx.c:497: `EILSEQ' undeclared (first use in this function)
os_macosx.c: At top level:
os_macosx.c:512: parse error before "cd"
os_macosx.c: In function `iconv_close':
os_macosx.c:514: `cd' undeclared (first use in this function)
make: *** [ObjXU/os_macosx.o] Error 1
[

Taro Muraoka wrote:

> Try attached file.  I have placed same one at:
>   http://www.kaoriya.net/testdir/osx_buildset-6.2f.006.tar.bz2
>
> Extract all files and set those in src directory and do:
> $ make -f Make_osx.mak
>
> I propose these files to be included in the release package, but is it
> too late?

It is quite late.  Although including a few files probably won't hurt
other systems, it seems we end up with an unorganized bunch of files for
building the Mac versions.  This is becoming a bit messy.

At least the INSTALLmac.txt file would need to be updated to explain
what all the files are for.   For example, what make program is needed
for this Make_osx.mak?  And the file should give the casual user an idea
of what version he will want to build.

Perhaps it should be organized in sections for where you can run the
produced Vim: OS 9, OS X native, OS X with X11, OS X in a terminal?
Then make sub-sections for various compilers, if needed.

--
The acknowledged parents of reengineering are Michael Hammer and James Champy.
When I say they're the "parents" I don't mean they had sex - and I apologize
for making you think about it.  I mean they wrote the best-selling business
book _Reengineering the Corporation_, which was published in 1993.
    Businesses flocked to reengineering like frat boys to a drunken
cheerleader.  (This analogy wasn't necessary, but I'm trying to get my mind
off that Hammer and Champy thing.)
				 (Scott Adams - The Dilbert principle)

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html ///

I have compiled vim 6.2f BETA for OS X (Carbon, Aqua interface).
I have not yet tested the binary much.  That's your job!  Please help
test this, so we can try to fix problems (if any) before the upcoming
release of vim 6.2.

       I compiled with Muraoka Taro's new Make_osx.mak .  I could not get
it to compile with iconv and gettext, so it does not have these features.

       As always, you can find my binary at
http://macvim.swdev.org/OSX/

					 --Benji Fisher

Hey Folks!

Let me presume that this has been beaten to death already....  but.

Any reason we don't compile with python support?  The mac is shipping
with it, fully supported....   does it pose difficulties that prevent
including it everywhere?

--p


On Tuesday, May 27, 2003, at 01:59 PM, Benji Fisher wrote:

>      I have compiled vim 6.2f BETA for OS X (Carbon, Aqua interface).
> I have not yet tested the binary much.  That's your job!  Please help
> test this, so we can try to fix problems (if any) before the upcoming
> release of vim 6.2.
>
>      I compiled with Muraoka Taro's new Make_osx.mak .  I could not
> get it to compile with iconv and gettext, so it does not have these
> features.
>
>      As always, you can find my binary at
> http://macvim.swdev.org/OSX/
>
> 				 --Benji Fisher
>
>



Patrick Curtain,  Husband & Father  ( i also write software )
             Building the BEST software, the FASTest way.
http://www.patrickcurtain.com/                          360.521.9625

Oupsie, forgot to send a patch over os_mac.pbproj after I got Vim 6.2
to compile.
Here's the patch.

Le mardi, 27 mai 2003, à 11:31 Canada/Eastern, Vince Negri a écrit :

> Benji,
>
> It appears that you just have ex_eval.c missing from the
> OS X makefile.
>
> Vince
>
>> -----Original Message-----
>> From: Benji Fisher [SMTP:benji@...]
>> Sent: Tuesday, May 27, 2003 4:30 PM
>> To: vim-dev@...; vim-mac@...
>> Subject: link errors:  vim 6.2f on Mac OS X
>>
>> Vim-dev and Vim-mac:
>>
>>       I apologize for the cross-posting, but I think this is the best
>> hope
>> for
>> solving this before the release of vim 6.2.  I tried to compile vim
>> 6.2f
>> on Mac
>> OS X and I got the following linking errors below.  Judging from the
>> names
>> of
>> the undefined symbols, I guess this has to do with the try/catch
>> mechanism.  Any
>> suggestions?  If I am right, how do I compile without try/catch?
>>
>> 				 --Benji Fisher
>>
>> [...]

Dany St-Amant wrote:
>
> Oupsie, forgot to send a patch over os_mac.pbproj after I got Vim 6.2 to
> compile.
> Here's the patch.

       I usually compile with Muraoka Taro's Make_osx.mak instead of Project
Builder, so (unless I am confused) this patch does not affect me.  Is it
possible to get perl support and Aqua GUI compiling with pbxbuild?

       Can someone else test the compilation with Project Builder?  We have to
rewrite INSTALLmac.txt one of these days ...

					 --Benji Fisher

Patrick Curtain wrote:
> Hey Folks!
>
> Let me presume that this has been beaten to death already....  but.
>
> Any reason we don't compile with python support?  The mac is shipping
> with it, fully supported....   does it pose difficulties that prevent
> including it everywhere?
>
> --p

       I look forward to the day when I can maintain the Mac OS X binaries with a
simple "make".  Currently, we can get an Aqua interface from Project Builder or
from Muraoka Taro's Make_osx.mak .  Neither of these is integrated with the
configure/make routine that we use on Linux etc., so adding Python support is
not so simple as adding a configure argument.  If someone can tell me how to get
Python support in the Carbon version, I will be happy to do it.

					 --Benji Fisher

On Tuesday, May 27, 2003, at 08:49  AM, MURAOKA Taro wrote:

> Try attached file.  I have placed same one at:
>   http://www.kaoriya.net/testdir/osx_buildset-6.2f.006.tar.bz2

Below is a tarball containing patches that address a few issues
with these files:

o  infplist.diff patches infplist.xml to set CFBundleSignature
     to "VIM!" (instead of its current, default value of "????")

o  Make_osx.diff applies the following patches:
     -  makes ICONV default to "no" (because os_macosx.c doesn't
        seem to compile with ICONV enabled)
     -  adds a target that builds the Contents/Resources/gvim.rsrc
        file, which is needed for some of Vim.app's dialog boxes
        [Benji: It looks like your latest binary suffers from the
        inputdialog() crash because it lacks this file.]
     -  changes the creator code in Contents/PkgInfo to "VIM!"
     -  adds Python support, currently disabled (because if_python.c
        appears to be incompatible (?) with Python 2.2).

Finally, unrelated to the above, os_mac_h.diff patches os_mac.h
to prevent gcc from printing lots of "warning: trigraph ??' ignored"
messages.  (The patch replaces #define UNKNOWN_CREATOR '????' with
#define UNKNOWN_CREATOR '\?\?\?\?'.)

Peter

---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------

begin 644 patches.tgz
M'XL(```````"`^U9^W/BR!'VK_9?T?9MSN!%Z,'+:.V]Q2![2<RC`#N^NKM2
M"6D`E?4Z/5BXRA^?GM$#.<8DJ<VRJ839VF(>W3/=/3W?IQGWM&>BNL&J;)BS
MV=&W*8(H"/5J]4C`TJC7V:\@Q6T!!RL5\8@.U(1JHRIB71"E6D4Z$H[V4*(@
MU'Q<TB,A\7?(H=@W"]!W+!<7%]!+<\#6GH\G$<&.-4@-D`19JLJ5)E:$R@G'
M<6]+2G)5E&M"+'GQLM`VB$));`!K`OQPW%%N'NZNUR0`UP=B>^$:"@:9:9$5
MRG&[R.0>^MVG5,QQ<S+8%TL,E='];HEN3WE;X)0*M`?]Q]USW"F3B?(TV2W4
M>[B?=.];_;MK2W/FXB\E^B/]5B[#WT"SK)R*XSHDU@%05IKM6220681IG"X!
M:]Q>X_2>2OP\^3SH;Y5QW*\.93K%7B*Y+0.KM1(F*&O20%?KI9J4!KKW"-=@
M+X&;8:,]:=V-L:V'VCS`-HV<JCPIV,5'@<]/38?WB&]AT$;*N#>ZHP,=LB26
MB]W\Q'6M@!^1H$?\.?%Q`FK>?[3$$\*MI<W!B_[XPR);/6Y*I69CXW&S6A)%
M,749X&G\<#,<JI.?ATJO-40GWA68JYWNJ,@KJ_`A--&1<.T16_-0@SC($=0=
M3!88KL.%ZT#70=2<:3K!3G/FX+9`G$;8AJ2*,SLNMF-]*D=^AP+N=8FNR$2*
MQ9R\BCETBT:D\;;,*>^QY:2RQ.NN,S/G3+RCW([A_35PG5AQV)I\OCX_DU]K
M;>GB/4L+.4/SOYC.MF%L<>'S6R/&VK%<S=@V')@AX3Q-?];F)#@[!V;JX.;/
MU-)WA<'#A,77G*FQ2MG-]7IK-?:O[#*U;K]]_]!18B^[;#'3T:W(()L%F>!]
MY_:>9BV5NW\S:L!961=P$:BJ$=GVFE6'ZYZFJXKOXZ'D9KYFDR^N_PSC=1`2
M.]_3=GTR)O[2U/$$Y_IOW<@QM-!TG=Q>TTS%)/&B$'H$5S9`,<P0ERC@:H,Q
M/$$0>9[KAX#0`@4=#S<Q8#+N%?&<?]'6#`^2Q$()EK=4\IIBQ1M$(Y5$X3*E
M&F;`O3DU,0)+1,S(8B:"I:V)#],U1('IS&&BM%^;1#M?6T$1#K$.XEIBR>9T
MO,AN)E(L,K,WV=IKM0=C]4EEHTKO(09^L5X2I0R1]F`W'LJO,WMK^)N5DMB\
MW*".)#1*$E)_XA=55CN#]N1IPA`G6!#$<W,&OP!'P'!U+ER%95-W`O@-/D"X
M(`X0?>&^'/H`Q`I(//`!9F8QF7G,YM0,P_/)S%QA'1&:G:S4+;4U'!;3.MJ1
MKZ--S&D*<`BO;4L+`E,'GP1NY&.V,^`;)2V8T:0OF`ZUD39L<&>@0=D/?!U-
MLDB1]F:S/)HVVRG`K6HRPH7)P@R8)."O9@4N+O5[9/IX`J@FVU-4*U.B&8_:
MS+?4GW<%=`1)J<C62TX:>3F98!9$7T*-2F2`P`2]/&3S89IG@^6<?6C9,D
MW*>*E-LX9$BI5DLWC@(6DEY9E[/J*H`-.QPG[$%M0CMC<BD"Y_ENZ%(Q!(M$
M.AM.N:>X&<I$KN`CO/NTV0WT,@>:U..ML"EGG)+22#$!/Z:#5K9QSSD$W4\[
M)!%L7PWB"?C<>E18NWNG?L9V?Z#V6MW^)OK(FKX&!O'P6!%'7V/WQDHW4&U-
MIU_/S,K!F!VH)[6C#)5^9ZPB#;ZY.=5+W(OL^SG>2<YT9CA3VC),'WZ--P)3
M@ZW8=I&>G3#@A\_S+@K#EB':7_8L,PCIXJ?I;&G2R_GITW4Q3$&,4?D>.3E*
MX^*+,?KI%B$7OIC)<_GL+N%9U&K=P$[X\4>@J06Y04Q`-PJI4KG,9P<`U\H^
M$MEZ+&4;8DFZS##TOR%,F2`]I?\D9._SPG2(GOIBG%W[#>;6'*PC0#0J.6)]
M.X+RBYOB%D%JY"<&WV=MGR"U(9<ENF<8W62,<^`,->]_PG*6X0'LWA_$)V?&
M:N65;;TP9-NJ&\6S.(?PJUEJ7N9X>&]N/G9[I_MP<^ON-FIX='+WHXH@E"I"
M\T4<4O+Y$V-A&>+?^#"U*:U>4=O?`P-GEKPRS".3PEY*4Z\,\_-\>A9#='RM
M8O-Q1A!V`^C<QIB=W:8@N9S1'QDN$+(ORHL<,YT<'<J_4K(D^F[O?_0!4$C?
M_RJU>HV]_]7%^N'];T_O?WD@^8?WOTH]>]6CH+!+LB$+E1WO?_@!4TVYX_CX
MZIFL/[9O;QB)C1=X:WDD?H`7G''H(RI<\70\E@Q8ST>$0O51&5WQ27O+-.;<
MT<+()XGV:4Z;,DA>];5V\H!C(\R.R!PMV6*#XLS1^\5F(G9Q8YXE,+E_SRAI
M?`//#LCX_U'B2XFZ^)[X7Y52_*]4J]5Z\O>?Q@'_]U"Z>%%=R1"G07EQ<OWU
MY634'K-G#1EX?1GXKAOR2]-F_^DM/EVKM#SQ"<(-6<;?@4N3PB2(9:EZ0K,1
M.+R'^[2Y,8]22=HX%NLQ_R#G@(`,),F2"!Q-J6,V"47G3%BZS`E7962L:C,6
MWLI7E4:C5+G,&.L'O-3/3(>`K2]4?8$7J$)0A+1"!;+7\5/@+Z`%]*F'7O%"
MS0E!U^+GNJDY!\]WIQ:Q(70A6#NAMH*%.5]8^)]]#U_P]`\IR6H/_;_T!W_M
MJ^V1TIH,1G!.>>P\1GF>V@47[*G((--H/D?U^-.=V9Y]NO^;MM,WPJ]P@*DG
M<]`G+2V3IX;2M[(V3FM[F!^^C%;@A9:^=_FNG7K'=''R\U]_BO^=TY:V=$T#
M,%WFON8MX(OF.[A:`(4:3_>TR-1VQBZ;;E?\#HQP*(=R*(=R*(=R*/_KY>_Z
'_\#Z`"@``(OF
`
end

Dany St-Amant wrote:

> Oupsie, forgot to send a patch over os_mac.pbproj after I got Vim 6.2
> to compile.
> Here's the patch.

No, it's not here...
Perhaps the maillist has a problem with the file.  You can e-mail it
directly to me (and others), preferably uuencoded or something like
that.

--
Engineers understand that their appearance only bothers other people and
therefore it is not worth optimizing.
				 (Scott Adams - The Dilbert principle)

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html ///

Rain Dog wrote:
> On Tuesday, May 27, 2003, at 08:49  AM, MURAOKA Taro wrote:
>
>> Try attached file.  I have placed same one at:
>>   http://www.kaoriya.net/testdir/osx_buildset-6.2f.006.tar.bz2
>
>
> Below is a tarball containing patches that address a few issues
> with these files:

       Thanks for the patches.  I have applied them and posted a new binary,
again with minimal testing.

> o  infplist.diff patches infplist.xml to set CFBundleSignature
>    to "VIM!" (instead of its current, default value of "????")

       That is one of many things I did not test.  I did a diff of the makefiles,
but they were too different for me to figure out what was missing.

> o  Make_osx.diff applies the following patches:
>    -  makes ICONV default to "no" (because os_macosx.c doesn't
>       seem to compile with ICONV enabled)

       That is what I find, too.  It also seems that gettext depends on iconv.

>    -  adds a target that builds the Contents/Resources/gvim.rsrc
>       file, which is needed for some of Vim.app's dialog boxes
>       [Benji: It looks like your latest binary suffers from the
>       inputdialog() crash because it lacks this file.]

       That is probably the best reason for me to update the binary.

>    -  changes the creator code in Contents/PkgInfo to "VIM!"
>    -  adds Python support, currently disabled (because if_python.c
>       appears to be incompatible (?) with Python 2.2).

       This does not work for me.  I'll send you the error messages later (when I
find time).

> Finally, unrelated to the above, os_mac_h.diff patches os_mac.h
> to prevent gcc from printing lots of "warning: trigraph ??' ignored"
> messages.  (The patch replaces #define UNKNOWN_CREATOR '????' with
> #define UNKNOWN_CREATOR '\?\?\?\?'.)

       I noticed that warning, too.  Can we make this little patch official?
(IMHO we do not need to make the extended comment a permanent part of the code:
   just put that info in the patch description.)

       I do not have time now to put all the files on my web site.  For now,
anyone who wants to compile at home needs the extra files from Mraoka Taro, with
Peter Cucka's patches recommended.

       Minor requests for make gurus:

1. I think there is still a "6.0" in infplist.xml .  I changed it by hand to
"6.2f".  IIUC, this file is processed by Make_osx.mak, so it should be possible
to do this automatically.  Can anyone fix this?

2. The .rsrc file is distributed as a .hqx file.  Can we add a rule for this?

					 --Benji Fisher

Bram Moolenaar wrote:
> Dany St-Amant wrote:
>
>
>>Oupsie, forgot to send a patch over os_mac.pbproj after I got Vim 6.2
>>to compile.
>>Here's the patch.
>
>
> No, it's not here...
> Perhaps the maillist has a problem with the file.  You can e-mail it
> directly to me (and others), preferably uuencoded or something like
> that.

       I put a copy on the web site.  Here is the only link to it:

http://macvim.swdev.org/OSX/files/project2.diff

I have still not tested it.  Any volunteers?

					 --Benji Fisher