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

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

> > The proper default value to use, once bug #20274 is fixed, should
> > be discussed in that context, not in the context of this temporary
> > workaround (#23604).
> >
> > Let's have that discussion there and then.
> 
> I don't see any point in delaying the discussion.  The correct
> default value is clear already.

The discussion is for bug #20274.  It makes sense to continue it
after that bug is fixed, or perhaps while fixing it.  Especially
since if you are making arguments in favor of a particular default
value based on the problem that is #20274.

If the nil use case is as insane as you say it is, then there is
apparently no sense in trying to fix bug #20274 to make it work.

> > It should be possible to try that and fall back if it is not
> > possible for some reason (e.g. the display does not exist).
> 
> Feel free to suggest such a test.

Sorry, I won't be fixing bug #20274.  And what you are discussing
now is exactly how to do that.

Do you maintain your claim that the nil use case is anyway so
inherently problematic that it is not a "sane" case, whether or
not it is the default behavior, so there is, in effect, no bug
#20274 to be fixed - no need to try to make Emacs provide a
reasonable behavior for nil?

> > But we should discuss this later and not here.  This bug is only
> > about the temporary workaround of setting the value to `t' _to
> > avoid bug #20274_ rearing its head by default.
> 
> I don't see that as a temporary workaround, I think the default should
> be t regardless.

But you apparently also think that the nil value should be
removed altogether, because it is not "sane".  No?

Regardless of such an opinion, that is for bug #20274, not this
bug.  Please take discussion of it there.