Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #182440

Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

Show all headers | View raw

On 06/20/2017 02:06 PM, JPlews wrote:
> On 20/06/17 13:14, Richard Owlett wrote:
>> I had understood ARandR would use it automatically. It evidently doesn't.
>
> This is my experience too, including some of the randomness, after
> reboots the DE is setting things, I find Gnome really weak in this area.
>
> The window oddness you describe reminds me of when displays are not in
> the natural order from the hardware, so your at a disadvantage if the
> primary display is not leftmost in many cases.
>
> IMO use arandr-indicator, or put a script onto a global shortcut, it is
> somewhat fiddly but you can use xdotool for a few fix-ups in the screen
> layouts if you want a particular window moving to somewhere and it
> doesn't consistently do it itself, but do consider grepping xrandr
> output to not move things unless the extra display is actually
> connected. pacmd for audio can be nice here too.
>
> AFAIK, but its been a few years, there's no nice method to spawn a
> script on monitor connections, but something like a mouse or usb hub can
> (again checking for connected displays first)
>
> Hope that helps
>
> JP


To clarify:
My OS is Stretch
My DE is MATE
Although I'm using a laptop, it is my primary machine.
Therefore the VGA monitor is *ALWAYS* connected.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

ARandR problems: Bug or opderator? Richard Owlett <rowlett@cloud85.net> - 2017-06-17 15:30 +0200
  Re: ARandR problems: Bug or opderator? Curt <curty@free.fr> - 2017-06-17 22:10 +0200
    Re: ARandR problems: Bug or opderator? Richard Owlett <rowlett@cloud85.net> - 2017-06-18 12:50 +0200
      One problem identified - was [Re: ARandR problems: Bug or opderator?] Richard Owlett <rowlett@cloud85.net> - 2017-06-20 14:20 +0200
        Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] JPlews <jw@plews.org.uk> - 2017-06-20 21:10 +0200
          Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] Richard Owlett <rowlett@cloud85.net> - 2017-06-20 22:30 +0200
            Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] JPlews <jw@plews.org.uk> - 2017-06-20 23:30 +0200
        Re: One problem identified - was [Re: ARandR problems: Bug or opderator?] deloptes <deloptes@gmail.com> - 2017-06-20 21:50 +0200
          Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] Richard Owlett <rowlett@cloud85.net> - 2017-06-20 22:40 +0200
        Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] Felix Miata <mrmazda@earthlink.net> - 2017-06-21 00:20 +0200
        Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] Jimmy Johnson <field.engineer@gmail.com> - 2017-06-21 02:30 +0200
          Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] Richard Owlett <rowlett@cloud85.net> - 2017-06-21 15:20 +0200
        Workaround {Re: One problem identified - was [Re: ARandR problems:  Bug or opderator?]} Richard Owlett <rowlett@cloud85.net> - 2017-06-23 13:30 +0200
          Re: Workaround {Re: One problem identified - was [Re: ARandR  problems: Bug or opderator?]} Felix Miata <mrmazda@earthlink.net> - 2017-06-23 21:50 +0200
            Re: Workaround {Re: One problem identified - was [Re: ARandR  problems: Bug or opderator?]} Richard Owlett <rowlett@cloud85.net> - 2017-06-24 13:50 +0200
              Re: Workaround {Re: One problem identified - was [Re: ARandR  problems: Bug or opderator?]} David Wright <deblis@lionunicorn.co.uk> - 2017-06-24 20:10 +0200

csiph-web