From: Ken Raeburn <raeburn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: a little feedback on Cocoa Emacs.app
Date: Mon, 4 Aug 2008 15:28:42 -0400 [thread overview]
Message-ID: <35E82E8D-B8CD-4EDC-B620-F18DA99BF1A1@gnu.org> (raw)
In-Reply-To: <200808041704.m74H4Zu9008903@sallyv1.ics.uci.edu>
On Aug 4, 2008, at 13:04, Dan Nicolaescu wrote:
> Ken Raeburn <raeburn@gnu.org> writes:
>
>> A variation I'd be more interested in, though, might be the ability
>> to
>> run window-less. Much like some Mac apps will let you close the last
>> window, but keep running, and let you open new windows (or quit)
>> through the menus that are displayed even without any open
>> windows. I
>> don't know if there's a good analog for this behavior for X11 and
>> Windows, though, so I'm not going to hold my breath.
>
> This behavior has been on the wish list for X11 for a while... It
> might
> not even be that hard to implement, but nobody has volunteered to do
> it
> so far.
Are there specific ideas for how to keep talking to Emacs in that case
other than emacsclient or gnuclient to tell it to run make-frame, or
is that the way? (Which reminds me... my old usage pattern for Emacs
used to be to run Emacs on the local X display while in front of the
machine, and tell it to invoke make-frame-on-display over ssh when
logged in remotely. One Emacs process, one long-lived Gnus session,
etc. I'd really like to be able to do something like that now, but
with the local display on my Mac using the NS support, which means
supporting both X and NS in one executable, and in one process.... I
also tended to have -- on the local display -- a minibuffer-only
frame, and zero or more minibuffer-less editing frames, so I could
certainly have no editing frames open at times, though there was
always the minibuffer at least.)
I'm mostly just curious; I doubt I'd have time to do anything about
this myself any time soon.
Ken
next prev parent reply other threads:[~2008-08-04 19:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 2:11 a little feedback on Cocoa Emacs.app Ken Raeburn
2008-07-27 2:29 ` Adrian Robert
2008-07-27 2:56 ` Stefan Monnier
2008-07-27 16:45 ` Ken Raeburn
2008-07-28 2:34 ` Adrian Robert
2008-08-04 10:15 ` Ken Raeburn
2008-08-04 12:42 ` mituharu
2008-08-04 13:08 ` Adrian Robert
2008-08-04 12:50 ` Adrian Robert
2008-08-04 16:56 ` Ken Raeburn
2008-08-04 17:04 ` Dan Nicolaescu
2008-08-04 17:23 ` Justin Bogner
2008-08-04 17:27 ` Dan Nicolaescu
2008-08-04 19:28 ` Ken Raeburn [this message]
2008-08-04 21:53 ` Dan Nicolaescu
2008-08-04 23:43 ` Adrian Robert
2008-08-05 3:05 ` Adrian Robert
2008-08-05 4:01 ` Ken Raeburn
2008-08-05 16:17 ` Adrian Robert
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35E82E8D-B8CD-4EDC-B620-F18DA99BF1A1@gnu.org \
--to=raeburn@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).