[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmonad
Subject:    Re: [xmonad] managehook: ... dual-head & screen sticking clients
From:       mito <info () mito-space ! com>
Date:       2022-01-17 18:12:55
Message-ID: 5945c8a8-d928-e626-6733-c57fd1633fde () mito-space ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Am 17.01.22 um 18:20 schrieb mito:
> Am 17.01.22 um 18:14 schrieb Brandon Allbery:
> > On Mon, Jan 17, 2022 at 12:09 PM mito <info@mito-space.com> wrote:
> > > Now (in dual-head), when switching workspaces, only one monitor/screen
> > > switches. So it would be of help *all screens* switch, too, and hence
> > > the complete workspace's 'view port'. – IMO "import qualified
> > > Graphics.X11.Xinerama" should do this, and that module treats both
> > > monitors as one in combination.
> > Importing a module in Haskell only makes names available; it does not
> > and can not perform any actions. Additionally, that is a low level
> > module which exposes the X11-layer multiscreen support, not xmonad's.
> > 
> > If you really want both screens to switch at the same time, you might
> > be interested in
> > https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Actions-DynamicWorkspaceGroups.html. \
> >  
> Thanks, will look into it! ^^
> 
Done . . .
Looks quite interesting; however Idk if this would solve my issue (or I 
don't get its purpose exactly). I don't intend to use complete "sets of 
workspaces" (like topics?), rather switching both screens at once when 
changing workspaces (to avoid client-screen swapping).

Anyway,

addRawWSGroup :: WSGroupId 
<https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Actions-DynamicWorkspaceGroups.html#t:WSGroupId> \
                
-> [(ScreenId 
<https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Config-Prime.html#t:ScreenId>, \
 WorkspaceId 
<https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Config-Prime.html#t:WorkspaceId>)] \
                
-> X 
<https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Config-Prime.html#t:X> \
 ()

has drawn my attention . . .

> > > As mentioned earlier, it works in Trinity (a.k.a. TDE=KDE3.5), so am I
> > > missing something in KDE5?
> > Are you talking about Trinity's window manager, or xmonad? xmonad (and
> > dwm) divide workspaces up between monitors; most window managers treat
> > a workspace as spanning all monitors.
> > 
> Sorry – to be more precisely: Xmonad as the WM (replacing kwin_x11) in 
> Trinity.
And yes, since Plasma wanted to re-invent the virtual desktop, dual-head 
screens are now seen as two separate ones, which can be individually 
customized with different wallpapers and bling such as "Activities".


[Attachment #5 (text/html)]

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Am 17.01.22 um 18:20 schrieb mito:<br>
    <blockquote type="cite"
      cite="mid:5a910e72-786f-962b-df1e-ae7b57bcd82d@mito-space.com">Am
      17.01.22 um 18:14 schrieb Brandon Allbery:
      <br>
      <blockquote type="cite">On Mon, Jan 17, 2022 at 12:09 PM mito
        <a class="moz-txt-link-rfc2396E" \
href="mailto:info@mito-space.com">&lt;info@mito-space.com&gt;</a> wrote:  <br>
        <blockquote type="cite">Now (in dual-head), when switching
          workspaces, only one monitor/screen
          <br>
          switches. So it would be of help *all screens* switch, too,
          and hence
          <br>
          the complete workspace's 'view port'. – IMO "import qualified
          <br>
          Graphics.X11.Xinerama" should do this, and that module treats
          both
          <br>
          monitors as one in combination.
          <br>
        </blockquote>
        Importing a module in Haskell only makes names available; it
        does not
        <br>
        and can not perform any actions. Additionally, that is a low
        level
        <br>
        module which exposes the X11-layer multiscreen support, not
        xmonad's.
        <br>
        <br>
        If you really want both screens to switch at the same time, you
        might
        <br>
        be interested in
        <br>
<a class="moz-txt-link-freetext" \
href="https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Actions-Dy \
namicWorkspaceGroups.html">https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Actions-DynamicWorkspaceGroups.html</a>.
  <br>
      </blockquote>
      Thanks, will look into it! ^^
      <br>
      <br>
    </blockquote>
    Done . . .<br>
    Looks quite interesting; however Idk if this would solve my issue
    (or I don't get its purpose exactly). I don't intend to use complete
    "sets of workspaces" (like topics?), rather switching both screens
    at once when changing workspaces (to avoid client-screen swapping).<br>
    <br>
    Anyway,<br>
    <br>
    <a id="v:addRawWSGroup" class="def">addRawWSGroup</a> :: <a
href="https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Actions-DynamicWorkspaceGroups.html#t:WSGroupId"
  title="XMonad.Actions.DynamicWorkspaceGroups">WSGroupId</a> -&gt;
    [(<a
href="https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Config-Prime.html#t:ScreenId"
  title="XMonad.Config.Prime">ScreenId</a>, <a
href="https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Config-Prime.html#t:WorkspaceId"
  title="XMonad.Config.Prime">WorkspaceId</a>)] -&gt; <a
href="https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Config-Prime.html#t:X"
  title="XMonad.Config.Prime">X</a> ()<br>
    <br>
    has drawn my attention . . .<br>
    <br>
    <blockquote type="cite"
      cite="mid:5a910e72-786f-962b-df1e-ae7b57bcd82d@mito-space.com">
      <blockquote type="cite">
        <blockquote type="cite">As mentioned earlier, it works in
          Trinity (a.k.a. TDE=KDE3.5), so am I
          <br>
          missing something in KDE5?
          <br>
        </blockquote>
        Are you talking about Trinity's window manager, or xmonad?
        xmonad (and
        <br>
        dwm) divide workspaces up between monitors; most window managers
        treat
        <br>
        a workspace as spanning all monitors.
        <br>
        <br>
      </blockquote>
      Sorry – to be more precisely: Xmonad as the WM (replacing
      kwin_x11) in Trinity.
      <br>
    </blockquote>
    And yes, since Plasma wanted to re-invent the virtual desktop,
    dual-head screens are now seen as two separate ones, which can be
    individually customized with different wallpapers and bling such as
    "Activities".<br>
  </body>
</html>


[Attachment #6 (text/plain)]

_______________________________________________
xmonad mailing list
xmonad@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic