Re: FVWM: fvwm3?

2024-02-03 Thread Mandar Mitra
Lucio Chiappetti wrote (Sat, Feb 03, 2024 at 01:53:29PM +0100):
> I hope to be able to go on with Xorg until I live.

Amen! :-)



Re: FVWM: FVWM3: 2 monitors with different geometries?

2023-12-23 Thread Mandar Mitra
Jaimos Skriletz wrote (Fri, Dec 22, 2023 at 12:45:34PM -0700):
> Yes, you can have different resolutions. I think you may run into
> issues using DesktopConfiguration shared with different resolutions,
> but DesktopConfiguration per-monitor will work just fine.

FVWM3 installation went without a hitch (I'm on Manjaro and just installed the 
AUR package). My existing .fvwm2rc also works without any problems. 

The default config bundled in the package uses "DesktopConfiguration global". 
Could someone please point me to / share an example config file that uses 
"DesktopConfiguration per-monitor"? I couldn't find a starting point for this 
on the forums / wiki. 

I'd like to create a Desktop-default (laptop's own monitor, always available) 
and a Desktop-external-monitor, which can be used when the external monitor is 
plugged in. Afterwards, I think I can use move-to-desk, starts-on-desk and 
similar functions to complete the rest of my setup.

Also, I'm sure there are more elegant ways to achieve this, but I suppose 
restarting fvwm after plugging in the external monitor will take care of 
detecting it, activating per-monitor DesktopConfiguration, and setting up the 
second Desktop on the external monitor?

Thanks,
Mandar.



Re: FVWM: FVWM3: 2 monitors with different geometries?

2023-12-22 Thread Mandar Mitra
Jaimos Skriletz wrote (Fri, Dec 22, 2023 at 12:45:34PM -0700):
> On Fri, Dec 22, 2023 at 9:42 AM Mandar Mitra  wrote:
> >
> >
> > Browsing around FVWM3's git repo, and looking at 
> > https://github.com/fvwmorg/fvwm3/blob/main/dev-docs/NEW-COMMANDS.md#hierarchy-and-specification
> >  in particular, it seems like fvwm3 will allow me to have independent 
> > desktops with appropriate geometries on Screen1 and Screen2.
> >
> 
> This is a bit better page to describe how to migrate from fvwm2 to fvwm3:
> 
> https://github.com/fvwmorg/fvwm3/discussions/878

...

Thank you so much for all the detailed answers! I will try to install fvwm3 in 
the next few days. If I have anything to add to the above, I will definitely 
report.

Thanks again,
-mandar



FVWM: FVWM3: 2 monitors with different geometries?

2023-12-22 Thread Mandar Mitra
I have a laptop with a 1366x768 screen (say Screen1), and a 1920x1080 monitor 
(say Screen2) connected to it (via HDMI or VGA).

Browsing around FVWM3's git repo, and looking at 
https://github.com/fvwmorg/fvwm3/blob/main/dev-docs/NEW-COMMANDS.md#hierarchy-and-specification
 in particular, it seems like fvwm3 will allow me to have independent desktops 
with appropriate geometries on Screen1 and Screen2.

I haven't been able to figure out how to do this with FVWM2, so if some kind 
soul could please confirm that this is possible with FVWM3, I'll take the 
plunge and migrate.

Somewhat related questions:

1. The NEW-COMMANDS.md page states "Desktops are linear in their arrangement. 
There is no concept of pages within a desktop (as there is with FVWM2)." Is 
that information correct? Or is this something left over from early design 
discussions?

2. The picture on the NEW-COMMANDS.md page shows that the Desktops on Screen1 
have different geometries. Is that really possible? Or shouldn't I take that 
"literally"?

Many thanks for any suggestions,
Mandar.



Re: FVWM: emulating mouse button 2 on HP touchpad

