From: Drew Adams <drew.adams@oracle.com>
To: Juanma Barranquero <lekktu@gmail.com>, Paul Eggert <eggert@cs.ucla.edu>
Cc: 23604@debbugs.gnu.org
Subject: bug#23604: desktop-restore-in-current-display should default to t
Date: Mon, 23 May 2016 17:54:00 -0700 (PDT) [thread overview]
Message-ID: <def08262-5108-4ebd-94ad-bd132a0e950e@default> (raw)
In-Reply-To: <CAAeL0SSwaodEZUMFoGy05ypoJm3a0+PEFgjDpqa-CE2XPQCH7g@mail.gmail.com>
> Am I making any sense?
To me you are. Thanks for your input and your memory of the history.
My hope is that something interesting and useful can come from
trying to deal with bug #20274, whatever default value is chosen.
The major question is that bug, I think: whether a nil use case
can be made less problematic.
Perhaps one way to start to trim it down a bit is to identify
cases where it is problematic. E.g., "tmux terminal multiplexer
atop xterm", "Emacs -nw", whatever else. And then try to do so
programmatically. IOW, perhaps keeping a nil behavior need not
be a case of all or nothing.
next prev parent reply other threads:[~2016-05-24 0:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 16:37 bug#23604: desktop-restore-in-current-display should default to t Paul Eggert
2016-05-23 17:13 ` Drew Adams
2016-05-23 17:28 ` Eli Zaretskii
2016-05-23 18:07 ` Paul Eggert
2016-05-23 20:33 ` Drew Adams
2016-05-23 21:01 ` Paul Eggert
2016-05-23 21:11 ` Drew Adams
2016-05-24 0:23 ` Paul Eggert
2016-05-24 0:37 ` Juanma Barranquero
2016-05-24 0:54 ` Drew Adams [this message]
2016-05-30 5:50 ` Paul Eggert
[not found] <<278b113b-21aa-5c54-6550-79bf1e481530@cs.ucla.edu>
[not found] ` <<f47f4679-8838-4410-968b-c3e9335fa806@default>
[not found] ` <<83a8jg65vd.fsf@gnu.org>
2016-05-23 17:47 ` Drew Adams
2016-05-23 18:19 ` Eli Zaretskii
[not found] <<<278b113b-21aa-5c54-6550-79bf1e481530@cs.ucla.edu>
[not found] ` <<<f47f4679-8838-4410-968b-c3e9335fa806@default>
[not found] ` <<<83a8jg65vd.fsf@gnu.org>
[not found] ` <<76836464-8187-469c-9ddd-df27b6da1acc@default>
[not found] ` <<831t4s63i2.fsf@gnu.org>
2016-05-23 20:33 ` Drew Adams
2016-05-24 2:31 ` Eli Zaretskii
[not found] <<<<278b113b-21aa-5c54-6550-79bf1e481530@cs.ucla.edu>
[not found] ` <<<<f47f4679-8838-4410-968b-c3e9335fa806@default>
[not found] ` <<<<83a8jg65vd.fsf@gnu.org>
[not found] ` <<<76836464-8187-469c-9ddd-df27b6da1acc@default>
[not found] ` <<<831t4s63i2.fsf@gnu.org>
[not found] ` <<48df821e-5abc-4e05-8b1e-82365ff6f15c@default>
[not found] ` <<83wpmk426m.fsf@gnu.org>
2016-05-24 4:43 ` Drew Adams
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=def08262-5108-4ebd-94ad-bd132a0e950e@default \
--to=drew.adams@oracle.com \
--cc=23604@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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 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).