From: George Plymale II <georgedp@orbitalimpact.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Where is the code for the Emacs server in the core?
Date: Sat, 13 Jan 2018 15:05:13 -0500 [thread overview]
Message-ID: <m0bmhxv81y.fsf@lehi.dev.orbitalimpact.com> (raw)
In-Reply-To: <83inc51z25.fsf@gnu.org> (message from Eli Zaretskii on Sat, 13 Jan 2018 18:52:18 +0200)
Eli Zaretskii <eliz@gnu.org> writes:
>> From: George Plymale II <georgedp@orbitalimpact.com>
>> Cc: emacs-devel@gnu.org
>> Date: Sat, 13 Jan 2018 10:51:55 -0500
>>
>> > The Mac port doesn't support multi-tty with GUI. The developer has no
>> > idea how to detach Emacs as a GUI application from Window Server or
>> > Dock without separating a GUI process (not thread) from the main Emacs
>> > (Lisp evaluator) process. TTY-only multi-tty is supposed to work.
>>
>> That is Yamamoto Mitsuharu's statement on why multi-tty is not supported
>> on the Emacs Mac Port. Does plain GNU Emacs have this problem? If so,
>> how does it get around or solve it? I have to assume that plain GNU
>> Emacs is also attached to the Window Server or Dock as well so I'm
>> wondering if there's something I'm missing.
>
> I know nothing about how macOS works wrt GUI applications, so I don't
> understand what is meant by "attached to the Window Server or Dock",
> nor how to compare that with what Emacs does on X, sorry. Perhaps
> someone else could chime in.
No problem, Alan has given some useful input on my conjectures.
next prev parent reply other threads:[~2018-01-13 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 7:58 Where is the code for the Emacs server in the core? George Plymale II
2018-01-12 9:39 ` Eli Zaretskii
2018-01-13 15:51 ` George Plymale II
2018-01-13 16:52 ` Eli Zaretskii
2018-01-13 20:05 ` George Plymale II [this message]
2018-01-13 17:00 ` Alan Third
2018-01-13 20:02 ` George Plymale II
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m0bmhxv81y.fsf@lehi.dev.orbitalimpact.com \
--to=georgedp@orbitalimpact.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.