2023-05-15 Thread Mandar Mitra
Lucio Chiappetti wrote (Sun, May 14, 2023 at 11:11:41PM +0200):
> This has nothing to do with xdotool. If in ANOTHER terminal I do
> 
> sleep 5; xdotool click 2
> 
> and then qjuickly enough move the mouse to an xterm, the MB1 selection *is*
> pasted. But of course this is a bit clumsy.
> 
> So the problem is an incompatibility between xterm and fvwm syntethic events
> (or a syntax problem with PointerKey ?)

I don't understand this very well, so I have a related question: are all events 
generated by xdotool synthetic events? Does this mean that xdotool will not 
work for some modern, security-conscious applications?

Thanks,
Mandar.



Re: FVWM: emulating mouse button 2 on HP touchpad

2023-05-15 Thread Mandar Mitra
Lucio Chiappetti wrote (Sat, May 13, 2023 at 11:44:36PM +0200):
> I am since ages a keen fvwm user (2.6.8 bundled with ubuntu), mostly on a
> desktop PC, with a personal configuration described in
> http://sax.iasf-milano.inaf.it/~lucio/WWW/Opinions/window.html.
> 
> In particular (independently of fvwm ?) I am used to do quick copy-and-paste
> of text selecting it with mouse button 1 (MB1) and pasting with mouse button
> 2 (MB2). Or shift-MB1 and shift-MB2 in my favourite editor (The Hessling
> Editor), due to a peculiarity of the editor.
> 
> Now I've got a new HP Probook laptop which has a touchpad without buttons.
> Apparently tapping near the bottom left and bottom right corners of the
> touchpad works as MB1 and MB3 ... but there is no MB2.

You mention your laptop is new, so it is likely that the touchpad supports 
multitouch and other goodies. 

It should be possible to configure the touchpad itself to send, for example, 
MB2 on a two finger tap. The exact details would depend on the driver Ubuntu 
uses for the touchpad. I believe common options are the Synaptics driver and 
libinput (probably the correct, "modern" option).

I don't clearly understand all details, but here's some output I get on my 
laptop that might give you an idea about what to expect.

---
latitude3490$ xinput
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ DELL0839:00 044E:120A Touchpadid=12   [slave  pointer  (2)]
⎜   ↳ AlpsPS/2 ALPS GlidePoint  id=18   [slave  pointer  (2)]
⎜   ↳ DELL0839:00 044E:120A Mouse   id=11   [slave  pointer  (2)]
---

And then, for more detail:

---
xinput list --long 12 # 12 is the device id for the touchpad

DELL0839:00 044E:120A Touchpad  id=12   [slave  pointer  (2)]
Reporting 7 classes:
Class originated from: 12. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right" 
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz 
Wheel Right"
...
---
  

HTH.



Re: FVWM: Alt-Tab and WindowList

2021-02-16 Thread Mandar Mitra
> Maybe you could try to figure out some reproducable instructions
> to make that happen (preferrably with a minimal config). 

Yes, let me try this.

> Have you tried using multiple pages?  For example, I use six (2x3)

I started with 2x3 and I'm now at 2x4. The clutter usually happens because I 
have, on one page: a terminal, an Emacs window for writing LaTeX, the output in 
a pdf viewer, and a bunch of other pdf files that constitute source material 
for my slides / notes.

Thanks for many useful tips. I'm definitely going to include some of these in 
my .fvwm2rc.

> > Idle curiosity: do you use ipe too? Nice to discover such
> > commonalities in an unrelated list.
> 
> No, sorry that I fooled you; i just instlled it to see what it's
> doing.

Wow, thanks for taking so much trouble! Thanks again for your time and all the 
suggestions.

-mandar



Re: FVWM: Alt-Tab and WindowList

2021-02-15 Thread Mandar Mitra
Mark Nejedlo wrote (Mon, Feb 15, 2021 at 10:15:41PM -0600):
> On Mon, Feb 15, 2021, at 9:55 AM, Mandar Mitra wrote:
> > The alternative you suggested won't help me, because I was looking to 
> > address precisely the situation when I have a page "cluttered with many 
> > windows, all atop each other".
> 
> I'm going to take a low probability shot in the dark.
> 
> Are you using ClickToFocus, or are you using 
> MouseFocus(default)/FocusFollowsMouse/SloppyFocus?  

