Opened 6 years ago

Last modified 5 years ago

#53838 assigned defect

MacVim @8.0.snapshot124 spams console with input method errors

Reported by: PaulForgey (Paul Forgey) Owned by: raimue (Rainer Müller)
Priority: Normal Milestone:
Component: ports Version: 2.4.1
Keywords: upstream Cc:
Port: MacVim


(macOS 10.12.3)

launching mvim from a Terminal window results in the somewhat frequent occurrence of the NSLog() output to the terminal from which mvim was launched:

2017-03-22 11:19:24.847 MacVim[601:9802] IMKInputSession presentFunctionRowItemTextInputViewWithEndpoint:completionHandler: : *NO* NSRemoteViewController to client, NSError=Error Domain=NSCocoaErrorDomain Code=4099 "The connection from pid 0 was invalidated from this process." UserInfo={NSDebugDescription=The connection from pid 0 was invalidated from this process.},

This is disruptively annoying as mvim is not usually used in isolation, but along side edit/run/debug activity in Terminal.

Change History (7)

comment:1 Changed 6 years ago by kencu (Ken)

Would seem to be a Macvim thing rather than a Macports thing to fix....

comment:2 Changed 6 years ago by raimue (Rainer Müller)

Owner: set to raimue
Status: newassigned

It appears that this was dismissed by upstream at least twice. The upstream issues have been closed although there was no solution.

comment:3 Changed 6 years ago by kencu (Ken)

the little script they suggest in one of those reports that launches mvim while redirecting the errors to null would certainly seem the easiest solution, unless you are in the mood to fix their source code for them.

comment:4 Changed 6 years ago by raimue (Rainer Müller)

In any case this should be handled upstream. As the other reports show, this is not specific to MacVim provided by MacPorts.

Such a wrapper script is not a good solution, as it hides any startup errors and might leave users clueless about problems. Nevertheless, if upstream decides this is the correct way to tackle this problem, then this should be done in the mvim wrapper script as shipped with MacVim.

comment:5 Changed 6 years ago by kencu (Ken)

Indeed. That's why I was surprised when you assigned this to yourself rather than closing it.

comment:6 Changed 6 years ago by raimue (Rainer Müller)

The ticket was assigned to me because I am the maintainer of the corresponding port. I acknowledge this is a issue that should be addressed. I am leaving the ticket open as long as the issue exists, so others can find it if they have the same problem.

comment:7 Changed 5 years ago by raimue (Rainer Müller)

Keywords: upstream added

Upstream should decide how to handle this, but so far the issue is being ignored.

Note: See TracTickets for help on using tickets.