MacVim.app - Snapshot 37

[björn-11]

Hi,

I have uploaded a new snapshot of MacVim.app to

http://code.google.com/p/macvim/wiki/Snapshot

Please download, test, and let me know if there are any problems.

I have done some changes to the communication between MacVim and Vim to
get rid of some potentially dangerous situations, but these kind of
changes also have a way of introducing new problems so be on the
lookout.  (Specifically, the DO connection is only in "event tracking
mode" during live-resize and scrolling to avoid situations where DO
messages arrive e.g. when the menu bar is highlighted as the result of a
Cmd-key being pressed.)

Changes since snapshot 36:
  - Fix bug where Vim would crash when resizing a window with
    double-width characters
  - Add option 'macmeta' to use "alt/option" as meta key to allow
    bindings to <M-..> (see ":h 'macmeta')
  - Add basic support for AppleScript (Jason Foreman).  E.g. to zoom a
    window:
      tell application MacVim
          set zoomed of first window to true
      end tell
  - Fix various bugs relating to initial window positioning
  - Keep window is visible on ":set lines=..." and "set columns=..."
  - Inserting text from "Special Characters" palette works again
  - Remove the functionality to use a modifier key as Esc (use the
    PCKeyboardHack app instead, see ":h macvim-hints | /esc")
  - More help on keyboard shortcuts (":h macvim-shortcuts") and the mvim
    script (see ":h mvim")
  - Speed up live resize
  - Support mvim script symlinks to [m|g]ex and rmvim (see ":h mvim")
  - Tentative support for receiving input from system services (Try
    this: insert "2+3", select the text, then hit Cmd-*.  Result: "2+3"
    is replaced with "5".  Sometimes it seems you have to choose
    "MacVim->Services->Script Editor->Get Result of AppleScript" instead
    of pressing Cmd-* for this to work.)
  - No more Vim zombie processes
  - Add "Reload"/"Ignore All" buttons to the file changed dialog
  - (Almost) Latest runtime files, and Vim patches


Björn

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Ted Pavlic]

> Please download, test, and let me know if there are any problems.

As described before, I still get that weird

"Press ENTER or type command to continue"

whenever I hit F1. In fact, I get it when I type ":help" too. In fact,
the *FIRST* time I do any ":help" command, I get


"Command terminated

Press ENTER or type command to continue"


The "Command terminated" doesn't occur with the F1. It does occur with
every first ":help" in a new window.


Thoughts?
--Ted

--
Ted Pavlic <ted@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[björn-11]

2008/11/16 Ted Pavlic <ted@...>:

>
>> Please download, test, and let me know if there are any problems.
>
> As described before, I still get that weird
>
> "Press ENTER or type command to continue"
>
> whenever I hit F1. In fact, I get it when I type ":help" too. In fact,
> the *FIRST* time I do any ":help" command, I get
>
>
> "Command terminated
>
> Press ENTER or type command to continue"
>
>
> The "Command terminated" doesn't occur with the F1. It does occur with
> every first ":help" in a new window.
>
>
> Thoughts?

Have you tried starting without any rc-files and plugins?

Björn

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Ted Pavlic]

>> Thoughts?
>
> Have you tried starting without any rc-files and plugins?

It's definitely a plugin that's causing the problem. Moving my .vim
directory elsewhere gets rid of the problem.

Here's something funny... Calling "mvim" from the command line fixes the
problem. I only have the problem when I start MacVim via the Finder.

--Ted


--
Ted Pavlic <ted@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Ted Pavlic]

It appears to have been

        hgcommand.vim

that was causing the problem. I've removed it, and everything SEEMS fine...

Thanks. :)
--Ted

Ted Pavlic wrote:
>
>>> Thoughts?
>> Have you tried starting without any rc-files and plugins?
>
> It's definitely a plugin that's causing the problem. Moving my .vim
> directory elsewhere gets rid of the problem.
>
> Here's something funny... Calling "mvim" from the command line fixes the
> problem. I only have the problem when I start MacVim via the Finder.

--
Ted Pavlic <ted@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Brian McKee]

On Sat, Nov 15, 2008 at 8:00 AM, björn <bjorn.winckler@...> wrote:
>
> Hi,
>
> I have uploaded a new snapshot of MacVim.app to
>
> http://code.google.com/p/macvim/wiki/Snapshot

Mirror blew up last night (exceeded disk quota by the email) - will
fix later today - FYI
Brian

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Brian McKee]

On Mon, Nov 17, 2008 at 9:24 AM, Brian McKee <brian.mckee@...> wrote:

