From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Karoly Lorentey Newsgroups: gmane.emacs.devel Subject: Re: Reordering etc/NEWS Date: Sat, 12 May 2007 01:27:56 +0200 Message-ID: <4644FBFC.6090903@lorentey.hu> References: <2wmz0iriyj.fsf@fencepost.gnu.org> <87fy65k6eh.fsf@red-bean.com> <853b25lk43.fsf@lola.goethe.zz> <87sla5iqhs.fsf@red-bean.com> <85sla5k4py.fsf@lola.goethe.zz> <4642C8C9.5050804@gnu.org> <86tzul15ky.fsf@lola.quinscape.zz> <4642E388.9010503@gnu.org> <86odktypii.fsf@lola.quinscape.zz> <86k5vhyoo8.fsf@lola.quinscape.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1178926092 31450 80.91.229.12 (11 May 2007 23:28:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 11 May 2007 23:28:12 +0000 (UTC) Cc: joakim@verona.se, emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 12 01:28:11 2007 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 1HmeWt-0002X1-2Z for ged-emacs-devel@m.gmane.org; Sat, 12 May 2007 01:28:07 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HmeeL-0006yA-Vw for ged-emacs-devel@m.gmane.org; Fri, 11 May 2007 19:35:49 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HmeeI-0006xg-Jq for emacs-devel@gnu.org; Fri, 11 May 2007 19:35:46 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HmeeI-0006xU-0i for emacs-devel@gnu.org; Fri, 11 May 2007 19:35:46 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HmeeH-0006xR-TK for emacs-devel@gnu.org; Fri, 11 May 2007 19:35:45 -0400 Original-Received: from ninsei.hu ([212.92.23.158]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HmeWm-0003XV-KA; Fri, 11 May 2007 19:28:00 -0400 Original-Received: from [192.168.1.12] (catv5403A040.pool.t-online.hu [84.3.160.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by chatsubo.ninsei.hu (Postfix) with ESMTP id 7F86178F2; Sat, 12 May 2007 01:27:59 +0200 (CEST) User-Agent: Thunderbird 1.5.0.10 (X11/20070403) Original-Newsgroups: gmane.emacs.devel In-Reply-To: <86k5vhyoo8.fsf@lola.quinscape.zz> X-detected-kernel: Linux 2.6 (newer, 3) 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:70871 Archived-At: David Kastrup wrote: > David Kastrup writes: >> joakim@verona.se writes: >>> I dont know. I have only tested mtty on gnu+linux. mtty doesnt have >>> any value on w32 as far as I can imagine, so I usually just use >>> Lennart Borgmans w32 emacs package. >> Why wouldn't it have value? It allows one to keep an existing Emacs >> session around into which one can connect remotely via ssh+emacsclient >> in order to do work. At least once emacsclient has been extended with >> a -nw (--no-window-system) option in order to open a frame on the >> emacsclient tty. Ah, that is good news. If the the Windows port has UN*X-like tty support, then multi-tty can easily support the use case you describe. This will still not involve significantly more porting work than simply fixing the compilation. > One additional possibility: with a sufficient level of craziness, you > might at one point of time link X libraries into Windows executables. > Then it would be possible to connect into an Emacs session running on > a Windows system from a system with an X server (either Windows with > an additional X server, or a posixy system), and have an X frame open > on that system. This would be a very desirable feature, but it needs more work; even the multi-tty branch doesn't support having multiple kinds of graphical terminals compiled in at once. >> It should also allow keeping an Emacs server session around (not just >> iconified, but actually frameless) that one can plug into using >> emacsclient again, and have it open a fresh frame. I intentionally left implementing frameless Emacs sessions after the merge, to let us discuss this proposed feature extensively on emacs-devel. I think we need to make non-trivial design decisions. (Where do messages go when there are no frames? How to recover when someone accidentally calls server-stop?) Currently people usually run multi-tty Emacs in a detached screen session that they never connect to. There are simple scripts to manage this. Screen provides the analogue of a console where you go to check *Messages* or restart the server when there is trouble. -- Karoly