From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ken Raeburn Newsgroups: gmane.emacs.devel Subject: Re: a little feedback on Cocoa Emacs.app Date: Mon, 4 Aug 2008 15:28:42 -0400 Message-ID: <35E82E8D-B8CD-4EDC-B620-F18DA99BF1A1@gnu.org> References: <4358E889-E5D2-4E68-83D3-E6AB9C03F7B5@gnu.org> <508B5967-EAA1-4DEA-8533-19E4C0CD4ECF@gnu.org> <9F4D1718-BBB2-489C-8124-35189C98775E@gnu.org> <2616537B-2ECE-4C20-B707-3C802DC4C10D@gmail.com> <25E49984-75A7-4879-93B5-22C240F8950C@gnu.org> <200808041704.m74H4Zu9008903@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v928.1) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1217878152 18033 80.91.229.12 (4 Aug 2008 19:29:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Aug 2008 19:29:12 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 04 21:30:02 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KQ5km-0004ms-Go for ged-emacs-devel@m.gmane.org; Mon, 04 Aug 2008 21:30:00 +0200 Original-Received: from localhost ([127.0.0.1]:58516 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KQ5jq-0000La-W5 for ged-emacs-devel@m.gmane.org; Mon, 04 Aug 2008 15:29:03 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KQ5jm-0000L4-8k for emacs-devel@gnu.org; Mon, 04 Aug 2008 15:28:58 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KQ5jl-0000KT-AY for emacs-devel@gnu.org; Mon, 04 Aug 2008 15:28:57 -0400 Original-Received: from [199.232.76.173] (port=57325 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KQ5jl-0000KO-6C for emacs-devel@gnu.org; Mon, 04 Aug 2008 15:28:57 -0400 Original-Received: from raeburn.org ([69.25.196.97]:20010) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KQ5jY-0008BM-9U; Mon, 04 Aug 2008 15:28:51 -0400 Original-Received: from NOME-KING.MIT.EDU (NOME-KING.MIT.EDU [18.18.1.160]) by raeburn.org (8.14.1/8.14.1) with ESMTP id m74JShLE019153; Mon, 4 Aug 2008 15:28:43 -0400 (EDT) In-Reply-To: <200808041704.m74H4Zu9008903@sallyv1.ics.uci.edu> X-Mailer: Apple Mail (2.928.1) X-detected-kernel: by monty-python.gnu.org: NetBSD 3.0 (DF) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:102059 Archived-At: On Aug 4, 2008, at 13:04, Dan Nicolaescu wrote: > Ken Raeburn 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