> On Sat, Nov 15, 2008 at 8:00 AM, björn <bjorn.winckler@...> wrote:
>>
>> Hi,
>>
>> I have uploaded a new snapshot of MacVim.app to
>>
>> http://code.google.com/p/macvim/wiki/Snapshot
>
> Mirror blew up last night (exceeded disk quota by the email) - will
> fix later today - FYI

Mirror's back syncing again - still want to tidy a couple of things
up, but  it's current again.

FYI, when I said blew up I meant it was still yesterday's data - it
was out of date not broken.

Brian

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[björn-11]

2008/11/17 Brian McKee <brian.mckee@...>:
>>
>> Mirror blew up last night (exceeded disk quota by the email) - will
>> fix later today - FYI
>
> Mirror's back syncing again - still want to tidy a couple of things
> up, but  it's current again.

Thanks for the heads-up Brian.  I haven't decided whether I should
update the appcast yet or whether I should build a new snapshot with
Ben's patch...

Björn

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Brian McKee]

On Tue, Nov 18, 2008 at 3:45 AM, björn <bjorn.winckler@...> wrote:

>
> 2008/11/17 Brian McKee <brian.mckee@...>:
>>>
>>> Mirror blew up last night (exceeded disk quota by the email) - will
>>> fix later today - FYI
>>
>> Mirror's back syncing again - still want to tidy a couple of things
>> up, but  it's current again.
>
> Thanks for the heads-up Brian.  I haven't decided whether I should
> update the appcast yet or whether I should build a new snapshot with
> Ben's patch...

Well, I'm ready for you now :-)

Checksumming is finally being properly confirmed.  If a daily download
or a checksum fails, it never updates the publicly available mirror,
and leaves the previous version in place.

OTOH, if anyone has some suggestions on cleaning up this mongrel code
that swaps BSD style md5 to GNU md5sum style checksums I'd appreciate
it.  (I am not a programmer, as you can probably tell)  It works, but
it looks horrible.

> cat *.md5 | sed 's/[()]//g' | awk '{ print $4," ",$2 } ' | sed 's/  \+\</  /g' > $CHECKSUMFILE ;
> md5sum -cv $CHECKSUMFILE ;

Brian

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Nico Weber]

> Thanks for the heads-up Brian.  I haven't decided whether I should
> update the appcast yet or whether I should build a new snapshot with
> Ben's patch...

Ben's patch fixes a potentially annoying issue, and when you haven't  
even updated the appcast yet, making a new snapshot affects only the  
people who downloaded 37 manually. So that sounds like a good idea.

Nico

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[björn-11]

2008/11/18 Nico Weber <nicolasweber@...>:
>
>> Thanks for the heads-up Brian.  I haven't decided whether I should
>> update the appcast yet or whether I should build a new snapshot with
>> Ben's patch...
>
> Ben's patch fixes a potentially annoying issue, and when you haven't
> even updated the appcast yet, making a new snapshot affects only the
> people who downloaded 37 manually. So that sounds like a good idea.

Yeah, that's what I was thinking, but I need a bit of prodding every
now and then.  Thanks. :-)

I'll post a new snapshot this weekend and leave the appcast alone
until next week.

Björn

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Steve Huff]

On Nov 18, 2008, at 10:07 AM, Brian McKee wrote:

> OTOH, if anyone has some suggestions on cleaning up this mongrel code
> that swaps BSD style md5 to GNU md5sum style checksums I'd appreciate
> it.  (I am not a programmer, as you can probably tell)  It works, but
> it looks horrible.
>
>> cat *.md5 | sed 's/[()]//g' | awk '{ print $4," ",$2 } ' | sed 's/  
>> \+\</  /g' > $CHECKSUMFILE ;
>> md5sum -cv $CHECKSUMFILE ;

not sure this is particularly better, but it uses fewer pipes :)

cat *.md5 | perl -e 'while ( <> ) { chomp; /^MD5\s+\(([^)]+)\).*\s+
(\S*)$/ && print "$2  $1\n"; }' > $CHECKSUMFILE ;
md5sum -cv $CHECKSUMFILE ;

-steve

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Ted Pavlic]

>>> cat *.md5 | sed 's/[()]//g' | awk '{ print $4," ",$2 } ' | sed 's/  
>>> \+\</  /g' > $CHECKSUMFILE ;
>>> md5sum -cv $CHECKSUMFILE ;
>
> not sure this is particularly better, but it uses fewer pipes :)
>
> cat *.md5 | perl -e 'while ( <> ) { chomp; /^MD5\s+\(([^)]+)\).*\s+
> (\S*)$/ && print "$2  $1\n"; }' > $CHECKSUMFILE ;
> md5sum -cv $CHECKSUMFILE ;

