public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Upgrading from 5.14 to 6.0 version
Date: Mon, 21 Nov 2022 19:26:30 +0000	[thread overview]
Message-ID: <1882118.taCxCBeP46@lenovo.localdomain> (raw)
In-Reply-To: <tlgf2p$flr$1@ciao.gmane.io>

[-- Attachment #1: Type: text/plain, Size: 3336 bytes --]

On Monday, 21 November 2022 18:12:41 GMT Grant Edwards wrote:
> On 2022-11-21, Michael <confabulate@kintzios.com> wrote:
> > On Monday, 21 November 2022 16:50:14 GMT Grant Edwards wrote:
> >> On 2022-11-21, Michael <confabulate@kintzios.com> wrote:
> >> > On Monday, 21 November 2022 16:11:13 GMT Grant Edwards wrote:
> >> >> I did have to give up the option of having multiple X11
> >> >> screens. The proprietary NVidia driver supported multiple screens,
> >> >> but the drivers for built-in Intel and Radeon drivers don't seem
> >> >> to.
> >> > 
> >> > AMD APUs with embedded radeon graphics work fine here with two
> >> > monitors (DVI + HDMI ports).
> >> 
> >> Yes, multiple montors work fine with both Intel and Radeon embedded
> >> graphics with Xorg drivers.
> >> 
> >> It's multiple X11 screens that isn't supported.  An X11 screen is the
> >> entity that's managed by single window manager and comprises what's
> >> usually called "a desktop". A screen can include multiple monitors.
> >> 
> >> https://wiki.archlinux.org/title/multihead#Separate_screens
> > 
> > You're right, I thought you meant two different monitors in Xinerama
> > style.  I didn't know anyone who still uses separate displays
> > (screens) these days.
> 
> I found it very helpful when I dealing with interruptions (which is
> about 50% of a typical day). I could flip one of the screens to a new
> virtual desktop (while leaving my email and web browser as-is on the
> other screen), deal with the interruption, then flip that screen back
> to the desktop containing whatever I was origininally working on.
> 
> My office setup had three screens, each with four virtual desktops.
> 
> When using multiple screens, you develop the habit of using one screen
> for common, always-on stuff (e.g. email, web browser) and the other
> screen(s) for working on code (or whatever).

I found Enlightenment to be most versatile in this respect.  Unlike say 
Plasma, which has two monitors locked on the same virtual desktop and when you 
switch to another virtual desktop *both* monitors flip over, in Enlightenment 
each monitor can switch to a different virtual desktop independently.  Like 
you, I keep always-on stuff on the left monitor, while switching between 
different virtual desktops on the right monitor.


> There are two main drawbacks to the multiple-screen setup:
> 
>  * You can't drag a window from one screen to the other. With the
>    monitor sizes that are common now, that's not as big an annoyance
>    as it used to be.

With Enlightenment you can move windows across monitors, irrespective of the 
virtual desktop each monitor displays.


>  * There are a few brain-dead (but vital) applications (e.g. Chrome)
>    that refuse to allow a user to run either multiple instances of the
>    application or allow windows on multiple screens (or X
>    servers). I'm a bit baffled by that restriction, but I'm sure it
>    allowed the developers to take some shortcut that saved 12 bytes of
>    data and 10 or 15 lines of code (out of many hundreds of megabytes
>    of occupied RAM and millions lines of code).
> 
> That said, you're right: using mulitple screens is no longer common.
> It's not even supported by many desktops these days. I switched from
> XFCE to openbox when XFCE dropped support for multiple screens.
> 
> --
> Grant


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-11-21 19:26 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  6:25 [gentoo-user] Upgrading from 5.14 to 6.0 version Dale
2022-11-11 10:30 ` Peter Humphrey
2022-11-11 10:35   ` Arve Barsnes
2022-11-11 10:56     ` Wols Lists
2022-11-11 18:12     ` Laurence Perkins
2022-11-11 12:24 ` hitachi303
2022-11-11 19:18   ` Dale
2022-11-11 22:08     ` Dr Rainer Woitok
2022-11-11 14:41 ` Rich Freeman
2022-11-11 19:42   ` Dale
2022-11-11 18:04 ` Laurence Perkins
2022-11-12 12:08 ` ralfconn
2022-11-12 16:00 ` [gentoo-user] " Nikos Chantziaras
2022-11-12 18:22   ` Dale
2022-11-12 18:43     ` Mark Knecht
2022-11-12 19:13     ` Wol
2022-11-12 20:02       ` Nikos Chantziaras
2022-11-12 20:03       ` Mark Knecht
2022-11-12 21:37         ` Dale
2022-11-14 19:57           ` Nikos Chantziaras
2022-11-14 21:05             ` Dale
2022-11-14 21:44               ` Michael
2022-11-14 23:56                 ` Wol
2022-11-15  0:10                 ` Dale
2022-11-15 17:46                   ` Laurence Perkins
2022-11-15  2:36                 ` Grant Edwards
2022-11-14 21:44               ` Mark Knecht
2022-11-12 21:17       ` Rich Freeman
2022-11-21  6:10 ` [gentoo-user] " Dale
2022-11-21 12:20   ` Rich Freeman
2022-11-21 20:52     ` Dale
2022-11-21 16:11   ` [gentoo-user] " Grant Edwards
2022-11-21 16:27     ` Michael
2022-11-21 16:50       ` Grant Edwards
2022-11-21 17:24         ` Michael
2022-11-21 18:12           ` Grant Edwards
2022-11-21 19:26             ` Michael [this message]
2022-11-21 19:37               ` Grant Edwards
2022-11-21 21:30                 ` Frank Steinmetzger
2022-11-21 18:15           ` Laurence Perkins
2022-11-22 19:01             ` Wol
2022-11-21 16:58     ` Mark Knecht
2022-11-21 17:49       ` Grant Edwards
2022-11-21 19:42         ` Mark Knecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1882118.taCxCBeP46@lenovo.localdomain \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox