[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23604: desktop-restore-in-current-display should default to t
From: |
Drew Adams |
Subject: |
bug#23604: desktop-restore-in-current-display should default to t |
Date: |
Mon, 23 May 2016 17:54:00 -0700 (PDT) |
> Am I making any sense?
To me you are. Thanks for your input and your memory of the history.
My hope is that something interesting and useful can come from
trying to deal with bug #20274, whatever default value is chosen.
The major question is that bug, I think: whether a nil use case
can be made less problematic.
Perhaps one way to start to trim it down a bit is to identify
cases where it is problematic. E.g., "tmux terminal multiplexer
atop xterm", "Emacs -nw", whatever else. And then try to do so
programmatically. IOW, perhaps keeping a nil behavior need not
be a case of all or nothing.
- bug#23604: desktop-restore-in-current-display should default to t, (continued)
bug#23604: desktop-restore-in-current-display should default to t, Paul Eggert, 2016/05/23
- bug#23604: desktop-restore-in-current-display should default to t, Drew Adams, 2016/05/23
- bug#23604: desktop-restore-in-current-display should default to t, Paul Eggert, 2016/05/23
- bug#23604: desktop-restore-in-current-display should default to t, Drew Adams, 2016/05/23
- bug#23604: desktop-restore-in-current-display should default to t, Paul Eggert, 2016/05/23
- bug#23604: desktop-restore-in-current-display should default to t, Juanma Barranquero, 2016/05/23
- bug#23604: desktop-restore-in-current-display should default to t,
Drew Adams <=
bug#23604: desktop-restore-in-current-display should default to t, Paul Eggert, 2016/05/30