From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: How to restore the layout? Date: Sat, 29 Jun 2013 02:54:33 +0200 Message-ID: References: <51C5AA68.4000204@alice.it> <51C9C790.3020407@gmx.at> <51CA0D4C.7080204@alice.it> <51CC3E42.7020409@alice.it> <51CC4CC1.3030202@alice.it> <51CC8403.1030009@gmx.at> <51CCA56A.8000508@gmx.at> <51CCA7DC.8060605@gmx.at> <83fvw2g44j.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1372467322 15741 80.91.229.3 (29 Jun 2013 00:55:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 29 Jun 2013 00:55:22 +0000 (UTC) Cc: Angelo Graziosi , Emacs developers , martin rudalics , Eli Zaretskii , Stephen Berman , Jambunathan K To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 29 02:55:22 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UsjRh-0005Fj-Ib for ged-emacs-devel@m.gmane.org; Sat, 29 Jun 2013 02:55:21 +0200 Original-Received: from localhost ([::1]:60226 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsjRh-0003vY-3N for ged-emacs-devel@m.gmane.org; Fri, 28 Jun 2013 20:55:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43240) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsjRe-0003vT-JO for emacs-devel@gnu.org; Fri, 28 Jun 2013 20:55:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UsjRd-0003hP-Cm for emacs-devel@gnu.org; Fri, 28 Jun 2013 20:55:18 -0400 Original-Received: from mail-ee0-x234.google.com ([2a00:1450:4013:c00::234]:61877) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsjRa-0003g6-Tt; Fri, 28 Jun 2013 20:55:15 -0400 Original-Received: by mail-ee0-f52.google.com with SMTP id c50so1317995eek.39 for ; Fri, 28 Jun 2013 17:55:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Zt/kgxKOCSq/VNplqR32GToi+Bw6s4XRaj3YEDaE1uY=; b=nkiODy8WCKp2uhwRjajl8oXfHr9h+PIdtriUOyzpMm8T3zqWum5uLWoiizTak9Psp5 3HySAaRjCkvq3wC211eKgmC+yt57u/tVLHcu5rMY+Q8w5fwe+DDc5iNGjB4L6ILzt6sE QEGobuOMcKf94Ei8USX4n6exWFt7Lbfzc14dVz0ozZkHzBeH7Z7hmxkjHFVDF/AjJ8ml /57BoDYQ4a3gc1YQlavzDWEck1kM3PdXEjyKsbDYkJgZUtNvsmdciqS+6VFOgswVXH7s RCEwaQb9+8od2+05wbxyFXNwh0rAQhSshFZMOAWFZpqAaNUmix4VGf6lO2VdRbl0Ok7L Ed/g== X-Received: by 10.15.36.133 with SMTP id i5mr16026506eev.52.1372467313839; Fri, 28 Jun 2013 17:55:13 -0700 (PDT) Original-Received: by 10.14.142.4 with HTTP; Fri, 28 Jun 2013 17:54:33 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c00::234 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:161261 Archived-At: On Fri, Jun 28, 2013 at 9:36 PM, Stefan Monnier wrote: > It all depends on the use-case, but my own use cases, frames on other > displays/terminals are always "temporary frames" I created via > emacsclient so as to access remotely the state of a running Emacs. The question is, what is the more common use-case? > I suggest you start with "only use the current display" (at least for > the non-daemon mode), since it's a kind of halfway step between the > previous behavior (which did not save&restore the window&frame state) > and the "restore the state on all the displays". The other behavior (try to restore the frame in its original display) is already implemented. I can remove that code, but I wouldn't like to do it unless there are reports of trouble. It could be customized, of course. We could change the meaning of desktop-save-windows (currently a boolean flag), to have: - t : restore all frames in their displays - local-state: only frames already in the current display - current-display: restore frames in the current display etc. (with better names) j