From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: GUI vs TTY when saving & restoring framesets
Date: Mon, 23 Jan 2017 17:14:39 +0100 [thread overview]
Message-ID: <CAAeL0SR+xHW4tU3Epyv6465wdqexsTaHrOKszoExB7pgcuJVbA@mail.gmail.com> (raw)
In-Reply-To: <838tq14w07.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]
On Mon, Jan 23, 2017 at 4:49 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> A I've said earlier, if we think different users might want different
> behavior in this respect, we should have a customizable option.
Agreed.
> In any case, the simplest case should work as expected: when the
> desktop file records only one frame, it shall be restored as a single
> text-mode frame when Emacs is started with -nw, I think.
Yes. I'm surprised this failed. This is basic stuff.
> I'm not sure this is desirable. It is IMO more natural to have the
> same frameset for all sessions. But that's me. Full disclosure: I
> never restore my sessions into Emacs started with -nw, except for
> testing these issues.
Same here. I never work with -nw except for testing purposes.
> Frame restoration is a relatively recent feature, so I think we should
> first make sure it works correctly in the simple scenarios, before we
> start extending it to support more exotic ones. As one data point, I
> don't think anyone has yet requested the features you describe above.
Depending where we want to go, these features aren't more exotic, just a
generalization of sorts. But I agree with you. Don't want to waste my time
with something that people doesn't need.
> I didn't write the above to assign blame.
I know. But that you don't blame me doesn't mean I don't feel a little
guilty. I've disliked when someone started some big (or user-visible)
change in Emacs and then disappeared (not a very common occurrence, but not
unheard of). And I did the same. Hi pot, meet kettle.
[-- Attachment #2: Type: text/html, Size: 1986 bytes --]
next prev parent reply other threads:[~2017-01-23 16:14 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
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 [this message]
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
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=CAAeL0SR+xHW4tU3Epyv6465wdqexsTaHrOKszoExB7pgcuJVbA@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=eliz@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).