163Re: Practical development of Mac vim
- Feb 6, 2001
> 1. How many people actually possess the vis, vim or vigorSince MPW is free now, there is no limitation.
> < URL:http://www.dictionary.com/cgi-bin/dict.pl?db=*&term=vim > to
> compile either a 68k or PPC executable for themselves?
> 2. I am have difficulty with Mac line endings in that some files whichWell, post it for review.
> the standard executable can read, mine cannot. For this reason alone,
> I am reluctant to post my work, as it might be confusing.
> 3. What objectives on the to do list achievable for the non expert asVim 6.0t should be compilable with MPW. (With some minor problems. Bram
> I am? Here are some possibilities:
> a) Fix up an MPW makefile to avoid the dependence on CodeWarrior
already has the patch.)
> b) Establish a 'prefs' file (which should contain a pointer to theI don't see this as a big advantage. Especially since sripts from other
> runtime folder, allowing the runtime folder, or pouch, to be placed
> anywhere on the system
platforms will look at the standard locations.
> c) Double clicking on a prefs or settings file should act as 'vim -u'This could indeed help.
> and bypass other initialisation.
> e) We could have a scheme for running plugins such as BBEdit plugins <Using MPW tools would be a great plus. I would love to call "sort" or
> URL:http://www.barebones.com/support/bbedit/bbedit-plugins.html > or (much
> more work?) MPW tools, <
> URL:http://devworld.apple.com/tools/mpw-tools/books.html#ToolServer > but
> perhaps also useful...
some other tools on my Mac.
> f) See whether Mindvision <There is nothing to install. Unpack the archive and doubleclick the
> URL:http://www.mindvision.com/pricing/shareware.asp > would let us use
> Installer Vise, as is the case with MacPerl, <
> URL:http://devworld.apple.com/tools/mpw-tools/books.html#ToolServer >
> another open source cross platform project that predates Linux.
> 4. I have copied the vim 6.0t sources into my Mac tree, and theMaybe a backslash in the pathname problem? Vim doesn't like that.
> project compiles, IIRC, without a hitch; but it does not run smoothly
> because it appears not to grok the explorer.vim plugin, but the
> error messages (basically that a backslash was found where it was not
> allowed does not appear to be Mac specific.
> 5. Is there anyone using MacVIm for serious work willing toThere are about 20 known users, I don't think most of them read this
> comment on how we are getting on?
There is nothing left to try
There is nothing left to choose
There is no greater power
Than the power of VI
- << Previous post in topic Next post in topic >>