[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34516: Multi-monitor frame sets
From: |
Robert Pluim |
Subject: |
bug#34516: Multi-monitor frame sets |
Date: |
Tue, 19 Feb 2019 10:17:20 +0100 |
Juri Linkov <juri@linkov.net> writes:
>> Juri Linkov <juri@linkov.net> writes:
>>
>>> Shouldn't frame.el provide a command like make-frame-on-display,
>>> but to make a frame on the specified monitor instead of display?
>>>
>>> Isn't the following patch the right way to do this?
>>> (It also adds completion for the existing command):
>>>
>>
>> I donʼt mind it, but it won't work on macOS, since thereʼs no 'name
>> entries in 'display-monitor-attributes-list' (and adding them looks
>> non-trivial, unless we go for 'Monitor-1', Monitor-2' etc.)
>
> Are there other NS-specific attributes that could provide
> a clear reference to a specific monitor? Maybe ‘geometry’
> could be used to deduce a relative arrangement of monitors?
I guess it could. Or we could fake up a monitor name on those systems
where ns_screen_name doesnʼt work.
Robert
- bug#34516: Multi-monitor frame sets, Juri Linkov, 2019/02/17
- bug#34516: Multi-monitor frame sets, Robert Pluim, 2019/02/18
- bug#34516: Multi-monitor frame sets, Juri Linkov, 2019/02/18
- bug#34516: Multi-monitor frame sets,
Robert Pluim <=
- bug#34516: Multi-monitor frame sets, Juri Linkov, 2019/02/23
- bug#34516: Multi-monitor frame sets, Robert Pluim, 2019/02/24
- bug#34516: Multi-monitor frame sets, Juri Linkov, 2019/02/24
- bug#34516: Multi-monitor frame sets, Andy Moreton, 2019/02/24
- bug#34516: Multi-monitor frame sets, Juri Linkov, 2019/02/25
bug#34516: Multi-monitor frame sets, Eli Zaretskii, 2019/02/18