Re: fvwm and casting from chrome
On Thu, May 28, 2020 at 15:49 (-0500), Peter G wrote: > On 5/28/20 8:00 AM, Jim Diamond wrote: >> On Wed, May 27, 2020 at 21:58 (-0500), Peter G wrote: >>> On 5/27/20 9:37 PM, Jim Diamond wrote: >>> > On Wed, May 27, 2020 at 21:32 (-0500), Peter G wrote: >>> > > On 5/27/20 4:58 PM, Thomas Adam wrote: >>> > > > On Wed, May 27, 2020 at 04:41:08PM -0500, peter g wrote: >>> > > > > Hi Everyone: >>> > > > Hello! >>> > > > > i have a frustrating issue with fvwm and casting from google's >>> > > > > chrome, that >>> > > > > maybe somebody has a workaround for. >>> > > > > Normally, under any other WM i've tried (and also on windows), in >>> > > > > the chrome >>> > > > > browser, choosing "Cast", will pop up a small window that asks the >>> > > > > user what >>> > > > > device to cast to. Unfortunately in fvwm that little window with >>> > > > > those >>> > > > > options does not show up. >>> > > > > I've tried both with my config, but also with a very fvwm config >>> > > > > such as: >>> > > > > key c A CM FvwmConsole >>> > > > > key r A CM Restart >>> > > > > Key u A CM Exec xterm >>> > > > > If anyone has a work around, that would be much appreciated, as >>> > > > > casting, for >>> > > > > better or worse, is very useful to me. >>> > > > Well, if it's a transient window, it will (by default) popup along >>> > > > side the >>> > > > parent window. That said, you can try: >>> > > > BugOpts ExplainWindowPlacement On >>> > > > in your ~/.fvwm2rc file, and monitor stderr to see what FVMM thinks >>> > > > of your >>> > > > missing window. >>> > > Thanks, I've tried that. >>> > > Doesn't show anything (I know that option is working, as I get the debug >>> > > info for other windows). As pointed out in another email, that "cast" >>> > > window >>> > > might indeed be a chrome internal window... what bothers me though, is >>> > > why >>> > > it shows up in other window managers. >>> > I haven't tried another window manager, but for what it's worth, the >>> > cast window does not show up for me in google-chrome. >>> Thank you for checking! >> No trouble! >>> > By the way, are you running these different window managers on the >>> > same Linux distro? Or is it possible you are using fvwm on one Linux, >>> > and other window managers on a different Linux distro? >>> I have done these check on the same machine, with the same installation of >>> chrome (i.e just long into a different WM). >>> A few window managers i checked: icewm, lxde, gnome (ubuntu's 18.04 default >>> desktop), ubuntu's winland desktop thing. All work as expected. >>> BTW, I'm running the latest github version 2 master branch of fvwm. Which >>> are you running? >> I tried this with google-chrome-81.0.4044.113 / fvwm-2.6.6+git on >> Slackware64-14.2 as well as google-chrome-83.0.4103.61 / fvwm-2.6.9 on >> Slackware64-current. >> The 2.6.6+git is probably (memory fails, I installed it in Sept 2017) >> a version from git around when 2.6.6 was the latest and greatest. >> If I get a chance to try another wm on these systems I'll follow-up. > ok, thanks for that. I ran xfce4. When there, chrome did, in fact pop up the little window. So it would seem that somehow fvwm is related; whether it is something fvwm2 is doing or something that it isn't doing (but chrome assumes) is an interesting question. I'm happy to do more similar experiments if that is of any use to anyone who wants to try to track this down. Jim
Re: fvwm and casting from chrome
On Wed, May 27, 2020 at 21:58 (-0500), Peter G wrote: > On 5/27/20 9:37 PM, Jim Diamond wrote: >> On Wed, May 27, 2020 at 21:32 (-0500), Peter G wrote: >>> On 5/27/20 4:58 PM, Thomas Adam wrote: >>> > On Wed, May 27, 2020 at 04:41:08PM -0500, peter g wrote: >>> > > Hi Everyone: >>> > Hello! >>> > > i have a frustrating issue with fvwm and casting from google's chrome, >>> > > that >>> > > maybe somebody has a workaround for. >>> > > Normally, under any other WM i've tried (and also on windows), in the >>> > > chrome >>> > > browser, choosing "Cast", will pop up a small window that asks the user >>> > > what >>> > > device to cast to. Unfortunately in fvwm that little window with those >>> > > options does not show up. >>> > > I've tried both with my config, but also with a very fvwm config such >>> > > as: >>> > > key c A CM FvwmConsole >>> > > key r A CM Restart >>> > > Key u A CM Exec xterm >>> > > If anyone has a work around, that would be much appreciated, as >>> > > casting, for >>> > > better or worse, is very useful to me. >>> > Well, if it's a transient window, it will (by default) popup along side >>> > the >>> > parent window. That said, you can try: >>> > BugOpts ExplainWindowPlacement On >>> > in your ~/.fvwm2rc file, and monitor stderr to see what FVMM thinks of >>> > your >>> > missing window. >>> Thanks, I've tried that. >>> Doesn't show anything (I know that option is working, as I get the debug >>> info for other windows). As pointed out in another email, that "cast" window >>> might indeed be a chrome internal window... what bothers me though, is why >>> it shows up in other window managers. >> I haven't tried another window manager, but for what it's worth, the >> cast window does not show up for me in google-chrome. > Thank you for checking! No trouble! >> By the way, are you running these different window managers on the >> same Linux distro? Or is it possible you are using fvwm on one Linux, >> and other window managers on a different Linux distro? > I have done these check on the same machine, with the same installation of > chrome (i.e just long into a different WM). > A few window managers i checked: icewm, lxde, gnome (ubuntu's 18.04 default > desktop), ubuntu's winland desktop thing. All work as expected. > BTW, I'm running the latest github version 2 master branch of fvwm. Which > are you running? I tried this with google-chrome-81.0.4044.113 / fvwm-2.6.6+git on Slackware64-14.2 as well as google-chrome-83.0.4103.61 / fvwm-2.6.9 on Slackware64-current. The 2.6.6+git is probably (memory fails, I installed it in Sept 2017) a version from git around when 2.6.6 was the latest and greatest. If I get a chance to try another wm on these systems I'll follow-up. Jim
Re: fvwm and casting from chrome
On Wed, May 27, 2020 at 21:32 (-0500), Peter G wrote: > On 5/27/20 4:58 PM, Thomas Adam wrote: >> On Wed, May 27, 2020 at 04:41:08PM -0500, peter g wrote: >>> Hi Everyone: >> Hello! >>> i have a frustrating issue with fvwm and casting from google's chrome, that >>> maybe somebody has a workaround for. >>> Normally, under any other WM i've tried (and also on windows), in the chrome >>> browser, choosing "Cast", will pop up a small window that asks the user what >>> device to cast to. Unfortunately in fvwm that little window with those >>> options does not show up. >>> I've tried both with my config, but also with a very fvwm config such as: >>> key c A CM FvwmConsole >>> key r A CM Restart >>> Key u A CM Exec xterm >>> If anyone has a work around, that would be much appreciated, as casting, for >>> better or worse, is very useful to me. >> Well, if it's a transient window, it will (by default) popup along side the >> parent window. That said, you can try: >> BugOpts ExplainWindowPlacement On >> in your ~/.fvwm2rc file, and monitor stderr to see what FVMM thinks of your >> missing window. > Thanks, I've tried that. > Doesn't show anything (I know that option is working, as I get the debug > info for other windows). As pointed out in another email, that "cast" window > might indeed be a chrome internal window... what bothers me though, is why > it shows up in other window managers. I haven't tried another window manager, but for what it's worth, the cast window does not show up for me in google-chrome. By the way, are you running these different window managers on the same Linux distro? Or is it possible you are using fvwm on one Linux, and other window managers on a different Linux distro? Cheers. Jim
Re: commit messages and developers discussion
On Mon, Oct 31, 2016 at 08:41 (+0100), Tiziano Zito wrote: > Dear all, > as a long time FVWM user I'm lurking on fvwm-workers@fvwm.org since forever. > First of all, thanks to the few devs who are keeping the project up and > running: I am grateful for your engagement and I am happy to see that > development hasn't stalled :-) > Since the move to git and GitHub, which I appreciate a lot as well, push > notifications get posted by GitHub to fvwm-workers@fvwm.org . Since Tiziano brought this up... I seem to get multiple copies of every commit message. (And it isn't because I am multiply subscribed to this list.) Does everyone see multiple copies? If so, can someone tell me why multiple copies of every commit are sent? Thanks.
Re: icon title in 2.6.5 changed to window title
On Thu, 31 May 2012 12:26:34 -0700 Thomas Adam wrote On 31 May 2012 18:11, z...@acadiau.ca wrote: P.S. Yes, I know I can work around this bug with a Style * IconTitle %i line in my config. And this is *precisely* why this can never be the default, due to how icon title assignment works. Sorry, I don't follow what you are saying. Previously (2.6.1 and back for the last 15 or 20 years, as far as I recall) the icon title was the icon title, and now the icon title is (by default) set when the window title is set. You say it can't be done, but changing the default to %i seems possible to me (as with the code I suggested in my OP). Maybe I'm not seeing some dependency somewhere else in the code. If need be, I'll write an FAQ entry about it, but I do not care at all, given you've answered your own question. What was it you had a point over? My point was that the icon title should not default to the window title. These are two separate resources, and have been separate for a long time. It seems like a rather arbitrary change, and since it is not backward compatible it seems like there should be some good reason to change the behaviour. Perhaps you have a good reason, but I don't see it. Cheers. Jim
fvwm-2.6.0 bug(?)
I am running fvwm 2.6.0 on Slackware64 13.1. When it starts up it (apparently) runs fvwm-menu-desktop, which sends out the following complaints: -- WARNING: '/etc/kde/xdg/menus/applications-kmenuedit.menu' does not exist Unknown 'DefaultLayout': 'HASH(0x139b0c0) 0 Merge ARRAY(0x139b228) 0 Merge ARRAY(0x139b2e8) 0 Separator ARRAY(0x139b360) 0 Menuname ARRAY(0x139b408) 0 ' Unknown 'Layout': 'HASH(0x139b4c8) 0 Merge ARRAY(0x139b630) 0 Menuname ARRAY(0x139b6a8) 0 Merge ARRAY(0x13768d8) 0 ' Unknown 'Layout': 'HASH(0x13d9040) 0 Merge ARRAY(0x13d91a8) 0 Filename ARRAY(0x13d9220) 0 Filename ARRAY(0x13dbba8) 0 Separator ARRAY(0x13dbc98) 0 Filename ARRAY(0x13dbd40) 0 Filename ARRAY(0x13dbe30) 0 Filename ARRAY(0x13dbf20) 0 Merge ARRAY(0x13dc058) 0 Separator ARRAY(0x13dc0d0) 0 Menuname ARRAY(0x13dc178) 0 ' DestroyMenu FvwmMenu AddToMenu FvwmMenu KDE Menu Title -- I don't see anything in my configuration which is asking fvwm to call this program. Should I be getting this without asking for it, or am I doing something wrong. (If the latter, my apologies for the noise.) Thanks. Jim
Bug on http://www.fvwm.org/download/ page
Hi, that page says If you find any bugs, you can enter them into the FVWM Bug Tracking System. But the link is broken. Cheers. Jim