The only general focus-related setting that I could find in my .fvwm2rc is:

Style * MouseFocusClickRaises

There are a couple others related to specific programs (e.g., TeamViewer).


> If it is NOT ClickToFocus, are you crossing the "clutter"
> transitioning the mouse between windows? Each window you cross will
> briefly have focus, so it will jump to the top of the list and
> unexpectedly push your "active" windows down.

I understand this was Dominik's suggestion too, but I'm reasonably sure that is 
not the case. On this particular laptop with only a 1366x768 screen, I have 
most windows (esp. pdf viewers) maximised in "cluttered" mode.

Many thanks to all of you for your suggestions,
-mandar.



Re: FVWM: Alt-Tab and WindowList

2021-02-15 Thread Mandar Mitra
Dominik Vogt wrote (Sun, Feb 14, 2021 at 12:05:26PM +0100):
> Try running just
> 
>   WindowList (currentpage)
> 
> from FvwmConsole and see if that works as expected.
> 
> The ordering of that list entirely depends on the order in which
> windows are focused.  If that results in a weird ordering, then
> something messes with window focus.  In that case, try if this
> helps:
> 
>   destroyfunc EWMHActivateWindowFunc
>   addtofunc EWMHActivateWindowFunc
>   + I echo Ignoring EWMHActivateWindowFunc $[w.id] $[w.name]
> 
> And watch the console output for the debug messages.

I have no idea what I'm doing wrong, but something does seem to be messing with 
window focus. For a while, the list is nicely maintained in MRU order, then 
suddenly, a window that I haven't focused for a while jumps up to the middle of 
the list. Sometimes its Emacs, sometimes its zathura (a pdf viewer). I copy 
pasted the destroyfunc and addtofunc that you provided above into FvwmConsole, 
but neither FvwmConsole itself, nor .xsession-errors had anything to report 
while the list was being re-ordered, apparently randomly.

The alternative you suggested won't help me, because I was looking to address 
precisely the situation when I have a page "cluttered with many windows, all 
atop each other".

For now, I've just disabled SelectOnRelease, and use the Fvwm assigned number 
to quickly jump to the window I want. This saves me from having to keep typing 
Tab to get where I want in the list. I suppose it'll just take a little while 
for muscle memory to reset itself to this usage pattern.

Thanks for all your suggestions!

Idle curiosity: do you use ipe too? Nice to discover such commonalities in an 
unrelated list.

-mandar



Re: FVWM: Trouble with transient windows

2021-02-13 Thread Mandar Mitra
Thomas Adam wrote (Sat, Feb 13, 2021 at 03:38:16PM +):
> On Sat, Feb 13, 2021 at 08:22:16PM +0530, Mandar Mitra wrote:
> > I would like the transient windows to not affect focus at all. I looked at 
> > the manual page for the FPGrabFocusTransient, FPGrabFocusTransient,  
> > FPReleaseFocusTransient, and similar options, but I couldn't figure out 
> > what I need to do to get the behaviour I want.
> > 
> > Is this something that I can take care of within fvwm? Or should I ask the 
> > ipe developer about this?
> 
> I suppose you're referring to something like this:
> 
>   Style * RaiseTransient
>   Style * LowerTransient
>   Style * StackTransientParent

Probably not (as far as I can tell from the manpage).

At the moment, the only thing that I want is that transients should never get 
focus. Is that something I can control from fvwm, or does that need to be fixed 
in the respective applications?

If that's not possible, I would like a transient to release focus when it goes 
away. I thought FPReleaseFocus, FPReleaseFocusTransient and 
FPOverrideReleaseFocus controlled this behaviour, but I don't understand 
exactly how. I have

