all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: GUI vs TTY when saving & restoring framesets
Date: Sun, 22 Jan 2017 21:11:03 +0200	[thread overview]
Message-ID: <83k29m52rc.fsf@gnu.org> (raw)
In-Reply-To: <20170122185537.GC12823@acm> (message from Alan Mackenzie on Sun,  22 Jan 2017 18:55:37 +0000)

> Date: Sun, 22 Jan 2017 18:55:37 +0000
> Cc: lekktu@gmail.com, emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> > > the order in my desktop file.
> 
> > Why is that a problem?  The order of buffers in the desktop file is
> > not something a user is supposed to look at, or care about.
> 
> I care a great deal about it.  I have set up keys <f1> to <f11> in the
> global key map to mean "switch to frame Fn".  Thus, rather than just
> being an arbitrary GUI window, each frame is associated with a particular
> function key.  I even have "Fn" in the mode line to see which frame I'm
> in.
> 
> Usually when I close an Emacs session, I quickly type <f6>, <f5>, ....,
> <f1> to order the buffers in my .emacs.desktop.  When I start Emacs (in a
> Linux tty, usually, with desktop-restore-frames nil) I do, repeatedly,
> C-x 5 b <cr> to set up the same buffers in the "same" frames.  For this,
> I need the buffers to be loaded in the right order, WITHOUT *scratch* as
> an interloper.  At the moment, this isn't happening in master in some
> circumstances.

I don't really understand the need for this.  I always have several
frames in my sessions, each one with its buffer, and when I restore
the sessions, each frame comes up with the same buffer it had when I
shut down Emacs, no complicated frame-walking dance necessary, neither
before shutting down Emacs nor after restarting it.  Maybe this stuff
you do is the culprit?




  reply	other threads:[~2017-01-22 19:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22  4:21 GUI vs TTY when saving & restoring framesets Juanma Barranquero
2017-01-22  4:23 ` Juanma Barranquero
2017-01-22 13:27 ` Alan Mackenzie
2017-01-22 16:31   ` Eli Zaretskii
2017-01-22 18:00     ` Alan Mackenzie
2017-01-22 18:14       ` Eli Zaretskii
2017-01-22 18:55         ` Alan Mackenzie
2017-01-22 19:11           ` Eli Zaretskii [this message]
2017-01-22 19:38             ` Alan Mackenzie
2017-01-22 20:03               ` Eli Zaretskii
2017-01-22 20:44                 ` Alan Mackenzie
2017-01-22 21:06               ` Juanma Barranquero
2017-01-23 17:39           ` Andreas Schwab
2017-01-23 18:02             ` martin rudalics
2017-01-22 16:23 ` Eli Zaretskii
2017-01-22 21:15   ` Juanma Barranquero
2017-01-23  3:36     ` Eli Zaretskii
2017-01-23 14:15       ` Juanma Barranquero
2017-01-23 15:49         ` Eli Zaretskii
2017-01-23 16:14           ` Juanma Barranquero
2017-01-23 16:16         ` Stefan Monnier

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=83k29m52rc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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.