Re: Killing a frame sometimes kills emacs

[Tassilo Horn <tassilo@member.fsf.org>]

"Jan D." <jan.h.d@swipnet.se> writes:

>>> Isn't that the known gtk bug with multiple displays?
>>
>> As said in the reply to Eli, I don't have multiple displays.  There's
>> only one X instance in which emacs runs with exactly one X11 frame.
>> Then I invoked "emacsclient -c" to get another X11 frame, and closing
>> that made emacs crash.
>
> From Emacs point of view, localhost:0 and unix:0 and :0 are three
> different displays, even if they physically are the same.
>
> Try doing the same and after you clicked the link in chromium, evaluate
> (x-display-list).  If you have more than one entry, it is the Gtk+ problem.

Indeed, after opening a new emacs frame from chromium, I have two
entries: (":0.0" ":0").  Before that, it was only (":0.0").

But still, since all other apps somehow spawning new emacs frames don't
create this problem, I wonder if chromium does something special.  I've
checked its sources, and eventually it'll call something like

  XDGUtil("xdg-open", "path/to/file.txt");

You can check that function here:

  http://codesearch.google.com/codesearch#OAMlx_jo-ck/src/chrome/browser/platform_util_linux.cc&l=17

That in turn calls LaunchProcess()

  http://codesearch.google.com/codesearch#OAMlx_jo-ck/src/base/process_util_posix.cc&l=531

Bye,
Tassilo