Le 13/04/2023 à 21:25, Quentin Barnes a écrit :
On Tue, Apr 11, 2023 at 11:14:48PM +0200, Maxime Soulé wrote:
[...]
for example. In this case, we fall into the case where Xrandr is not used,
so the layout defaults to root coordinates, so always one monitor.
This brought up a question
Le 10/04/2023 à 18:16, Quentin Barnes a écrit :
On Mon, Apr 10, 2023 at 12:31:49PM +0200, Maxime Soulé wrote:
Le 08/04/2023 à 22:31, Quentin Barnes a écrit :
On Sat, Apr 08, 2023 at 07:09:54PM +0200, Maxime Soulé wrote:
[...]
Another thing that comes in mind: don't forget that these new
Le 10/04/2023 à 02:10, Stefan Monnier a écrit :
I just tested using virtualbox and the following setup:
Screen 0: minimum 64 x 64, current 1440 x 600, maximum 32766 x 32766
VGA-0 connected 800x600+640+0 0mm x 0mm
800x600 60.00*+ 60.00*
VGA-1 connected primary 640x480+0+60 0mm x 0mm
Le 08/04/2023 à 22:31, Quentin Barnes a écrit :
On Sat, Apr 08, 2023 at 07:09:54PM +0200, Maxime Soulé wrote:
Le 08/04/2023 à 18:03, Quentin Barnes a écrit :
[...]
I created a commit with my changes for comment here:
https://github.com/qbarnes/ctwm-mirror/commit
Le 08/04/2023 à 18:51, Stefan Monnier a écrit :
I have two screens with the following layout:
++
||
+---+|
| ||
| ||
| ||
+---+|
Le 08/04/2023 à 19:28, Maxime Soulé a écrit :
Le 08/04/2023 à 18:51, Stefan Monnier a écrit :
[snip]
cat < layout.txt
0:10x40+20+0
1:20x10+0+10
EOF
./layout.pl layout.txt 5x5+22+12
then typing f+Return for full.
e+Return, sorry, as I forgot f.zoom is the vertical zoom.
++
Max.
[snip]
Le 08/04/2023 à 18:51, Stefan Monnier a écrit :
I have two screens with the following layout:
++
||
+---+|
| ||
| ||
| ||
+---+|
Le 08/04/2023 à 18:03, Quentin Barnes a écrit :
I'm happy to see the recent ctwm changes with xrandr support!
To take better advantage of those changes, I'd like some info about
the monitors to be available when processing my ".ctwmrc" file.
I tried hacking what I could via esyscmd()s that
The f.dynmenu call was wrong, sorry:
f.dynmenu """
cat <
Hi,
After dynamic menus, I propose you a new f.label function.
It works like f.title, but is always drawn like an non-selected usual
menu item.
It could allow to easily emulate some basic dialog boxes like this one:
Menu "reboot"
{
Hi,
After dynamic menus, I propose you a new f.label function.
It works like f.title, but is always drawn like an non-selected usual
menu item.
It could allow to easily emulate some basic dialog boxes like this one:
Menu "reboot"
{
"Reboot" f.title
"Do you really want
tome/ctwm-mirror/commit/e04ca3c004f450d0eae2c92b9ac40598d1f3b717
++
Max.
Le 12/02/2023 à 23:34, Maxime Soulé a écrit :
Hi,
I just implemented a new f.dynmenu function.
The doc says:
f.dynmenu |string|
This function invokes a menu created dynamically by the execution
of the argument |str
It seems the message formatting has been altered.
See the doc here:
https://github.com/maxatome/ctwm-mirror/commit/8d7f5d43ed0c1a21313c0e36bfc35d81410a796b#diff-026da8e81158e5ab5e436f732837290bf316912d36359ece9ec138ac29da5bd5R2526
++
Max.
Le 12/02/2023 à 23:34, Maxime Soulé a écrit :
Hi
Hi,
I just implemented a new f.dynmenu function.
The doc says:
f.dynmenu |string|
This function invokes a menu created dynamically by the execution of
the argument |string| passed to |/bin/sh|. On stdout of this
execution, the definition of one or several menu items is expected:
Hi,
Le 15/12/2022 à 04:48, Matthew D. Fuller a écrit :
Only a year or two later than vaguely planned, let's test out a
release beta. With a little luck, we can promote it by New Years...
https://www.ctwm.org/tmp/ctwm-4.1.0-beta.20221214.tar.xz
SHA256 (ctwm-4.1.0-beta.20221214.tar.xz) =
Hi,
Le 16/07/2021 à 03:05, Matthew D. Fuller a écrit :
[snip]
So, I propose that we deorbit it.
Yes, please! Burn it! :)
So, who wants to speak up in favor of VirtualScreens? Or against
working up a release?
As I already said on this list 3 years ago [1], I don't think anyone
uses this
Hi,
I take advantage of your message to remind the list about 2 small
patches that does not seem to be integrated:
https://github.com/maxatome/ctwm-mirror/commit/6f0f08ca4aea429424a3b3abf455a84c4022a778
(Matthew told us on 12th, July 2020 it is committed, but I don't see it
in master
Hi, just to not forgot... :)
https://github.com/maxatome/ctwm-mirror/commit/ee70936830720992ba63cd29ef3220331c663e95
++
Max.
On 12/07/2020 15:07, Maxime Soulé wrote:
Hi,
On 12/07/2020 00:31, Matthew D. Fuller wrote:
On Thu, Jul 09, 2020 at 06:33:05PM +0200 I heard the voice of
Maxime
Hi,
On 12/07/2020 00:31, Matthew D. Fuller wrote:
On Thu, Jul 09, 2020 at 06:33:05PM +0200 I heard the voice of
Maxime Soulé, and lo! it spake thus:
[snip]
It is weird (but probably historic?) that frame_bw and frame_bw3D
fields have the same meaning for the user (the border width, but one
Hi,
When 3D borders are disabled, squeezing a window produces a little shift
on x by the border width, and the width of the title grows by 2 × the
border width. Yes, it is a little annoying :)
The fix:
https://github.com/maxatome/ctwm-mirror/commit/6f0f08ca4aea429424a3b3abf455a84c4022a778
Hi,
It is probably due to the font used in title.
The matched font is not the same between the 2 versions of your system,
or perhaps it changed a little.
Regards,
Max.
On 06/07/2020 20:16, Aaron Sloman wrote:
I recently screwed up my stonebook mini laptop running fedora 31 while
trying
Hi,
In "Twm Keys" menu, modifiers are not correctly displayed
https://github.com/maxatome/ctwm-mirror/commit/3327c2a8bad4550f54a25cf852aca3dcb9d977b8
fixes them.
+ it seems "make indent" did not run for otp.c after last commit:
Hi Stefan,
On 17/10/2019 15:59, Stefan Monnier wrote:
The reason is the presence of at least one XProperty set only by fvwm,
either _NET_FRAME_EXTENTS or
_KDE_NET_WM_FRAME_STRUT:
Do I understand right that it's not necessary to set
_KDE_NET_WM_FRAME_STRUT if we set _NET_FRAME_EXTENTS?
You
Hi,
I don't know whether you encounter this problem or not, but in my case
(Linux or FreeBSD, with ctwm and without any session manager nor
desktop), the field autocomplete feature of firefox is very annoying as
the drop-down menu of possible completions appears just over the field
itself.
Hi Matthew,
Le 14/10/2018 à 01:51, Matthew D. Fuller a écrit :
Give it a whirl!
Here's a thing we might consider; the little window we show with
dimensions or locations for resize/moving windows. Historically,
there are 2 locations for it; the default is top-left of the screen,
or
Le 03.04.2018 à 16:38, Stefan Monnier a écrit :
Along the same lines, a window that's in screen 0 could only belong to
workspaces of screen 0 and not to workspaces of other screens (so
there's never a situation where you might need to display a given window
at two different places at the same
Le 01.04.2018 à 01:11, Stefan Monnier a écrit :
Check the code, removing VirtualScreens handling would over-simplify
the code.
I hope it would only simplify it, rather than over-simplify it ;-)
Did'nt know the oversimplify verb :) good catch! Anyway, you understood me.
The way
Hi Stefan,
Le 30.03.2018 à 18:54, Stefan Monnier a écrit :
Could add an option to automatically provide the VirtualScreens thingy
based on the xrandr monitor information?
It wouldn't fix those quirks, clearly, but it might encourage people to
use VirtualScreens and in turn to try and fix them.
Hi all,
Episode V:
* f.occupy window now uses layout (to stay visible);
* If CenterFeedbackWindow, feedback window is centered in first monitor;
* When XrandR is in use, some geometries can optionally be relative to
a monitor, using geometries like "HDMI1:800x600-0+0". "HDMI1" name is
28 matches
Mail list logo
