unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Slim & Multi-monitor
Date: Tue, 04 Dec 2018 07:53:56 +0100	[thread overview]
Message-ID: <87r2exhjej.fsf@elephly.net> (raw)
In-Reply-To: <87h8fvyv2l.fsf@gmail.com>


Hi Chris,

> Brett Gilio <brettg@posteo.net> writes:
>
>> I have a dual monitor setup for my workstation I use Guix on. The Slim
>> DM is quite nice for me, and i'd theoretically like to remain with
>> it. However, I am having trouble with the way Slim is treating the
>> dual-monitor display. Instead of treating each monitor as their own
>> "workspace", it is treating both monitors together as a single extended
>> display, which creates an awkward division down the middle of Slim, and
>> displays part of the login field on each monitor display.
>>
>> I checked the documentation for Slim to see if this is written on, and I
>> did not find anything.
>
> I can confirm that this happens for me, also.  I wasn't sure if it was a
> bug or not, so I didn't comment on it, but it certainly seems incorrect.
> Since this affects multiple people using GuixSD, perhaps we should file
> a bug report about it.  Could you do that by emailing bug-guix@gnu.org?

I don’t think Slim supports multiple monitors, so there’s little we can
do without forking it.

Slim also has a couple of other drawbacks (such as no support for input
methods and lack of localisation).  We should change the default to a
different display manager such as gdm or lightdm.

--
Ricardo

      reply	other threads:[~2018-12-04  6:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 17:30 Slim & Multi-monitor Brett Gilio
2018-11-07 17:33 ` Pierre Neidhardt
2018-11-08  7:36 ` Giovanni Biscuolo
2018-12-03  6:37 ` Chris Marusich
2018-12-04  6:53   ` Ricardo Wurmus [this message]

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87r2exhjej.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=cmmarusich@gmail.com \
    --cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).