While we're at it, get rid of all the pipes and shorten the Perl:

perl -ne 'chomp; /^MD5\s+\(([^)]+)\).*\s+ (\S*)$/ && print "$2  $1\n";'
*.md5 > $CHECKSUMFILE ;
md5sum -cv $CHECKSUMFILE ;

--Ted

--
Ted Pavlic <ted@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[PitPalme]

Hi,

On 18 Nov., 16:07, "Brian McKee" <brian.mc...@...> wrote:
> OTOH, if anyone has some suggestions on cleaning up this mongrel code
> that swaps BSD style md5 to GNU md5sum style checksums I'd appreciate
> it.  (I am not a programmer, as you can probably tell)  It works, but
> it looks horrible.
>
>> cat *.md5 | sed 's/[()]//g' | awk '{ print $4," ",$2 } ' | sed 's/  \+\</  /g' > $CHECKSUMFILE ;
>> md5sum -cv $CHECKSUMFILE ;

What about

awk 'BEGIN {FS="[\ \t=\(\)]+"} /^MD5 \(.*\) = [0-9a-z]+$/ {print $3"
"$2}' *.md5 |md5sum -cv;

or

awk 'BEGIN {FS="[\ \t=\(\)]+"} /^MD5 \(.*\) = [0-9a-z]+$/ {print $3"
"$2}' *.md5 >$CHECKSUMFILE;
md5sum -cv $CHECKSUMFILE

if you prefer the intermediate file ...???

Or shorter (without line syntax check):

awk 'BEGIN {FS="[\ \t=\(\)]+"} {print $3"  "$2}' *.md5 |md5sum -cv
--
Regards,
 Pit
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[PitPalme]

Hello again,

On 18 Nov., 22:19, PitPalme <pitpa...@...> wrote:
> On 18 Nov., 16:07, "Brian McKee" <brian.mc...@...> wrote:
>
> > OTOH, if anyone has some suggestions on cleaning up this mongrel code
> > that swaps BSD style md5 to GNU md5sum style checksums I'd appreciate
> > it.  (I am not a programmer, as you can probably tell)  It works, but
> > it looks horrible.
>
> >> cat *.md5 | sed 's/[()]//g' | awk '{ print $4," ",$2 } ' | sed 's/  \+\</  /g' > $CHECKSUMFILE ;
> >> md5sum -cv $CHECKSUMFILE ;

D**n it ... Who ever inserted the line break ...

> What about
>
> awk 'BEGIN {FS="[\ \t=\(\)]+"} /^MD5 \(.*\) = [0-9a-z]+$/ {print $3"  "$2}' *.md5 |md5sum -cv;
>
> or
>
> awk 'BEGIN {FS="[\ \t=\(\)]+"} /^MD5 \(.*\) = [0-9a-z]+$/ {print $3"  "$2}' *.md5 >$CHECKSUMFILE;
> md5sum -cv $CHECKSUMFILE
[...]
> awk 'BEGIN {FS="[\ \t=\(\)]+"} {print $3"  "$2}' *.md5 |md5sum -cv

(Note the two spaces in 'print' for md5sum compatibility ...)
--
Regards,
 Pit
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Tobia Conforto-2]

> - No more Vim zombie processes

Unfortunately I can still see dozens of Vim processes after I quit  
MacVim.

Maybe it has to do with the fact that I edit files on remote  
filesystems, or maybe it's something else entirely.  I haven't found a  
sequence of operations that reproduce it either, but after a full day  
of work, MacVim leaves behind several Vim processes that start to  
litter the system logs with error messages.

I have attached a piece of log copied from Console.app

The frantic logging starts when I quit MacVim and ends a few seconds  
later, when I type "pkill Vim" in a terminal--something I've taken on  
doing every time I quit MacVim.  (pkill comes from proctools and just  
sends a signal to all processes with a certain name.)

If there's anything you want me to test, let me know.


Tobia


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Ben Schmidt-4]

Tobia Conforto wrote:

>> - No more Vim zombie processes
>
> Unfortunately I can still see dozens of Vim processes after I quit  
> MacVim.
>
> Maybe it has to do with the fact that I edit files on remote  
> filesystems, or maybe it's something else entirely.  I haven't found a  
> sequence of operations that reproduce it either, but after a full day  
> of work, MacVim leaves behind several Vim processes that start to  
> litter the system logs with error messages.
>
> I have attached a piece of log copied from Console.app

Yikes! With logging like that you'll have exhausted your disk space in a
few minutes!

They're not zombies, though. They're clearly still running. Just not
properly...

I have no idea what's causing it. Björn surely will have more idea than
me. But I'm interested...

What OS version are you running?

Do you start Vims by using mvim from Terminal, or the New Window command
in MacVim, or something else?

You don't have Application Enhancer or the Logitech Control Centre by
any chance? Any other similar hacks you have installed?

> The frantic logging starts when I quit MacVim and ends a few seconds  
> later, when I type "pkill Vim" in a terminal--something I've taken on  
> doing every time I quit MacVim.  (pkill comes from proctools and just  
> sends a signal to all processes with a certain name.)

BTW, there's a standard BSD command 'killall' on OSX which basically
does the same thing.

Ben.




--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[Tobia Conforto-2]

Ben Schmidt wrote:
> Yikes! With logging like that you'll have exhausted your disk space  
> in a few minutes!

I know. That's why I kill them right after quitting MacVim.
While MacVim is open, they don't log anything, it's only when I quit  
the app that they cause trouble.

> What OS version are you running?  Do you start Vims by using mvim  
> from Terminal, or the New Window command in MacVim, or something else?

Leopard 10.5.5
I start Vims with the New Window command exclusively.

> You don't have Application Enhancer or the Logitech Control Centre  
> by any chance? Any other similar hacks you have installed?

Why, I have both Application Enhancer and the Logitech Control Centre  
(the daemon only, without the input manager), as well as SIMBL, the  
Ecamm Plugin Loader, and Edit in ODBEditor ;-)  Plus a few third-party  
kernel extensions, daemons, and random cruft.

I can uninstall APE and Logitech, and move all the Input Managers  
somewhere else, if you think they might be the culprits.  I'll tell  
you in a few days if that solved the problem.

> BTW, there's a standard BSD command 'killall' on OSX which basically  
> does the same thing.

Nice, thanks!

Do you know if there's a standard command equivalent to pgrep -fl?  
(list processes that match a regular expression in their full  
commandline)


Tobia

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

[kimo-2]

Hi,

I'm getting similar logs to the one posted by Tobia.  My computer had
only been up for a day (of active coding in vim) and I noticed this
morning 150 Vim processes, but I had less than ten files open.  I
checked my system.log file and it was around 1.4 gigs of exclusively
Vim exceptions:  "connection is invalid."  Here's my vim version:

VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Oct  4 2008 18:37:02)
MacOS X (unix) version
Included patches: 1-22
Compiled by Bjorn Winckler <bjorn.winckler@...>

I just opened MacVim for 1 second to get that version info and these
messages were posted to my Console:
com.apple.launchd[78] ([0x0-0x28028].org.vim.MacVim[592]): Stray
process with PGID equal to this dead job: PID 627 PPID 1 Vim
com.apple.launchd[78] ([0x0-0x28028].org.vim.MacVim[592]): Stray
process with PGID equal to this dead job: PID 593 PPID 1 Vim

I'm not sure if that's related to the issues above, but it seems like
it could be.

Kimo


On Nov 19, 7:20 am, Tobia Conforto <tobia.confo...@...> wrote:

> Ben Schmidt wrote:
> > Yikes! With logging like that you'll have exhausted your disk space  
> > in a few minutes!
>
> I know. That's why I kill them right after quitting MacVim.
> While MacVim is open, they don't log anything, it's only when I quit  
> the app that they cause trouble.
>
> > What OS version are you running?  Do you start Vims by using mvim  
> > from Terminal, or the New Window command in MacVim, or something else?
>
> Leopard 10.5.5
> I start Vims with the New Window command exclusively.
>
> > You don't have Application Enhancer or the Logitech Control Centre  
> > by any chance? Any other similar hacks you have installed?
>
> Why, I have both Application Enhancer and the Logitech Control Centre  
> (the daemon only, without the input manager), as well as SIMBL, the  
> Ecamm Plugin Loader, and Edit in ODBEditor ;-)  Plus a few third-party  
> kernel extensions, daemons, and random cruft.
>
> I can uninstall APE and Logitech, and move all the Input Managers  
> somewhere else, if you think they might be the culprits.  I'll tell  
> you in a few days if that solved the problem.
>
> > BTW, there's a standard BSD command 'killall' on OSX which basically  
> &