[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Eli Zaretskii
Subject: bug#23604: desktop-restore-in-current-display should default to t
Date: Mon, 23 May 2016 21:19:49 +0300

> Date: Mon, 23 May 2016 10:47:36 -0700 (PDT)
> From: Drew Adams <address@hidden>
> Cc: address@hidden, address@hidden
> > Leaving it at nil makes no sense to me.  It means that you invoke
> > Emacs, which will then display on a different terminal -- could be a
> > terminal half a world away.  That could be something that is desired
> > in some specialized use cases, but makes no sense at all as the
> > default.
> > 
> > This problem will exist on any platform that supports X displays,
> > i.e. on any Posix system.
> > 
> > > Anyway, the right course of action now (if Emacs 25.1 is released
> > > with the default value changed to t) is (after the 25.1 release)
> > > to fix bug #20247 and revert the default value to nil.
> > 
> > No, the right course is to set it to t and leave it at that.
> You elided this, just after that paragraph:
>   At that point, if there is disagreement about the default value,
>   ^^^^^^^^^^^^^
>   i.e., if someone really thinks it should be t by design (and not
>   just as a workaround), then we can discuss the pros & cons for
>   the default behavior.

And you elided the part where you claim that no arguments were
presented in favor of the non-nil value.

> 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.

> 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.

> 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]