Style * MouseFocusClickRaises, GrabFocusTransientOff, !FPGrabFocusTransient, 
FPReleaseFocusTransient, FPOverrideReleaseFocus

but that's not giving me what I want.

-mandar



FVWM: Alt-Tab and WindowList

2021-02-13 Thread Mandar Mitra
I have Alt-Tab bound as follows:

Key Tab A M WindowList (CurrentPage) 
CurrentAtEnd,IconifiedAtEnd,...,SelectOnRelease Alt_L

I'd like windows to be listed in most recently used order, and there are a 
number of fvwm related Web pages that state that is what "normally" happens, 
but what I'm observing is the following.

As long as I'm switching back and forth between Window A and Window B, things 
work well. I also have some other windows (all pdf viewers displaying different 
files) on the same page. If I take a look at one of them, I would expect A, B 
and the focused pdf viewer window to occupy the top 3 slots, but that's not 
what happens. Either A or B is positioned way down in the list.

I thought CurrentAtEnd might be messing up fvwm's sorting order, but this 
happens even without that option, and I can't make sense of the order in which 
windows are listed.

Can anyone offer any insights / workarounds please? Many thanks, as always!

-mandar



FVWM: Trouble with transient windows

2021-02-13 Thread Mandar Mitra
Hi,

I suppose I'm having trouble correctly understanding the options for transient 
windows. Here's the scenario in which I'd like fvwm to behave differently.

I have 3 windows on a page: emacs, a pdf viewer, and ipe (for drawing diagrams).

Ipe sometimes pops up a little window (only borders, no titlebar or buttons) 
that says "Waiting for external editor" (meaning emacs), and grabs focus.

I have to manually focus emacs before I can type anything. When I quit emacs, 
the above window goes away. Its place is taken by another "Compiling..." type 
window -- again, only borders, no titlebar, and this grabs focus for its brief 
lifetime. When it goes away (almost immediately), none of my windows has focus.

I would like the transient windows to not affect focus at all. I looked at the 
manual page for the FPGrabFocusTransient, FPGrabFocusTransient,  
FPReleaseFocusTransient, and similar options, but I couldn't figure out what I 
need to do to get the behaviour I want.

Is this something that I can take care of within fvwm? Or should I ask the ipe 
developer about this?

I'm using 2.6.7-3. Many thanks for any pointers!

-mandar



Re: FVWM: FvwmForm replaces FvwmPrompt (fvwm 2.0.41)

2020-08-29 Thread Mandar Mitra
Since this thread has gotten quite chatty:

Thomas Adam wrote (Thu, Aug 27, 2020 at 04:02:07PM +0100):
> I did reply back to him -- he wishes us all well, and is delighted that fvwm
> is still continuing.

I can't help wondering aloud what Drew Moseley uses now.

I used to be a twm user at that time, moved to tvtwm, and finally to fvwm 
around the turn of the century :-) I think, when the earliest versions of 
StarOffice were released for GNU/Linux users. Under tvtwm, the cursor wouldn't 
show up in the StarOffice window.

-mandar



Re: FVWM: Zoom whiteboard and fvwm

2020-08-07 Thread Mandar Mitra
Dov Grobgeld wrote (Fri, Aug 07, 2020 at 07:02:34PM +0300):
> I can confirm that the Whiteboard indeed works now. Thanks! But, I still
> don't get the floating toolbar unless I first run the whiteboard and then
> switch the sharing to another window.

You mean the one with various options for the whiteboard cursor: type of line, 
text, colour selection, etc.? I get that without any problems, so don't know 
what might be wrong.

I suppose I'm superstitious, but if you tinker around with it until you get 
frustrated, give up, and revisit after some days/weeks, these things sometimes 
fix themselves :).

Good luck!



Re: FVWM: Zoom whiteboard and fvwm

