[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: Juanma Barranquero
Subject: bug#23604: desktop-restore-in-current-display should default to t
Date: Tue, 24 May 2016 02:37:00 +0200

On Tue, May 24, 2016 at 2:23 AM, Paul Eggert <address@hidden> wrote:

> Anyway I hope Juanma has time to weigh in so that we don't need to guess.

I'm alive, which is quite different from active.

Regarding this issue, if memory serves I'd say desktop-restore-in-current-display defaults to nil because

a) It made sense (to me anyway) that you would restore frames where they were created. "Bringing them" to the current display seems to me like a specialized use (a last resort), not the default one. If having it set to nil means that you open a frame "half a world away" is because you were working with a display half a world away in the first place...

b) I could be wrong, but I think that was Stefan's preferred default.

That said, I really have no strong preference. We should use the one which is likely to cause less trouble. OTOH, if it does cause trouble only for "Emacs users that run the tmux terminal multiplexer atop xterm", it could be solved at the social level (I mean, warning users), or there's perhaps a way to detect it (perhaps some frame parameters could give a clue?) and avoid the problem altogether.

Am I making any sense?


reply via email to

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