From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: lekktu@gmail.com, 23604@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#23604: desktop-restore-in-current-display should default to t
Date: Mon, 23 May 2016 21:43:47 -0700 (PDT) [thread overview]
Message-ID: <338c6492-fd4a-495e-aa95-ed4da0e73f48@default> (raw)
In-Reply-To: <<83wpmk426m.fsf@gnu.org>>
> I was talking only about the default value. Please stop
> putting your words into my mouth.
Hm. Sorry if I misunderstood you. But these were your words:
Can you explain why using display that is not the current
one even makes sense?
Anyway, great. Glad to hear it, if you're not claiming that
using a display other than the current makes no sense.
So the problems we see now with nil, once taken care of (bug
#20247), should have no bearing on which value to choose as
the default.
Which is what I said: let's see what happens with bug #20247,
and then decide which value is more useful as the default.
(Until then t is more useful, of course - that's this
workaround, #23604.)
next parent reply other threads:[~2016-05-24 4:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[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 ` bug#23604: desktop-restore-in-current-display should default to t 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>
2016-05-23 17:47 ` Drew Adams
2016-05-23 18:19 ` Eli Zaretskii
2016-05-23 16:37 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
2016-05-30 5:50 ` Paul Eggert
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=338c6492-fd4a-495e-aa95-ed4da0e73f48@default \
--to=drew.adams@oracle.com \
--cc=23604@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@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 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).