2020-08-07 Thread Mandar Mitra
Hmmm, I'm not sure what has changed, but the instructions I had written about 
earlier (from https://forum.manjaro.org/t/zoom-whiteboard-does-not-work/131178) 
seem to be working now. Specifically:

1. Start Zoom.
2. Run "xcompmgr -c -l0 -t0 -r0 -o.00" in a terminal.
3. Start the whiteboard. I can now draw, change colour, etc.

As suggested in the Manjaro forum page, I'm thinking of putting this in my 
.xsession now.

GI, Dov, perhaps you could try this to see if it helps.



FVWM: Zoom whiteboard and fvwm

2020-07-06 Thread Mandar Mitra
Like many other people, I have had to start using Zoom. I couldn't get the 
whiteboard to work, so I (blindly) followed the tips given here:

https://forum.manjaro.org/t/zoom-whiteboard-does-not-work/131178

Now the whiteboard works partially: text and a few other annotations work, but 
general drawing tools do not. On a hunch, I logged in using the default Linux 
Mint Mate desktop manager, and things seem to work fine.

If you're running fvwm and using Zoom, can you please check if you can 
reproduce this problem?

Many thanks for your help!
-mandar.



FVWM: left and right control keys behaving differently

2020-06-22 Thread Mandar Mitra
I'm running fvwm 2.6.7-3 on Linux Mint 19.2, and have the 
following in my .fvwm2rc for scrolling with the keyboard:

Key LeftA   CM  Scroll -100 0
Key Right   A   CM  Scroll +100 +0
Key DownA   CM  Scroll +0   +100
Key Up  A   CM  Scroll +0   -100
Key LeftA   CS  Scroll -100 0
Key Right   A   CS  Scroll +100 +0
Key Up  A   CS  Scroll +0   -100
Key DownA   CS  Scroll +0   +100

Strangely, Left Control + either Left or Right Alt + either 
Left or Right Shift works as expected with the Left, Right, 
and Up arrow keys, but does not work with the Down key!

Right Control + Right Alt has the same problem (works with 
Left, Right, and Up, but not Down).

Right Control + Left Alt or Right Control + Shift (either)
also works as expected.

Can someone please suggest where I should start trying to
figure this out?

Thanks!
-mandar.

---

Output of xev from 4 button presses given below:

KeyPress event, serial 36, synthetic NO, window 0x661,
root 0x154, subw 0x662, time 278988216, (26,38), root:(114,182),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 36, synthetic NO, window 0x661,
root 0x154, subw 0x662, time 278988811, (26,38), root:(114,182),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 36, synthetic NO, window 0x661,
root 0x154, subw 0x662, time 278989234, (26,38), root:(114,182),
state 0x0, keycode 108 (keysym 0xffea, Alt_R), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 36, synthetic NO, window 0x661,
root 0x154, subw 0x662, time 278989667, (26,38), root:(114,182),
state 0x0, keycode 105 (keysym 0xffe4, Control_R), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False



Re: FVWM: appearance

2019-01-03 Thread Mandar Mitra
Oleg Tyurin wrote (Thu, Jan 03, 2019 at 12:19:53AM +0400):
> Hi. Please help me understand how to configure application appearance 
> properly.
> After fresh install of FVWM2 I had an appearance according to screenshot1. 
> Next, probably after install of something an appearance had 
> been changed according to screenshot2.
> How can I configure this appearance back to screenshot1?
> I use Fedora 25, FVWM2 without Gnome3.
> I would appreciate any help. Thanks!

Your icon theme seems to have changed / been updated. This is almost certainly 
a Gnome / GTK thing, not related to fvwm (as other people have already pointed 
out). 

Random guess: your file-manager used gtk2 themes earlier, and uses gtk3 themes 
now.

Non-fvwm related content:

I haven't used Fedora in a very long time, but once upon a time, rpm -qa --last 
would give you a list of packages in most-recently-installed/updated-first 
order. That should give you some hint about what might have changed. 

If you think it might be useful, we could discuss this off-list.

-mandar