bug#23604: desktop-restore-in-current-display should default to t

[Drew Adams <drew.adams@oracle.com>]

> >> It's not clear that the original design choice was made in full
> >> knowledge of the problems that have been exposed since then.
> >
> > And yet you cite (below) one such problem, from the time the design
> > was developed, no?
> 
> No, that problem was exposed quite a bit later, months after the
> desktop-restore-in-current-display code was installed.

Yes, but you have there a clear reiteration of the design intent
and the designer saying that he still thinks that is a sane
default behavior.

So sure, the "original" design predates the use of it and hence
the discovery of such a problem.  But that original design was
still supported by the original designer, with knowledge of the
problem.

Let's not quibble about the words.  In that exchange, at least,
Juanma both (a) still considered the nil default to be a good one,
for the original-design reasons that he reiterated, and (b) was
open to the question of changing the default.  IOW, he was saying
pretty much what I'm saying, IIUC: (a) a nil design choice is a
sane one; it supports a good use case and (b) another default
choice could be OK too.