The usual argument here (and I don't dispute it) is that i3 is a window
manager, and window managers aren't responsible for identifying screens.
Now, it happens that the major competitors -- gnome and kde mostly --
are also desktop environments, and DE's are responsible for handling
screens. So the question arises.
My personal opinion is that i3 and other similar WM's could use a really
good HOWTO or even descent apt-get'able package that just handles these
missing details -- screen support, automatic volume mounting, etc. But
I don't think it's i3-dev's responsibility, I just think it's lacking in
this otherwise ideal world.
Jeff Abrahamson
+33 6 24 40 01 57
+44 7920 594 255
http://p27.eu/jeff/
http://transport-nantes.com/
On 23/01/2019 18:06, Luís Moreira de Sousa (Redacted sender
luis.de.sousa for DMARC) wrote:
Hi Jeff,--
could you elaborate on why this is not an i3 issue? Perhaps I am
trying to address it the wrong way.
Thank you.
--
Luís Moreira de Sousa
Bowlespark 8
6701 DN Wageningen
The Netherlands
Phone: +31 628 544 755
Email: luis.de.sousa@xxxxxxxxxxxxx <mailto:luis.de.sousa@xxxxxxxxxxxxx>
RingID: ring:7ca91d83f4f9dec82fec9f1144b8e5c1ef2a110c
URL: https://ldesousa.github.io
Sent with ProtonMail <https://protonmail.com> Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, 23 January 2019 17:45, Jeff Abrahamson <jeff@xxxxxx> wrote:
I'm afraid the only reliable technique I've found is to logout and
login again. Neither xrandr --output --auto nor arandr reliably do
the right thing for me, though they often do with some fiddling.
This is usually viewed as a "not i3" issue, which, while technically
correct, of course doesn't address the point you make that coming
from many other environments this is automatic and so we don't see it.
Jeff Abrahamson
+33 6 24 40 01 57
+44 7920 594 255
http://p27.eu/jeff/
http://transport-nantes.com/