Re: FVWM: A question on Actions in FvwmButtons
Hi, Am Do den 25. Jan 2024 um 13:48 schrieb João Oliveira: > I am using FVWM2 with a button that launches Firefox, but the window > opens somewhere on the screen and I usually have to move it to a > "better" place. I solved that by a style: Style Firefox* StartsOnPage 2 0, SkipMapping, RecaptureHonorsStartsOnPage, CaptureHonorsStartsOnPage, StartsOnPageIncludesTransients, FixedPPosition, State 2 The state is used later to exclude firefox from UrgencyFunc as it sometimes takes the focus itself, which led to errornous input of password or parts of it in the past, that I was typing in to another window at this moment. Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Re: FVWM: A question on Actions in FvwmButtons
On Thu, 25 Jan 2024 at 12:50, João Oliveira wrote: > Action (Mouse 1) 'Exec exec firefox ; ResizeMove 90 90 5 5' You should probably use the PositionPlacement style for this. -- Thomas
Re: FVWM: Where's stdout + stderr
On Sat, Nov 13, 2021 at 05:33:15PM -0700, Jaimos Skriletz wrote: > On Sat, Nov 13, 2021 at 5:25 PM Dominik Vogt wrote: > > > > The Devuan upgrade finally forces me to switch to v3, but it's > > giving me a _hard_ time debugging the configuration during the > > transition. There is zero indication of what fvwm is doing in the > > console output. Where's the error output? > > > > Checkout the -v option in the manual page. Fvwm now outputs logs to > ~/.fvwm/fvwm3-output.log and needs to be turned on. You can turn it on > for a running process using the SIGUSR2 signal. Thanks. This "3" stuff really needs to go away. Feels like being back to the nineties. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
Re: FVWM: Where's stdout + stderr
On Sat, Nov 13, 2021 at 5:25 PM Dominik Vogt wrote: > > The Devuan upgrade finally forces me to switch to v3, but it's > giving me a _hard_ time debugging the configuration during the > transition. There is zero indication of what fvwm is doing in the > console output. Where's the error output? > Checkout the -v option in the manual page. Fvwm now outputs logs to ~/.fvwm/fvwm3-output.log and needs to be turned on. You can turn it on for a running process using the SIGUSR2 signal. jaimos
Re: FVWM: a problem of .login starting fvwm (migration suse-ubuntu)
On Sun, 14 Nov 2021, Cameron Simpson wrote: On 14Sep2021 15:36, Lucio Chiappetti wrote: I am migrating (actually, configuring a new PC) from opensuse 42.3 to xubuntu 20.04.3. Thanks for your interest. In the meanhile I arranged an acceptable workaround. Apparently ALL of the .login is not executed This is pretty normal. The display manager is running fvwm as your "session", so it starts it directly without using a shell at all. My long standing approach has been to have a .xsession file specifying my desktop session. I'm not sure whether that's compatible with the default xubuntu way. To recap, a "text terminal then startx" style login goes: Used that only once for a laptop which failed to start X at boot (or perhaps back in the old times of Sun workstation in the '90s ...) An XDM (et al) style login goes: (not just the part relevant to XSESSION_IS_UP ...by the way what is the correct way in ubuntu to check I am in an X session ?) Apparently in xubuntu the things to be tested are if ( $?XDG_SESSION_TYPE != 0 ) then if ($XDG_SESSION_TYPE == x11) then my arrangement has been to move some conditional code in .cshrc, and leave some conditional X server stuff (like the X11 bell emulation) in .login, and force its execution in fvwm with a xterm -ls in StartFunction Thanks anyhow -- 'It seemed to me,' said Wonko the Sane, 'that any civilization that had so far lost its head as to need to include a set of detailed instructions for use in a package of toothpicks, was no longer a civilization in which I could live and stay sane.' Douglas Adams, So Long, and Thanks for All the Fish
Re: FVWM: a problem of .login starting fvwm (migration suse-ubuntu)
On 14Sep2021 15:36, Lucio Chiappetti wrote: >I am migrating (actually, configuring a new PC) from opensuse 42.3 to >xubuntu 20.04.3. In particular I would like to clone my fvwm >configuration (since I have a screen of the same size), the one in >http://sax.iasf-milano.inaf.it/~lucio/WWW/Opinions/window.html > >What I am noticing (which is probably not directly related fvwm itself >but to the way it is started with the X server) is that the fvwm >session does not run my .login (I am since ages a tcsh user, so I have >a .cshrc and a .login).Such .login is executed correctly in a ssh >session. > >The .login has few items (a PATH setting, a font path xset +fp setting >(plus other audio stuff so far commented out) which is conditional to >a $?XSESSION_IS_UP, and a setenv of some locale like LC_TIME to >en_US.UTF-8) > >Apparently ALL of the .login is not executed This is pretty normal. The display manager is running fvwm as your "session", so it starts it directly without using a shell at all. This is generally safer because many shell startups have some tty interaction which doesn't make sense in a batch environment (the headless process of running fvwm in a GUI directly). My long standing approach has been to have a .xsession file specifying my desktop session. Mine is this: #!/bin/sh . /etc/profile . $HOME/.profile exec $HOME/rc/x11/session To make your startup easier you'd want a tcsh based script, something like: #!/usr/bin/tcsh source /etc/login source $HOME/.login exec fvwm (Untested, and I am not a csh user so the syntax may be a bit incorrect.) In my setups I have environment setting in .profile and interactive stuff in .zshrc (or .bashrc, or .cshrc for you as a tcsh user). So the session script sources the .login (environment setting) but _not_ the .cshrc (interactive things). To recap, a "text terminal then startx" style login goes: - login tcsh - start x11, your environment is already set up An XDM (et al) style login goes: - X11 active - run .xsession - - source .login etc - - execute fvwm as the session, so that the logout happens when fvwm logs out Just a different ordering. >(not just the part relevant to XSESSION_IS_UP ...by the way what is >the correct way in ubuntu to check I am in an X session ?) I check that $DISPLAY is not empty, and maybe do an: xdpyinfo >&/dev/null as an additional check. In Bounre shell that might be like this: if [ -n "$DISPLAY" ] && xdpyinfo >/dev/null 2>&1 then ... x11 stuff here ... fi You'll have to adjust for csh. Cheers, Cameron Simpson
Re: FVWM: a problem of .login starting fvwm (migration suse-ubuntu)
Lucio, I also use Ubuntu 20.04, fvwm, and tcsh. What display manager are you using? I like xdm and fvwm is started from .xsession. My .login is just for setting the environment, and .tcshrc for aliases. cat .xsession #!/bin/bash export PATH=~/bin:/usr/local/bin:/usr/local/sbin:$PATH export TZ="America/Los_Angeles" /bin/mv -f /home/frankb/.xsession-errors /home/frankb/.xsession-errors.old exec /usr/bin/fvwm 2> $HOME/.xsession-errors E. Frank Ball III On Tue, Sep 14, 2021 at 03:36:43PM +0200, Lucio Chiappetti wrote: > I am migrating (actually, configuring a new PC) from opensuse 42.3 to > xubuntu 20.04.3. In particular I would like to clone my fvwm configuration > (since I have a screen of the same size), the one in > http://sax.iasf-milano.inaf.it/~lucio/WWW/Opinions/window.html > > What I am noticing (which is probably not directly related fvwm itself but > to the way it is started with the X server) is that the fvwm session does > not run my .login (I am since ages a tcsh user, so I have a .cshrc and a > .login).Such .login is executed correctly in a ssh session. > > The .login has few items (a PATH setting, a font path xset +fp setting > (plus other audio stuff so far commented out) which is conditional to a > $?XSESSION_IS_UP, and a setenv of some locale like LC_TIME to en_US.UTF-8) > > Apparently ALL of the .login is not executed > > (not just the part relevant to XSESSION_IS_UP ...by the way what is the > correct way in ubuntu to check I am in an X session ?) > > I checked with ps -H the way fvwm is started > > On suse > > 1 1690 root /usr/bin/sddm > 1690 17584 root /usr/lib/sddm/sddm-helper ... --start fvwm --user > lucio > 17584 17586 lucio /usr/bin/fvwm > > On ubuntu > > 1 977 root /usr/sbin/lightdm > 977 34424 root /usr/lib/xorg/Xorg -core :0 ... > 977 56656 root lightdm --session-child 12 19 > 56656 56682 lucio fvwm2 > 56682 56759 lucio/usr/bin/ssh-agent /usr/bin/im-launch fvwm2 > > The difference between fvwm and fvwm2 is virtual. On suse /usr/bin/fvwm2 is > a link to fvwm. On ubuntu fvwm is a link to /etc/alternatives... which in > turn is a link to /usr/bin/fvwm2. > > Suse has fvwm 2.6.6 and ubuntu has 2.6.8 > > What is apparent is that somehow suse performs a "login with my shell" > before starting fvwm (thus setting my environment) while ubuntu starts fvwm > ignoring my login shell choices. > > How can I either change this order, or instruct fvwm under ubuntu so that > it sets up a basic environment which is then inherited by all child shells > (in xterm, urxvt or whatever) ? > > Thanks > > -- > Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) > For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html
Re: FVWM: Interview fvwm developers
Hi, thanks for your replies. Am 07.07.21 um 23:14 schrieb Dominik Vogt: >> >> How far back is "early days"? I am sure Dan Espen and Dominik Vogt would >> qualify! > The beginning :) >> They're still lurking round these parts somewhere, I do hope! > > Sure I am. :) Great :) >> As for Robert Nation, I contacted him a few years ago via LinkedIn. Chuck >> hasn't been seen on this list in several years, AFAIK. > > Since 2005 I haven't talked to Rob and Chuck. The resulting > discussion is on our history page. Does anybody have an e-mail address Chuck Hines? I would try to contact them directly. I will contact Dominik, as we both speak German. Kind regards Keywan -- Redakteur/staff editor c’t – Magazin für Computertechnik www.ct.de Karl-Wiechert-Allee 10 D-30625 Hannover, Germany Tel.: +49 (0)511 5352 300 Fax: +49 (0)511 5352 417 E-Mail: k...@ct.de Heise Medien GmbH & Co. KG Registergericht: Amtsgericht Hannover HRA 26709 Persönlich haftende Gesellschafterin: Heise Medien Geschäftsführung GmbH Registergericht: Amtsgericht Hannover, HRB 60405 Geschäftsführer: Ansgar Heise, Dr. Alfons Schräder
Re: FVWM: Thank you for your work and suggestions for new FVWM features
Thank you. See below. Best wishes, Wojciech On 12/7/21 12:22 am, Thomas Adam wrote: On Sun, Jul 11, 2021 at 12:13:49PM +1000, Wojciech Lipinski wrote: Perhaps I could help a little bit with the content cleaning and merging. I do not have much spare time either but I could do what I can in the time available. I am not sure how http://fvwm.sourceforge.net/ relates to fvwm.org and who is in charge of it. Me neither, and it's not something I'm bothered to find out. In most cases, it seems sourceforge sites have been taken over by squatters. Although that's perhaps not the case here, I don't have control of that site and don't wish to. As I said before, in most google searches, fvwm.org is usually the place that's referenced. Yes, fvwm.org comes at the top, Github is a bit lower in the search results of Duckduckgo in Australia. It says it is a mirror of fvwm.org and that it is an official FVWM page, but it does not look like a mirror of fvwm.org anymore. However, the following section of that "mirror" website is quite useful: http://fvwm.sourceforge.net/doc/unstable/allCommands.html That's not something that's going to work for fvwm3, as the documentation is now rendered via asciidoctor. To maintain this list, we'd have to produce this a different way. I can see that /Archive/Manpages on fvwm.org contain all the commands (https://www.fvwm.org/Archive/Manpages/fvwm.html#lbBN). I could not find an index containing all commands. Would those pages, perhaps with a command index added and after removal of all the obsolete features, be an reasonable starting point for the official documentation of FVWM3 commands? Furthermore, some websites, e.g. https://wiki.debian.org/Fvwm, refer to https://www.fvwm.org/contact/ but it leads to 404. If Jaimos is reading this, I'm sure he'll be able to fix this on the Debian-side. Thanks. fvwm.org says 2.6.9 is a stable frozen release. Wikipedia says 3-1.0.3 is the current stable release. Perhaps 2.6.9 should be referred to as the old stable on fvwm.org? I guess there is some legacy for the long history of FVWM. How is fvwm.org maintained? It's no different to how it has always been. It's just that now, Github is being used for CI/CD and for people to submit patches. I can see that fvwm.org is now much refreshed and it has its Wiki section. Is it based on MediaWiki? If not, have you and/or your colleagues considered using MediaWiki? It's using Markdown and Jekyll (which is what is used for Github Pages as well). See: https://www.fvwm.org/Wiki/ -- this will tell where to find the repository to checkout for the Wiki as well (it's a part of the fvwm.org website code). Found it, thanks, all clear now. One more question related to the versions: /Wiki/Todo says under "Edits and Cleanup" "Update syntax and versions to 2.6.x.". As 3-1.03 is now the stable release, does it mean the 2.6.x syntax will be fully maintained in FVWM3, or this is some legacy text in the Wiki page? Kindly, Thomas
Re: FVWM: Microsoft Teams
On Thu, 13 Aug 2020, Klaus Ethgen wrote:
> Hi folks,
>
> Lets send that mail again after setting dmarc to quarantine instead of
> reject. This Mailinglist does not work with dmarc.
>
> I need to use Microsoft Teams for some reason. My problem is, that when
> I get a notification, that notification gets shown in the lower right
> side of the screen and direct after that, I get relocated onto the
> Screen where Teams is running, independent on what other screen I am
> currently and what I do.
>
> So I endet more than one time now, typing password into teams where it
> should never ever been.
>
> I already have !FPFocusByFunction and !FPFocusByProgram set but it
> doesn't work.
>
> `xev -id 0x481 -event expose -event visibility -event structure
> -event substructure -event focus -event owner_grab_button | awk
> '{now=strftime("%F %T%z\t");sub(/^/, now);print}'` gave me the
> following:
>2020-08-12 10:25:12+0100
>2020-08-12 10:25:12+0100VisibilityNotify event, serial 18,
> synthetic NO, window 0x481,
>2020-08-12 10:25:12+0100state VisibilityPartiallyObscured
>2020-08-12 10:25:12+0100
>2020-08-12 10:25:12+0100Expose event, serial 18, synthetic NO,
> window 0x481,
>2020-08-12 10:25:12+0100(0,0), width 1804, height 666, count 2
>2020-08-12 10:25:12+0100
>2020-08-12 10:25:12+0100Expose event, serial 18, synthetic NO,
> window 0x481,
>2020-08-12 10:25:12+0100(678,666), width 1126, height 515,
> count 1
>2020-08-12 10:25:12+0100
>2020-08-12 10:25:12+0100Expose event, serial 18, synthetic NO,
> window 0x481,
>2020-08-12 10:25:12+0100(678,1181), width 846, height 1, count > 0
>2020-08-12 10:25:12+0100
>2020-08-12 10:25:12+0100ConfigureNotify event, serial 18,
> synthetic YES, window 0x481,
>2020-08-12 10:25:12+0100event 0x481, window 0x481,
> (116,18), width 1804, height 1182,
>2020-08-12 10:25:12+0100border_width 0, above 0x140da85,
> override NO
>2020-08-12 10:25:12+0100
>2020-08-12 10:25:12+0100Expose event, serial 18, synthetic NO,
> window 0x481,
>2020-08-12 10:25:12+0100(0,666), width 678, height 516, count 0
>2020-08-12 10:25:12+0100
>2020-08-12 10:25:12+0100FocusIn event, serial 18, synthetic NO,
> window 0x481,
>2020-08-12 10:25:12+0100mode NotifyNormal, detail
> NotifyNonlinear
>
> Anybody an idea how to get rid of that very annoying behaviour?
>
> Its the most extreme focus grabbing I ever seen; Not even firefox is
> that extreme.
Teams is rubbish. Here are the things I do to make it less annoying
(still don't know how to get borders). You know how Alt-F4 (or whatever
your close is) minimises the window instead? So opening it back up first
involves going back to your original virtual desktop? Yeah, that's
annoying too. And it always then went to the bottom of my window focus
list because I had IconifiedAtEnd set (turns out I no longer iconify apps
intentionally, so easy to disable that).
I can't see anything in my Teams settings where I disable any urgency
or focus functions, so that might cover it. If not, I can dig deeper...
Key Tab A M WindowList Root c c CurrentDesk, NoGeometry, CurrentAtEnd # ,
IconifiedAtEnd #don't want IconfiedAtEnd anymore in 2020, because Microsoft
Teams iconifies when you close it, but you still want to be able to alt-tab
back to it. Would love an "IconifiedAtEndExceptForTeams"
DestroyFunc MyUrgencyFunc
AddToFunc MyUrgencyFunc
+ I Iconify off
+ I FlipFocus
+ I Raise
+ I WarpToWindow 5 5
# opera was from 2009. Microsoft teams actually steals the focus by
# warping the pointer to its window. Didn't need to engage the below
# styles as well
DestroyFunc UrgencyFunc
AddToFunc UrgencyFunc
+ I ThisWindow (!"opera|*Microsoft Teams*") MyUrgencyFunc
# nothing works to get borders and decorations back: Style "Microsoft Teams*"
GNOMEIgnoreHints #
https://fvwm.fvwm.narkive.com/z7ifVxX2/fvwm-forcing-window-decorations
# at least we get titlebar back:
# see also "missing titlebar, decorations for one program (Microsoft Teams
electron app)"
Style "*Microsoft Teams*" NoDecorHint, RecaptureHonorsStartsOnPage,
CaptureHonorsStartsOnPage, StartsOnPageIncludesTransients, FixedPPosition,
StickyIcon
--
Tim Connors
Re: FVWM: No module "FvwmTaskBar" in Fvwm 2.6.9?
Thomas,
On Monday, 2020-08-17 17:40:58 +0100, you wrote:
> ...
> Pass. Not a FVWM problem, but definitely a problem with Gentoo's ebuild.
>
> [~]{7958}[0] % apropos fvwm[23]
> fvwm3 (1)- F? Virtual Window Manager for X11
> FvwmMFL (1) - the Fvwm3 front-loader module
> fvwm2 (1)- F? Virtual Window Manager for X11
Funny, here "apropos" also finds "fvwm (1)", but of course neither
"fvwm2 (1)" nor "fvwm3 (1)". But
# find . -xdev \( -name 'fvwm.1*' -o -name 'fvwm2.1*' \)
#
doesn't return anything. So I'll ask on the Gentoo list.
> I'll get back to you about FvwmIconMan.
Fine, thanks :-)
Sincerely,
Rainer
Re: FVWM: No module "FvwmTaskBar" in Fvwm 2.6.9?
Thomas, On Monday, 2020-08-17 16:59:11 +0100, you wrote: > ... > Show me your config and I'll take a look. DestroyModuleConfig FvwmIconMan: * *FvwmIconMan: Action Mouse 1 N sendcommand Focus, sendcommand "Iconify Off" *FvwmIconMan: Action Mouse 2 N sendcommand "FvwmIdent" *FvwmIconMan: Action Mouse 3 N sendcommand "Iconify Toggle" *FvwmIconMan: Background Gray *FvwmIconMan: ButtonGeometry 1x30 *FvwmIconMan: DontShowicon=Untitled resource=Untitled *FvwmIconMan: FocusAndSelectButtonDown Black Yellow *FvwmIconMan: FocusButton Down Black Yellow *FvwmIconMan: FollowFocus True *FvwmIconMan: Font-bitstream-bitstream vera serif-bold-r-*--0-125-*-*-*-*-*-* *FvwmIconMan: Foreground Black *FvwmIconMan: Format "%t" *FvwmIconMan: IconButton Up Black Dimgray *FvwmIconMan: ManagerGeometry 1x1 *FvwmIconMan: MaxButtonWidthByColumns 1 *FvwmIconMan: NumManagers 1 *FvwmIconMan: PlainButton Up Black Gray *FvwmIconMan: ReliefThickness 2 *FvwmIconMan: Resolution Page *FvwmIconMan: SelectButtonUp Black Gray *FvwmIconMan: SortNone *FvwmIconMan: Title "" *FvwmIconMan: TitleButton Flat Black Gray *FvwmIconMan: UseWinList True > > > 2. After I upgraded again from Fvwm version 2.6.5-r3 to 2.6.9 I found > >that the manpage "/usr/share/man/man1/fvwm.1.bz2" is missing. Is > >this Gentoo specific or did I look in the wrong place? > > Sounds like the '--enable-mandoc' option to ./configure wasn't passed? Don't think so because other manual pages are there: $ ls -1 /usr/share/man/man1/Fvwm* /usr/share/man/man1/fvwm* /usr/share/man/man1/FvwmAnimate.1.bz2 /usr/share/man/man1/FvwmAuto.1.bz2 /usr/share/man/man1/FvwmBacker.1.bz2 /usr/share/man/man1/FvwmBanner.1.bz2 /usr/share/man/man1/FvwmButtons.1.bz2 /usr/share/man/man1/FvwmCommand.1.bz2 /usr/share/man/man1/FvwmConsole.1.bz2 /usr/share/man/man1/FvwmConsoleC.pl.1.bz2 /usr/share/man/man1/FvwmCpp.1.bz2 /usr/share/man/man1/FvwmEvent.1.bz2 /usr/share/man/man1/FvwmForm.1.bz2 /usr/share/man/man1/FvwmIconMan.1.bz2 /usr/share/man/man1/FvwmIdent.1.bz2 /usr/share/man/man1/FvwmM4.1.bz2 /usr/share/man/man1/FvwmPager.1.bz2 /usr/share/man/man1/FvwmPerl.1.bz2 /usr/share/man/man1/FvwmProxy.1.bz2 /usr/share/man/man1/FvwmRearrange.1.bz2 /usr/share/man/man1/FvwmScript.1.bz2 /usr/share/man/man1/fvwm-bug.1.bz2 /usr/share/man/man1/fvwm-config.1.bz2 /usr/share/man/man1/fvwm-convert-2.6.1.bz2 /usr/share/man/man1/fvwm-menu-desktop.1.bz2 /usr/share/man/man1/fvwm-menu-directory.1.bz2 /usr/share/man/man1/fvwm-menu-headlines.1.bz2 /usr/share/man/man1/fvwm-menu-xlock.1.bz2 /usr/share/man/man1/fvwm-root.1.bz2 $ Sincerely, Rainer
Re: FVWM: No module "FvwmTaskBar" in Fvwm 2.6.9?
Thomas, On Saturday, 2020-08-15 12:36:24 +0100, you wrote: > ... > Custom tooltips aren't possible in FvwmButtons yet. Well, I think I'll survive with just the clock :-) However, two other minor problems showed up: 1. While the names of the buttons in FvwmButtons are placed normally, the names of the FvwmIconMan buttons are placed (using format "%t") as if all names started with two or three blanks, which is just a minor waste of time. That's probably just the space occupied by the square box shown for iconified windows. But even whith "ShowNoIcons True" neither this box nor this space goes away. What's the correct option to use? 2. After I upgraded again from Fvwm version 2.6.5-r3 to 2.6.9 I found that the manpage "/usr/share/man/man1/fvwm.1.bz2" is missing. Is this Gentoo specific or did I look in the wrong place? Sincerely, Rainer
Re: FVWM: No module "FvwmTaskBar" in Fvwm 2.6.9?
Thomas, On Wednesday, 2020-08-12 21:45:44 +0100, you wrote: > ... > Autohide is already in the FAQ and is independent of any module. See: > > https://www.fvwm.org/Archive/Faq/#autohiding-fvwmbuttons-or-other-windows Ok, so this is solved, too. Thankyou :-) > For everything else such as a Start button and a clock is achievable through > FvwmButtons. Others have also pointed me to https://www.fvwm.org/Wiki/Panels/FvwmTaskBar/ and that helped me re-implementing my taskbar, except for the clock dis- playing the current date as tooltip when hovering the mouse pointer over it. Is this still doable? > ... > >FvwmForm > Killed. I use FvwmForm to interactively ask questions and to interpret the ans- wers received. How to do this now? > ... > >FvwmWinlist > Dead. Erm ... what's the difference between "Killed" and "Dead"? But more to the point: How do I achieve the same effect with current methods? > You'll hate Fvwm3. Just because I'll have to change my configuration files? No. But if Fvwm3 can no longer do things I need and Fvwm2 was able to do, then yes. Sincerely, Rainer
Re: FVWM: detecting "continuous" keyboard modifier
thomas wrote: > On Tue, Jun 23, 2020 at 11:57:45AM -0400, Paul Fox wrote: > > Hi -- > > > > Is there a way in fvwm to distiguish these two sequences? > > alt tab alt tab > > ^tab and alt keys both released here > > and > > alt tab tab > > ^ only tab key released here > > > > I don't recall seeing anything about this in the docs -- but that > > doesn't mean it's not there! :-) > > This is not possible at the moment. Thanks. paul =-- paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 76.5 degrees)
Re: FVWM: No module "FvwmTaskBar" in Fvwm 2.6.9?
Thomas, On Tuesday, 2020-08-11 15:30:04 +0100, you wrote: > ... > > Question: What has become of "FvwmTaskBar"? > > FvwmIconMan is the module to use now. Well, reading the manual page I'm not yet quite sure it fits my needs: My taskbar - features three more buttons in addition to the "Start Menu" button, - features a digital clock which shows the date as tooltip, - and most importantly it automatically hides. While I think I could also provide the buttons via module "FvwmButtons" and could use a separate digital clock application, I did neither find an "AutoHide" specification for "FvwmIconMan" nor for "FvwmButtons". And auto hiding of the taskbar is crucial for my various fullscreen app- lications running each in a separate desktop page. Any suggestions? And while we're at it, here's a list of other Fvwm modules important for me: FvwmAuto FvwmConsole FvwmForm FvwmIdent FvwmPager FvwmWinlist Are all of these still available in Fvwm 2.6.9 and not yet deprecated? Sincerely, Rainer
Re: FVWM: How to make window appear on multiple (but not all) desktops?
Thanks very much Dominik, Hegel3DReloaded, and Elliot! I was able to use your ideas to craft a solution. Cheers, Steve Dominik Vogt wrote: > On Wed, Feb 26, 2020 at 03:16:12PM -0500, Stephen Talley wrote: > > In my FVWM configuration, I can use either Sticky: > > > > # Show window on all desktops > > Style *Emulator* Sticky > > > > ???or StartsOnDesk: > > > > # Show window on desktop 3 only > > Style *Emulator* StartsOnDesk 3 > > > > But how can I make a window appear on, say, desktops 3 and 4, but not 0, 1, > > or 2? > > Fvwm does not manage desk objects. The desk a window is present > on is just a property of the window, so there is no direct way to > do that. However, you can do some scripting: > > -- snip -- > addtofunc custom_gotodesk > + I setenv _desk $0 > + I test (envmatch _desk 1) all (xeyes) stick on > + I test (envmatch _desk 2) all (xeyes) stick on > + I test (envmatch _desk 3) all (xclock) stick on > + I test (envmatch _desk 4) all (xclock) stick on > + I GotoDesk 0 $0 > + I All (xeyes) stick off > + I All (xclock) stick off > + I unsetenv _desk > -- snip -- > > Call this function instead of GotoDesk with > > custom_gotodesk > > -- > > This won't work if you click on the pager to switch desks because > the GotoPage command is hard coded there. In that case, FvwmEvent > helps: > > -- snip -- > *FvwmEvent: new_desk deskchange > Module FvwmEvent > > addtofunc deskchange > + I echo dc $[desk.n] > + I setenv _desk $[desk.n] > + I test (envmatch _desk 1) all (xeyes) movetodesk > + I test (envmatch _desk 2) all (xeyes) movetodesk > + I test (envmatch _desk 3) all (xclock) movetodesk > + I test (envmatch _desk 4) all (xclock) movetodesk > + I unsetenv _desk > -- snip -- > > You'll probably want to put the module execution in the > initfunction/restartfunction. > > Ciao > > Dominik ^_^ ^_^ > > -- > > Dominik Vogt
Re: FVWM: How to make window appear on multiple (but not all) desktops?
On Wed, Feb 26, 2020 at 03:16:12PM -0500, Stephen Talley wrote: > In my FVWM configuration, I can use either Sticky: > > # Show window on all desktops > Style *Emulator* Sticky > > ???or StartsOnDesk: > > # Show window on desktop 3 only > Style *Emulator* StartsOnDesk 3 > > But how can I make a window appear on, say, desktops 3 and 4, but not 0, 1, > or 2? Fvwm does not manage desk objects. The desk a window is present on is just a property of the window, so there is no direct way to do that. However, you can do some scripting: -- snip -- addtofunc custom_gotodesk + I setenv _desk $0 + I test (envmatch _desk 1) all (xeyes) stick on + I test (envmatch _desk 2) all (xeyes) stick on + I test (envmatch _desk 3) all (xclock) stick on + I test (envmatch _desk 4) all (xclock) stick on + I GotoDesk 0 $0 + I All (xeyes) stick off + I All (xclock) stick off + I unsetenv _desk -- snip -- Call this function instead of GotoDesk with custom_gotodesk -- This won't work if you click on the pager to switch desks because the GotoPage command is hard coded there. In that case, FvwmEvent helps: -- snip -- *FvwmEvent: new_desk deskchange Module FvwmEvent addtofunc deskchange + I echo dc $[desk.n] + I setenv _desk $[desk.n] + I test (envmatch _desk 1) all (xeyes) movetodesk + I test (envmatch _desk 2) all (xeyes) movetodesk + I test (envmatch _desk 3) all (xclock) movetodesk + I test (envmatch _desk 4) all (xclock) movetodesk + I unsetenv _desk -- snip -- You'll probably want to put the module execution in the initfunction/restartfunction. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
Re: FVWM: How to make window appear on multiple (but not all) desktops?
On Wednesday, 26. February 2020 20:16, Stephen Talley wrote: > In my FVWM configuration, I can use either Sticky: > > # Show window on all desktops > Style Emulator Sticky > > …or StartsOnDesk: > > # Show window on desktop 3 only > Style Emulator StartsOnDesk 3 > > But how can I make a window appear on, say, desktops 3 and 4, but not 0, 1, > or 2? > > Thanks, > > Stephen In your case StickyAcrossDesks is not an option, since it doesn't have desk arguments. You can help yourself with FvwmEvent module to observe desk changes. For example: *FvwmEvent: Cmd *FvwmEvent: new_desk f_ChangeDesk And then write some handy function(s): DestroyFunc f_ChangeDesk AddToFunc f_ChangeDesk + I InfoStoreAdd current_desk $[desk.n] + I Test (EnvMatch infostore.current_desk 3) Next (Emulator) MoveToDesk + I Test (EnvMatch infostore.current_desk 4) Next (Emulator) MoveToDesk -- Hegel3DReloaded https://github.com/NsCDE/NsCDE
Re: FVWM: Fvwm3 Virtual Desktop Problem
On Fri, 21 Feb 2020 09:45:57 + Thomas Adam wrote: > Please send me a copy of your config. > The config file is attached. The VD lines are near the top. But since my original post I need to make a slight correction. I just noticed I actually have *three* virtual desktops in a 3x1 arrangement. I did not notice this at first since I never scroll beyond the rightmost desktop with a 2x2 arrangement. LP config Description: Binary data
Re: FVWM: Fvwm3 Virtual Desktop Problem
On Thu, Feb 20, 2020 at 06:53:43PM -0500, Larry Piet wrote: > When I started fvwm3 using the same config file as with fvwm-2.6.9 > there were no apparent problems. However, my virtual desktops were > missing. The config file specifies a 2x2 arrangement but with > fvwm3 I only get a 2x1 arrangement. The lower two virtual desktops > are not present. Please send me a copy of your config. Kindly, Thomas
Re: FVWM: Perform action, one in a time - at every open window at all desks and workspaces.
I often restart fvwm. With tons of windows open. So that no windows are open - cant be the reason. I have written in this thread espcially about that - and maybe found a way out of it. But the message is stalled . So I have to wait until it been moderated. And I prefere to not use fvwm-event in this case - out of several reasons. I have the thumbnail-function executed every time i switch desktop. I just want a helper function that I runs only when needed. 2020-02-07 17:08 GMT+01:00, Dominik Vogt : > Please don't top-post on this list and leave the relevant portions > of the discussion intant when replying to a message. > > On Fri, Feb 07, 2020 at 04:10:49PM +0100, Peter Holm wrote: >> I am not sure if the All command is the solution. I suppose the >> actual viewport (if that is the correct term here) should be at the >> actual desk and page before the function thumbnail_minicons executes. >> >> Am I wrong.? > > "All" (without further conditions) does what the name suggests: It > executes the action for each and every existing window at the time > when its called. E.g. > > All MoveToDesk > > moves all windows to the current desk. > >> 2020-02-07 11:56 GMT+01:00, Peter Holm : >> > No go with >> > AddtoFunc StartFunction >> > + I All Thumbnail_MiniIcons > > The problem with that approach is that the function is executed in > the StartFunction, before any window is created. If it's really > necessary to execute a function for a new window, the FvwnEvent > module can be used. > > Ciao > > Dominik ^_^ ^_^ > > -- > > Dominik Vogt > > -- Med vänlig hälsning / With kind regards /Peter Holm
Re: FVWM: Perform action, one in a time - at every open window at all desks and workspaces.
On Thu, Feb 06, 2020 at 10:00:57PM +0100, Peter Holm wrote: > Is there any way go to every populated desk/page, and perform action > at windows att thoose desk/pages.? Yes, the command is "all", e.g. all Thumbnail_MiniIcons > I would like to perform this modified version of Tavis Ormandy's > tumbnial function at every populated desk/page when some specific > comdirions are met. > > DestroyFunc Thumbnail_MiniIcons > AddToFunc Thumbnail_MiniIcons > + I SetEnv fvwm_mini_icon_size 64 ##Replace with infostore > + I Current Raise > + I SetEnv MiniIcon-$[w.id] $[w.MiniIconFile] > + I ThisWindow (!Shaded, Focused, !Overlapped, !FvwmPager, !Iconic) PipeRead \ > " echo Raise; $[FVWM_USERDIR]/bin/thumb $[w.id] $[fvwm_mini_icon_size]\ > $[FVWM_USERDIR]/tmp/mini_icon.tmp.$[w.id].png $[w.MiniIconFile]\ > && echo WindowStyle EWMHMiniIconOverride, MiniIcon > $[FVWM_USERDIR]/tmp/mini_icon.tmp.$[w.id].png || echo Nop" Ciao Dominik ^_^ ^_^ -- Dominik Vogt
Re: FVWM: Pixmaps [was: Minimum task bar example]
> Thomas Adam hat am 6. Januar 2020 um 15:18 geschrieben: > Beyond the example you've already mentioned, what more is it you're wanting to > do? What should the end result look like for you? The example did not work. I tried it two times on two different machines. Copied line by line it showed vertically arranged buttons looking similar to WindowList. I wanted to have horizontally arranged buttons like in the default task bar of KDE or MS windows. Meanwhile I did achieve something with FvwmIconMan alone, but then I had checkboxes for iconified windows. I just wanted to have simple buttons for which the windows are raised when I klick into them with the left mouse button, as simple as possible. I now did setup right mouse button actions for the window decoration which display the WindowList, so I don't need a task bar any more. Off-Topic: The GitHub repo seems to not contain the FVWM pixmaps (the mini.xpms), is there an upstream repo somewhere else which contains them? Carsten
Re: FVWM: Minimum task bar example
On Sun, Dec 22, 2019 at 02:11:10PM +0100, Carsten Kunze wrote: > Hello, > > is there a minimum task bar example as a starting point for something more > sophisticated? Just making the task bar appear with as few as possible > lines? The example at https://fvwmforums.org/wiki/Panels/FvwmTaskBar/ does > not work, i.e. does not look as expected (it looks as a simple "Module > FvwmIconMan" with just a different background color). Beyond the example you've already mentioned, what more is it you're wanting to do? What should the end result look like for you? Kindly, Thomas
Re: FVWM: Laptop backlight control applet
Hi, Perhaps in Arch wiki (https://wiki.archlinux.org/index.php/Backlight) you'll find more. Regards, Thomas Am 29. Dezember 2019 15:57:52 schrieb Dan Espen : Carsten Kunze writes: Stuart Longland hat am 29. Dezember 2019 um 13:54 geschrieben: Under Linux I have key bindings set up that call this Python script installed in /usr/local/bin: https://gitlab.com/wavexx/acpilight/blob/06fcb7452e8b79107860425af4aecc1dac9e06b1/xbacklight The relevant files in /sys are owned by the 'video' group. Not sure what would be used on BSD or Unix though and you don't say what OS you're using. I'm using Linux. Unfortunately I'm more looking for a graphical app (best would be something which can be added to stalonetray). The search "xbacklight gui" suggests there are multiple choices. Perhaps this one: https://github.com/theelous3/xbacklight-tooltip -- Dan Espen
Re: FVWM: Laptop backlight control applet
Carsten Kunze writes: >> Stuart Longland hat am 29. Dezember 2019 >> um 13:54 geschrieben: Under Linux I have key bindings set up that >> call this Python script installed in /usr/local/bin: >> >> https://gitlab.com/wavexx/acpilight/blob/06fcb7452e8b79107860425af4aecc1dac9e06b1/xbacklight >> >> The relevant files in /sys are owned by the 'video' group. >> >> Not sure what would be used on BSD or Unix though and you don't say >> what OS you're using. > > I'm using Linux. Unfortunately I'm more looking for a graphical app > (best would be something which can be added to stalonetray). The search "xbacklight gui" suggests there are multiple choices. Perhaps this one: https://github.com/theelous3/xbacklight-tooltip -- Dan Espen
Re: FVWM: Laptop backlight control applet
> Stuart Longland hat am 29. Dezember 2019 um > 13:54 geschrieben: > Under Linux I have key bindings set up that call this Python script > installed in /usr/local/bin: > > https://gitlab.com/wavexx/acpilight/blob/06fcb7452e8b79107860425af4aecc1dac9e06b1/xbacklight > > The relevant files in /sys are owned by the 'video' group. > > Not sure what would be used on BSD or Unix though and you don't say what > OS you're using. I'm using Linux. Unfortunately I'm more looking for a graphical app (best would be something which can be added to stalonetray).
Re: FVWM: Laptop backlight control applet
> Mandar Mitra hat am 29. Dezember 2019 um 14:00 > geschrieben: > Not sure this is of any use to you, but the designated Fn+key combination > (F10 on my laptop) works for me. I'm running fvwm as the window manager via > .xsession on a Linux Mint Mate 19 box. This does work somehow but I'm rather looking for an applet with a graphical interface, i.e. a slider controllable with the mouse.
Re: FVWM: Laptop backlight control applet
Carsten Kunze wrote (Sun, Dec 29, 2019 at 01:16:41PM +0100): > Hello, > > is there an laptop backlight control applet which can be used with FVWM (and > possibly stalonetray)? Not sure this is of any use to you, but the designated Fn+key combination (F10 on my laptop) works for me. I'm running fvwm as the window manager via .xsession on a Linux Mint Mate 19 box.
Re: FVWM: Laptop backlight control applet
On 29/12/19 10:16 pm, Carsten Kunze wrote: > Hello, > > is there an laptop backlight control applet which can be used with FVWM (and > possibly stalonetray)? > Under Linux I have key bindings set up that call this Python script installed in /usr/local/bin: https://gitlab.com/wavexx/acpilight/blob/06fcb7452e8b79107860425af4aecc1dac9e06b1/xbacklight The relevant files in /sys are owned by the 'video' group. Not sure what would be used on BSD or Unix though and you don't say what OS you're using. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: FVWM: avoiding crosshair when thumbnailing
I Invoke it from the function I use to switch desktops and pages. Anyway - i solved it. I Just removed Raise. /Peter 2019-12-26 1:31 GMT, Thomas Adam : > On Thu, Dec 26, 2019 at 12:26:03AM +, Peter Holm wrote: > > Hi Peter, > >> To get thumbnails within fvwmpager, I do as following. >> DestroyFunc Mini_Thumbnail >> AddToFunc Mini_Thumbnail >> + I Raise >> + I SetEnv MiniIcon-$[w.id] $[w.MiniIconFile] >> + I ThisWindow (!Shaded, !FvwmPager, !Iconic) PipeRead \ >> "$[FVWM_USERDIR]/bin/thumb $[w.id] $[fvwm_mini_icon_size] >> $[FVWM_USERDIR]/tmp/mini_icon.tmp.$[w.id].png $[w..MiniIconFile]\ >> && echo WindowStyle EWMHMiniIconOverride, MiniIcon >> $[FVWM_USERDIR]/tmp/mini_icon.tmp.$[w.id].png || echo Nop" >> #- >> >> But the call to ThisWindow gives me a crosshair in thoose cases where >> there is no window below the mousepointer. >> How do I avoid the crosshair.? > > You're seeing the crosshair because the way you've invoked Mini_Thumbnail > is > not in a window context which means FVWM has no idea which window to > operate > on. > > How are you invoking this function? > > Kindly, > Thomas > -- Med vänlig hälsning / With kind regards /Peter Holm
Re: FVWM: avoiding crosshair when thumbnailing
On Thu, Dec 26, 2019 at 12:26:03AM +, Peter Holm wrote: Hi Peter, > To get thumbnails within fvwmpager, I do as following. > DestroyFunc Mini_Thumbnail > AddToFunc Mini_Thumbnail > + I Raise > + I SetEnv MiniIcon-$[w.id] $[w.MiniIconFile] > + I ThisWindow (!Shaded, !FvwmPager, !Iconic) PipeRead \ > "$[FVWM_USERDIR]/bin/thumb $[w.id] $[fvwm_mini_icon_size] > $[FVWM_USERDIR]/tmp/mini_icon.tmp.$[w.id].png $[w..MiniIconFile]\ > && echo WindowStyle EWMHMiniIconOverride, MiniIcon > $[FVWM_USERDIR]/tmp/mini_icon.tmp.$[w.id].png || echo Nop" > #- > > But the call to ThisWindow gives me a crosshair in thoose cases where > there is no window below the mousepointer. > How do I avoid the crosshair.? You're seeing the crosshair because the way you've invoked Mini_Thumbnail is not in a window context which means FVWM has no idea which window to operate on. How are you invoking this function? Kindly, Thomas
Re: FVWM: Window title placed to low in title area
> Thomas Adam hat am 17. Dezember 2019 um 02:03 geschrieben: > > The font size is also taken into account when rendering, plus the TitleHeight. > I'm still not sure what problem you're having, but I'd say it's working as > expected. I have supplied some example pictures. I don't know if they can be attached at this mailing list so I put them on an image server. I'm using the following minimal RC file which uses the default font (which I want to use): TitleStyle Height 14 Mouse 1 R A Menu RootMenu Nop Mouse 3 R A WindowList Mouse 0 4 A Iconify AddToMenu RootMenu + XTerm Exec exec xterm + Restart Restart https://ibb.co/bgKPt9q shows the default title area height. You can see the the lowest pixels of 'y' and 'g' are already at the bottom line. Below the '[' is 1 pixel and 2 or 3 pixels are above--so the font is already not perfectly centered. At https://ibb.co/nkvX1rf you see the result for TitleStyle Height 18. Now some pixels at the bottom are cut while the space above the text remains the same. At https://ibb.co/b18hHD0 is the example for TitleStyle Height 16 and at https://ibb.co/zFL9fd4 for TitleStyle Height 14. Now the text can't be read anymore, still there is free space above the text. What I had expected is that space below *and* above the text gets reduced when text area height gets decreased. So is it either possible to calculate the vertical position depending on text font size and title area high or to supply a simple command for the RC file so the user can specify an offset for the vertical text placement?
Re: FVWM: Window title placed to low in title area
On Sun, Dec 15, 2019 at 02:58:50PM +0100, Carsten Kunze wrote: > Hello, > > by default FVWM (2.6.7) does place the window title with a fixed offset from > top of the title area. If the title area height is reduced using "TitleStyle > Height" the free space below the title text gets reduced and finally the > text gets clipped from below. What would be expected is that the text gets > rendered always vertically centered regardless of the title area height. The font size is also taken into account when rendering, plus the TitleHeight. I'm still not sure what problem you're having, but I'd say it's working as expected. > Is there an option to somehow affect the vertical placement of the window > title text? No, there is not. -- Thomas Adam
Re: FVWM: FvwmPerl not compatible with Perl 5.26 and later?
Ok I cloned from master and built it and confirmed that Perl 5.26.1 is working fine with this version. A bug fix version would be great. Thanks, Lance > On Dec 9, 2019, at 2:12 PM, Thomas Adam wrote: > >> On Sun, Dec 08, 2019 at 03:55:50PM -0800, Lance wrote: >> Is this a known issue? I looked at the source code for fvwm 2.6.9 and it >> seems to have to same issue. > > If you could check master, I can release a bug-fix version of FVWM for this. > Just let me know. > > Kindly, > Thomas
Re: FVWM: Question regarding actions when modifier keys are held down/released
On Wed, Sep 4, 2019 at 11:32 PM Stephen Dennison wrote:
> Well, as Thomas Adam points out, you can just use FvwmPager
> -transient. You can then use up/down/left/right to move towards a
> page, then hit any key to dismiss it. With just -transient it wont
> show other desks, so you'd have to pick the number of desks you want
> and provide that as a max. For example, I use five here (for six
> desks):
>
> Key Alt_L A C FvwmPager -transient 0 5
>
> ...
>
> But really, use Thomas's suggestion, as usual, it's terse and entirely
> on point.
Ok, it took me a while to get back to this. I've been trying different
configurations and simplifying, and have come up with a solution for
now. The transient option did not behave as I desired, as it required
me to hit a key or button to make the pager go away, at least as I had
it configured. There is still a bit of tweaking to do, but this works
and is close enough to the ideal behavior (from my perspective), that
I'll stick with it for a while.
First, my configuration is as follows (these are all the entries in my
`.fvwm/config` file that I thought were relevant):
#v+
# Set debug variable.
InfoStoreAdd DEBUG true
# Virtual desktops
DesktopName 0 main
DesktopName 1 vm
DesktopName 2 code
DesktopName 3 other
DesktopSize 1x1
# Give hints to ewmh compliant pagers and taskbars.
EwmhNumberOfDesktops 4
# Set focus style to SloppyFocus, and a mouse click raises a window.
Style * SloppyFocus, MouseFocusClickRaises
# Minimize overlap with other windows measured by pixel area.
Style * MinOverlapPlacement
# Use the rubber-band outline style when resizing windows.
Style * ResizeOutline
# Allow windows/icons to snap to other windows/icons, respectively, if
# they come within 15 pixels of the other object. All can snap to the
# screen edge.
Style * SnapAttraction 15 SameType ScreenAll
# Style for the pop-up pager.
Style PopUpPager PositionPlacement screen 0 100-100w 0-1p
Style PopUpPager !Borders, CirculateSkip, FixedPosition, FixedSize, !Handles, \
StaysOnTop, Sticky, !Title, WindowListSkip
# Function: ShadeIt - START
#
# $0: Name of window
# $1: Shaded state (Shaded or !Shaded)
# $2: ToBeShaded (True or False)
# $3: Target layer
# $4: Post shade action (usually Raise or Lower)
#
# If a window named $0 exists and is in state $1, then apply shade
# state $2 to it, place it in layer $3, then take action $4 (usually
# Raise or Lower).
DestroyFunc ShadeIt
AddToFunc ShadeIt
# Log function entry and parameters.
+ I Test ($[infostore.DEBUG]) \
Echo < ShadeIt (0: $0) (1: $1) (2: $2) (3: $3) (4: $4)
# If no window of this name exists then log it and break out.
+ I None ("$0", CirculateHit) Echo | ShadeIt - no such window
+ I TestRc (Match) Break
# If it does exist and is in state $1, then apply shade state $2, ...
+ I Next ("$0", CirculateHit, $1) WindowShade $2
+ I TestRc (Match) KeepRc Test ($[infostore.DEBUG]) \
Echo | ShadeIt - '$0' shaded state to $2 based on $1
# ... place it in layer $3, ...
+ I TestRc (Match) Next ("$0", CirculateHit, !$1) Layer 0 $3
+ I TestRc (Match) KeepRc Test ($[infostore.DEBUG]) \
Echo | ShadeIt - '$0' placed in layer $3
# ... and execute $4 on it.
+ I TestRc (Match) Next ("$0", CirculateHit, !$1) $4
+ I TestRc (Match) KeepRc Test ($[infostore.DEBUG]) \
Echo | ShadeIt - $4 '$0'
# Function: ShadeIt - END
# Function: ToggleShade - START
#
# $0: Name of window
# $1: Command to execute
#
# Check for window named $0. If not found, execute $1. Once found,
# toggle shade state of $0 (shade if unshaded, unshade if shaded).
#
# Found: https://fvwmforums.org/wiki/Tips/TogglingWindows/
DestroyFunc ToggleShade
AddToFunc ToggleShade
+ I Test ($[infostore.DEBUG]) Echo < ToggleShade (0: $0) (1: $1)
+ I None ("$0", CirculateHit) $1
+ I TestRc (Match) KeepRc Test ($[infostore.DEBUG]) \
Echo | ToggleShade - '$0' opened
+ I TestRc (Match) Wait "$0"
# Check to see if the target window is shaded and, if so, unshade.
+ I Next ("$0", CirculateHit, Shaded) \
ShadeIt "$0" Shaded False 6 Raise
+ I TestRc (Match) Break
# Check to see if the target window is unshaded and, if so, shade.
+ I Next ("$0", CirculateHit, !Shaded) \
ShadeIt "$0" !Shaded True 0 Lower
# Function: ToggleShade - END
# Function: ChangeToDesk - START
#
# $1: Name of the pager to show when changing.
# $0: Change the view by this number of desks.
#
# Change desks downward (if $1 = 1) or upward (if $1 = -1), unshade
# the window named $0, and schedule it to shade each time the desk is
# changed to get it out of the way.
DestroyFunc ChangeToDesk
AddToFunc ChangeToDesk
+ I Test ($[infostore.DEBUG]) Echo < ChangeToDesk
# Step 1: Display $0 by unshading if window name provided.
+ I Test (!EnvMatch 0 "") \
Next ("$0", CirculateHit, Shaded) ShadeIt "$0" Shaded False 6 Raise
# Step 2: Change desks.
+ I GotoDesk $1 0 3
+ I Test ($[infostore.DEBUG]) \
Echo | ChangeToDesk - Go to the desk $[desk.n]: $[desk.name$[desk.n]]
# Step 3: Desc
Re: FVWM: Question regarding actions when modifier keys are held down/released
On Wed, Sep 04, 2019 at 11:30:48PM -0400, Stephen Dennison wrote: > Sorry about that. It worked briefly but now it seems it has been > "archived".. I presume that someone saw mention of the errors and went > off to either fix it or just archive the content off to make it > available elsewhere... It's dead, Jim. To be replaced with something newer, sometime soon. > But really, use Thomas's suggestion, as usual, it's terse and entirely on > point. :) -- Thomas Adam
Re: FVWM: Question regarding actions when modifier keys are held down/released
> Another interesting idea - although I think I'm starting to lean toward > having the pager pop up when the desk change is initiated, and then the > only problem is how to allow multiple desk changes without releasing the > Ctrl-Alt keys, and how to make sure the pager closes after releasing the > keys. Well, as Thomas Adam points out, you can just use FvwmPager -transient. You can then use up/down/left/right to move towards a page, then hit any key to dismiss it. With just -transient it wont show other desks, so you'd have to pick the number of desks you want and provide that as a max. For example, I use five here (for six desks): Key Alt_L A C FvwmPager -transient 0 5 So, have a pager that shows 5 desktops (and however many pages you've already defined), summon that pager by hitting ctrl and then alt (because control is used as the modifier) and use the arrow keys to move from page to page. The pager just seems to support doing this, using arrows to move page to page, I mean. I don't know where this is documented. I just happened to notice it when I was testing it. To move a desk, you'd need another keybinding. Unless there is some other key for this, as I'm not even sure where the arrow keys are documented. But you might want to use different keys for moving by a full desk. Either way, here's how you could move a desk up or down, again using zero to five desks (total of size): Key Right A CM GotoDesk 1 0 5 Key Left A CM GotoDesk -1 0 5 Because it uses the same keys as those for summoning the pager you might get some drawing oddities, but it will still move like it's supposed to. This doesn't quite fit your desire of dismissing after landing on your target desk, though, so you mgiht just want to use ctrl + arrow to move (get rid of M modifiers above) so it doesn't interfere with the pager. This will allow the pager to stay up until you dismiss it with something (like space or enter or any key other than arrows, I think). So be sure to do something like this, too: Style FvwmPager Sticky, StaysOnTop > > >I had experimented with using the windows key to do something on its > >own when not being used as a modifier key, but I eventually discarded > >it. I posted about it to the fvwm forums, which can be found here: > >https://fvwmforums.org/phpBB3/viewtopic.php?f=6&t=2832#p14222 > > Hrm... I get all kinds of warnings when I access that page, and no > information in any of the three posts. Is there another place to access > the information? Sorry about that. It worked briefly but now it seems it has been "archived".. I presume that someone saw mention of the errors and went off to either fix it or just archive the content off to make it available elsewhere... It was a filthy hack anyway. Essentially I re-assign stdout to dev null so that I can import xlib, which will complain about something I can't recall to standard out which fvwm would choke on from a piperead, then I tested to see if a modifier was still held down within a certain timeout so that I could ignore any long presses, eg presses where the modifier was being used as a modifier to press some other key because it took longer to do that then it did to just whack the modifier as a bound key. Then I wrote the command I wanted Fvwm to run to FvwmCommand. But really, use Thomas's suggestion, as usual, it's terse and entirely on point.
Re: FVWM: Question regarding actions when modifier keys are held down/released
* Stephen Dennison [2019-08-29 09:25 -0400]: On Thu, Aug 29, 2019 at 8:43 AM Dave Weller-Fahy wrote: On Thu, Aug 29, 2019 at 2:16 AM Martin Cermak wrote: > On Wed 2019-08-28 13:03 , Dave Weller-Fahy wrote: > > My goal is to have the following rules followed. > > > > Rules about keys being pressed and (possibly) held. > > - If Ctrl-Alt are pressed ... > > - and if no other keys are pressed within some period of time ... > > - then pop up the pager > > - and if other keys (such as arrow keys) are pressed ... > > - then execute some other action > > > > Rules about keys being released. > > - If Ctrl-Alt are released ... > > - and if the pager is displayed ... > > - then remove the pager > > > > The use case is to have Ctrl-Alt-(up|down|left|right) change desks, > > I have this setup too (as an option). But primarily I use > Ctrl-Alt-(). This gives me a clear idea which > of my 9 desks (arranged as a 3x3 matrix) I am switching to. > Nothing visual involved. I was reaching the conclusion that what I wanted was not possible with fvwm (at least, not possible without an external utility), but figured I would check with the mailing list before giving up and looking for an external utility to help. I may also try fvwm3 to see if what I want is possible there. You can bind a key to a modifier and set the unbound one as your modifier (Key Control_L A M Exec exec executable.nameor Key Alt_L A C Exec exec executable.name or ...) And that can still be used for some other action (Key T A CM Exec exec other-executable.name would still work, for example) but it will cause your executable to be executed even when you're just using the alt and control as modifiers. Hrm... I'd tried to do that, and completely forgot about _L/_R, instead I focused on Alt. That's an interesting thought on your part, and I'll have to play with that tomorrow (tonight is for bed). The key here is that the pager coming up should be brief... and I'm beginning to rethink the "must come up before the direction key is pressed". You could make a wrapper script that uses xlib and does a `display.query_keymap()` to see if the keys are still being held down. Then if after a set time the key isn't still held, you might decide that the wrapper was invoked intentionally and should then call a function in fvwm to toggle your pager. It would take a little getting used to, as you'd train yourself to hold modifier keys for a brief pause when executing stuff other than toggling the pager, but it's not impossible. Another interesting idea - although I think I'm starting to lean toward having the pager pop up when the desk change is initiated, and then the only problem is how to allow multiple desk changes without releasing the Ctrl-Alt keys, and how to make sure the pager closes after releasing the keys. I had experimented with using the windows key to do something on its own when not being used as a modifier key, but I eventually discarded it. I posted about it to the fvwm forums, which can be found here: https://fvwmforums.org/phpBB3/viewtopic.php?f=6&t=2832#p14222 Hrm... I get all kinds of warnings when I access that page, and no information in any of the three posts. Is there another place to access the information? Regardless, thanks for all the good idea fodder... now I'll go dream about this, and play with it tomorrow. Regards, -dave signature.asc Description: PGP signature
Re: FVWM: Question regarding actions when modifier keys are held down/released
* Chris Siebenmann [2019-08-29 16:11 -0400]: I've searched the website, archives, wiki, and a number of configuration websites, and have been unable to find a way to cause an action to happen when a modifier key is held down and/or released. I'm running fvwm 2.6.8 on CentOS 7. It's possible that you'll be able to build an interface similar to what you want to do with the xcape program combined with some FVWM configuration tricks: https://github.com/alols/xcape Interesting: this might be useful, thank you! This gets you a way to get a preview, but it doesn't give you the kind of UI flow that you were interested in initially. You'd be doing 'tap something, look, hit Ctrl-Alt arrow key to act, tap to dismiss' or the like, instead of being able to start out by holding down Ctrl-Alt, waiting, and then continuing with another key. (Possibly you can contrive more FVWM functions and FvwmEvents settings and so on so that the pager is automatically dismissed after the desk changes, or just after a timeout time.) I think my "see the pager just before I decide which way to go" ideal may have to fall to the pragmatic "see the pager just after I decide which way to go so I can verify the direction, distance, etc. of the journey." I'll keep chugging away at it, though, because I think it'll be useful if I can get it to work. Regards, -dave signature.asc Description: PGP signature
Re: FVWM: Question regarding actions when modifier keys are held down/released
* Thomas Adam [2019-08-29 09:35 -0400]: On Wed, Aug 28, 2019 at 01:03:32PM -0400, Dave Weller-Fahy wrote: Greetings, I've searched the website, archives, wiki, and a number of configuration websites, and have been unable to find a way to cause an action to happen when a modifier key is held down and/or released. I'm running fvwm 2.6.8 on CentOS 7. This has always been historically tricky. At least it's not easy: if it were easy I'd feel really dumb for missing it. :) The use case is to have Ctrl-Alt-(up|down|left|right) change desks, but, if one wants, then holding Ctrl-Alt before pressing the arrow key will pop up the pager so you can see the desks to which you will be changing. A lot of the replies here have been utterly overkill, for what should be as simple as: FvwmPager -transient Thank you! I missed that bit entirely (especially about the "when button released"), however it seems that doesn't do what I'd expect. I think I misinterpreted "button" to mean "key or button", but in this case it seems to be just "button", as in "mouse button". I created a small function called ChangeToDesk with just the pager call (with -transient) and a GotoDesk command, and bound it to Ctrl-Alt-Down. #v+ Style FvwmPager StaysOnTop, Sticky Key Down A CM ChangeToDesk 1 # Function: ChangeToDesk $0 # # Change desks downward (if $0 = 1) or upward (if $0 = -1). DestroyFunc ChangeToDesk AddToFunc ChangeToDesk + I Test ($[infostore.DEBUG]) Echo "< ChangeToDesk" + I Module FvwmPager -transient PopUpPager 0 3 + I Test ($[infostore.DEBUG]) Echo "| ChangeToDesk - FvwmPager" + I GotoDesk $0 0 3 + I Test ($[infostore.DEBUG]) Echo "| ChangeToDesk - GotoDesk" #v- My attempts to use this configuration are below. 1. I hit Ctrl-Alt-down. 2. The pager pops up, and I change desktops. 3. No other arrow keys will cause the desktop to change again until I release Ctrl and Alt. 4. Releasing Ctrl and Alt does not cause the pager to close. 5. Hitting any other key causes the pager to be closed. This is closer, and with some other options I may be able to get closer still. Thanks again for the information about transient. Also, on a side note, is there any chance that fvwm3 will have more flexibility with regards to acting upon keyboard presses, holds, and releases because of the restructuring? Regards, -dave signature.asc Description: PGP signature
Re: FVWM: Question regarding actions when modifier keys are held down/released
> I've search the website, archives, wiki, and a number of configuration > websites, and have been unable to find a way to cause an action to > happen when a modifier key is held down and/or released. I'm running > fvwm 2.6.8 on CentOS 7. It's possible that you'll be able to build an interface similar to what you want to do with the xcape program combined with some FVWM configuration tricks: https://github.com/alols/xcape xcape generates keyboard events when you tap a key, including a modifier key. You can make this keyboard event be some weird key and modifier combination that you don't otherwise use and will never hit, and bind that to a FVWM function that summons and dismisses the pager. If you already have an existing FVWM keybinding that does this, so much the better. (For instance, I bind my left control to F5 with all of control, shift, and alt down, and then have a 'Key F5 A CSM ...' binding in my fvwmrc. This way xcape and that keybinding isn't stealing something that I ever want to actually use.) This gets you a way to get a preview, but it doesn't give you the kind of UI flow that you were interested in initially. You'd be doing 'tap something, look, hit Ctrl-Alt arrow key to act, tap to dismiss' or the like, instead of being able to start out by holding down Ctrl-Alt, waiting, and then continuing with another key. (Possibly you can contrive more FVWM functions and FvwmEvents settings and so on so that the pager is automatically dismissed after the desk changes, or just after a timeout time.) - cks
Re: FVWM: Question regarding actions when modifier keys are held down/released
On Wed, Aug 28, 2019 at 01:03:32PM -0400, Dave Weller-Fahy wrote: > Greetings, > > I've search the website, archives, wiki, and a number of configuration > websites, and have been unable to find a way to cause an action to > happen when a modifier key is held down and/or released. I'm running > fvwm 2.6.8 on CentOS 7. This has always been historically tricky. > The use case is to have Ctrl-Alt-(up|down|left|right) change desks, > but, if one wants, then holding Ctrl-Alt before pressing the arrow key > will pop up the pager so you can see the desks to which you will be > changing. A lot of the replies here have been utterly overkill, for what should be as simple as: FvwmPager -transient Kindly, Thomas
Re: FVWM: Question regarding actions when modifier keys are held down/released
On Thu, Aug 29, 2019 at 8:43 AM Dave Weller-Fahy wrote: > > On Thu, Aug 29, 2019 at 2:16 AM Martin Cermak wrote: > > On Wed 2019-08-28 13:03 , Dave Weller-Fahy wrote: > > > My goal is to have the following rules followed. > > > > > > Rules about keys being pressed and (possibly) held. > > > - If Ctrl-Alt are pressed ... > > > - and if no other keys are pressed within some period of time ... > > > - then pop up the pager > > > - and if other keys (such as arrow keys) are pressed ... > > > - then execute some other action > > > > > > Rules about keys being released. > > > - If Ctrl-Alt are released ... > > > - and if the pager is displayed ... > > > - then remove the pager > > > > > > The use case is to have Ctrl-Alt-(up|down|left|right) change desks, > > > > I have this setup too (as an option). But primarily I use > > Ctrl-Alt-(). This gives me a clear idea which > > of my 9 desks (arranged as a 3x3 matrix) I am switching to. > > Nothing visual involved. > > Thanks for the confirmation! I have the Ctrl-Alt-direction (or any other > arbitrary key combination to change desktops) working perfectly: I > should have been more clear on that. The thing I've not been able to > accomplish is getting the pager to pop up when keys are pressed and > then go away when those same keys are released. > > I was reaching the conclusion that what I wanted was not possible with > fvwm (at least, not possible without an external utility), but figured I > would check with the mailing list before giving up and looking for an > external utility to help. I may also try fvwm3 to see if what I want is > possible there. > You can bind a key to a modifier and set the unbound one as your modifier (Key Control_L A M Exec exec executable.nameor Key Alt_L A C Exec exec executable.name or ...) And that can still be used for some other action (Key T A CM Exec exec other-executable.name would still work, for example) but it will cause your executable to be executed even when you're just using the alt and control as modifiers. You could make a wrapper script that uses xlib and does a `display.query_keymap()` to see if the keys are still being held down. Then if after a set time the key isn't still held, you might decide that the wrapper was invoked intentionally and should then call a function in fvwm to toggle your pager. It would take a little getting used to, as you'd train yourself to hold modifier keys for a brief pause when executing stuff other than toggling the pager, but it's not impossible. I had experimented with using the windows key to do something on its own when not being used as a modifier key, but I eventually discarded it. I posted about it to the fvwm forums, which can be found here: https://fvwmforums.org/phpBB3/viewtopic.php?f=6&t=2832#p14222
Re: FVWM: Question regarding actions when modifier keys are held down/released
On Wednesday, 28. August 2019 17:03, Dave Weller-Fahy
wrote:
> Greetings,
>
> I've search the website, archives, wiki, and a number of configuration
> websites, and have been unable to find a way to cause an action to
> happen when a modifier key is held down and/or released. I'm running
> fvwm 2.6.8 on CentOS 7.
>
> My goal is to have the following rules followed.
>
> Rules about keys being pressed and (possibly) held.
>
> - If Ctrl-Alt are pressed ...
> - and if no other keys are pressed within some period of time ...
> - then pop up the pager
> - and if other keys (such as arrow keys) are pressed ...
> - then execute some other action
>
> Rules about keys being released.
>
> - If Ctrl-Alt are released ...
> - and if the pager is displayed ...
> - then remove the pager
>
> The use case is to have Ctrl-Alt-(up|down|left|right) change
> desks,
> but, if one wants, then holding Ctrl-Alt before pressing the
> arrow key
> will pop up the pager so you can see the desks to which you will
> be
> changing.
Hello,
I have too lasted for this feature at some point. Unfortunately, both Alt
and Ctrl are modifiers and by themselves cannot have a function. I was
thinking of calling IgnoreModifiers temporary in some function, but this
sentence in fvwm(1) man page disocouraged me: "If you issue it when your
fvwm session is already up and running the results are unpredictable."
But not all is lost - probably the closest match to this functionality is
the following setup which I currently use (purified <...> part of
configuration). Pager is configured under name/alias "LocalPager":
FvwmEvent (called as "Module FvwmEvent MainLoop") setup:
<...>
*MainLoop: new_desk f_ChangeDesk
*MainLoop: new_page f_ChangePage
<...>
DestroyFunc f_ChangePage
AddToFunc f_ChangePage
<...>
+ I Test (EnvMatch infostore.pageshowrootpager 1) f_ShowLocalPager
<...>
DestroyFunc f_ChangeDesk
AddToFunc f_ChangeDesk
+ I Test (EnvMatch infostore.pageshowrootpager 1) f_ShowLocalPager
DestroyFunc f_ShowLocalPager
AddToFunc f_ShowLocalPager
+ I Deschedule 131313
+ I All (Iconic, "LocalPager") State 0
+ I All (State 0, "LocalPager") Iconify off
+ I All (State 0, "LocalPager") Piperead "echo Move +$((
$[vp.width]/2-$[w.width]/2 ))p +5p"
+ I Schedule 1500 131313 All ("LocalPager", !HasPointer, !Iconic) Iconify on
+ I Schedule 3000 131313 All ("LocalPager", !HasPointer, !Iconic) Iconify on
+ I Schedule 5000 131313 All ("LocalPager", !HasPointer, !Iconic) Iconify on
+ I Schedule 8000 131313 All ("LocalPager", !HasPointer, !Iconic) Iconify on
+ I Schedule 1 131313 All ("LocalPager", !HasPointer, !Iconic) Iconify on
+ I All ("LocalPager") State 0 False
Now the keybindings part: when moving to another page or desk by ANY key
binding, LocalPager will popup on the screen (top center in my case) and
indicate where we are. If it doesn't get any attention, or it is left
alone after 3, 5, 8 or 10 seconds, it will dissapear. I'm using
Ctrl+(Up|Down|Left|Right) to move through pages of the current desk.
However, if Ctrl+Menu is pressed (which is close and handy to
Ctrl+cursor keys), Pager will move under the pointer for direct visual
selection with mouse, no matter if it is Iconic currently or not:
Silent Key Menu A C f_BringLocalPager
DestroyFunc f_BringLocalPager
AddToFunc f_BringLocalPager
+ I f_ShowLocalPager
+ I All (LocalPager) AnimatedMove m-5 m-6
One can even use my "double key binding" which has some Emacs-like feel,
and it prevents accidental activation while typing fast something. This
is a meta function, or "API" let's say.
# Execute what is in $1 - $X only a second time when
# function is called. Used to make double key bindings
# that will prevent accidental call while typing fast.
DestroyFunc f_DoubleBindKey
AddToFunc f_DoubleBindKey
+ I Test (EnvMatch infostore.dbk_$0 1) $[1-]
+ I Test (!EnvMatch infostore.dbk_$0 1) InfoStoreAdd dbk_$0 1
+ I Schedule 2000 InfoStoreRemove dbk_$0
That said, "Key Menu A C" can be than called as
f_DoubleBindKey loc_pager f_BringLocalPager
... where "loc_pager" is part for the short lived infostore variable
special only to this usage of the function.
Hope this helps a bit.
P. S.
You can find this and lot of other functions in My "NsCDE" project of FVWM-based
CDE on steroids on Github.
... one of the main causes of the fall of the Roman Empire
was that, lacking zero, they had no way to indicate
successful termination of their C programs.
-- Robert Firth
Re: FVWM: Question regarding actions when modifier keys are held down/released
On Thu, Aug 29, 2019 at 2:16 AM Martin Cermak wrote: > On Wed 2019-08-28 13:03 , Dave Weller-Fahy wrote: > > My goal is to have the following rules followed. > > > > Rules about keys being pressed and (possibly) held. > > - If Ctrl-Alt are pressed ... > > - and if no other keys are pressed within some period of time ... > > - then pop up the pager > > - and if other keys (such as arrow keys) are pressed ... > > - then execute some other action > > > > Rules about keys being released. > > - If Ctrl-Alt are released ... > > - and if the pager is displayed ... > > - then remove the pager > > > > The use case is to have Ctrl-Alt-(up|down|left|right) change desks, > > I have this setup too (as an option). But primarily I use > Ctrl-Alt-(). This gives me a clear idea which > of my 9 desks (arranged as a 3x3 matrix) I am switching to. > Nothing visual involved. Thanks for the confirmation! I have the Ctrl-Alt-direction (or any other arbitrary key combination to change desktops) working perfectly: I should have been more clear on that. The thing I've not been able to accomplish is getting the pager to pop up when keys are pressed and then go away when those same keys are released. I was reaching the conclusion that what I wanted was not possible with fvwm (at least, not possible without an external utility), but figured I would check with the mailing list before giving up and looking for an external utility to help. I may also try fvwm3 to see if what I want is possible there. Regards, -dave
Re: FVWM: Override Vector Colorset
"B. [simoN] Karhan" writes: > Hi all, > I was wondering if there is a way to explicitly set (i.e. override the > default > inheritance) of the colorset used for the segment-drawing in the Vector style? Nope, don't think so. -- Dan Espen
Re: FVWM: howto conditionally add menu entries?
On 8/3/19, hw wrote: > Dan Espen writes: >> Try PipeRead. Use shell, Perl, Python, your choice. > > How would that work? I'm trying to make a kinda dynamic configuration, > meaning that there is supposed to be a basic configuration accompanied > by optional configurations. [...] > If I was to write some program to create the root menu, I would always > need to modify the program when new optional configurations are to be > added so it could recognize them. That is something I would prefer to > avoid. [...] > Unfortunately, that raises the question how I can make it so that the > entries in the root menu appear in a desired order and with the title at > the top rather than somewhere in between the entries ... Is there a way > to sort menu entries once no more entries are being added? > > I'm probably not the first one to try this. It can't be this difficult, > can it? I have long thought about menu stuff, too. What I wanted for me is a menu that allows me to browse apps and files, the latter also categorywise (i.e. all, or only text/graphics/multimedia, or on extension). And this menu must include recent accesses nicely presented, so one does not need to search for long. Kind of self-sorting menus that do not make the need of sorting arise. Imho PipeRead and some script language is the way to go. You can look at what I use on https://github.com/kernschmelze/meowpurr. Actually two programs, reads the .desktop files' information and is usually started once FVWM starts up, does the menu generation when called by PipeRead. It is still WIP - the integration/merging of the Freedesktop Recent file/URL data is still in progress - and there are some small bugs ofc. When I got time I also will add the MenuColor directive that @ThomasAdam recently implemented (big kudos to Thomas!) So if you want to see how to dynamically generate complex nested menu structures, maybe take a look at that, or even give it a try. You might like Its self-sorting features, which it adapts depending on your usage.
Re: FVWM: howto conditionally add menu entries?
Stuart Longland writes:
> On 3/8/19 1:56 pm, hw wrote:
>> If I was to write some program to create the root menu, I would always
>> need to modify the program when new optional configurations are to be
>> added so it could recognize them. That is something I would prefer to
>> avoid.
>
> Well no, the program will need to store its state somewhere, and have
> that state updated so that next time it is called by FVWM, its output
> reflects the new state.
The script may or may not have to save state, it could just be looking
at data. Here is a fragment where a perl subroutine is given a
menu title and a command, it looks at the command and if the command
can be found (using "which") it goes on to add the menu entry:
# arg 1, the menu title
# arg 2-n, the command
sub Add {
($desc,$func,$accel)=@_;
($f1, $f2)=split(" ",$func);
if ( $f1 eq "Exec" ) {
$x=`which $f2 2>&1`;
$rc=$?;
if ( $rc != 0 ) {
# print "cant find &f2, rc $rc, cmd o/p $x\n";
return;
}
}
...
--
Dan Espen
Re: FVWM: howto conditionally add menu entries?
hw writes:
> Dan Espen writes:
>
>> hw writes:
>>
>>> Hi,
>>>
>>> how can I conditionally add menu entries? For example:
>>>
>>>
>>> [...]
>>> Read fvwm-functions-starters-common.fvwm
>>> Read fvwm-functions-starters-games.fvwm quiet
>>> Read fvwm-functions-starters-local.fvwm quiet
>>> [...]
>>>
>>>
>>> DestroyMenu Main
>>> AddToMenu Main
>>> + "Main"Title
>>> + "Common" PopUp Common
>>> + "Games" PopUp Games
>>> + "Local" PopUp Local
>>>
>>>
>>> I want the "Common" and "Games" entries in the menu only when the files
>>> defining them (like fvwm-functions-starters-games.fvwm) can be read.
>>>
>>> I thought I could use something like
>>>
>>> DestroyMenu Main
>>> AddToMenu Main
>>> + Test (f fvwm-functions-starters-games.fvwm) AddToMenu Main "Games" PopUp
>>> Games
>>>
>>>
>>> and that doesn't work in that the menu entry doesn't show up regardless
>>> of the existance of the file. There doesn't seem to be a way to test
>>> whether something is defined or not; if there was, I could test if a
>>> menu has been defined and only then add it to another menu.
>>
>> Try PipeRead. Use shell, Perl, Python, your choice.
>
> How would that work? I'm trying to make a kinda dynamic configuration,
> meaning that there is supposed to be a basic configuration accompanied
> by optional configurations. An optional configuration needs to make an
> entry for its sub-menu into the root menu if the optional configuration
> is available.
>
> If I was to write some program to create the root menu, I would always
> need to modify the program when new optional configurations are to be
> added so it could recognize them. That is something I would prefer to
> avoid.
>
> Hm, having that said, I can make it so that the optional configurations
> add themselves to the root menu. All they need is a line like
>
> AddToMenu Main "Games" PopUp Games
>
> Unfortunately, that raises the question how I can make it so that the
> entries in the root menu appear in a desired order and with the title at
> the top rather than somewhere in between the entries ... Is there a way
> to sort menu entries once no more entries are being added?
>
> I'm probably not the first one to try this. It can't be this difficult,
> can it?
No, it's not difficult at all.
I have a number of scripts that work with PipeRead, here is a very short
one:
#!/usr/bin/perl
print "DestroyFunc LockTerm\n";
$_ = `uname -s`;
chomp;
if ( /Linux/ ) {
print "AddToFunc LockTerm I Exec exec gnome-screensaver-command -l\n";
exit 0;
}
print "AddToFunc LockTerm I Exec exec myscreensaver -lock\n";
This creates a "LockTerm" function which is different when running on Linux.
(I used the same configuration file on Solaris systems.)
Doing sorts, file existence tests, just about anything should be
obvious. Just only print commands when you want to generate Fvwm
commands.
If you look at fvwm-menu-desktop you'll see how far you can go with
this.
--
Dan Espen
Re: FVWM: howto conditionally add menu entries?
On 3/8/19 1:56 pm, hw wrote: > If I was to write some program to create the root menu, I would always > need to modify the program when new optional configurations are to be > added so it could recognize them. That is something I would prefer to > avoid. Well no, the program will need to store its state somewhere, and have that state updated so that next time it is called by FVWM, its output reflects the new state. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: FVWM: howto conditionally add menu entries?
Dan Espen writes: > hw writes: > >> Hi, >> >> how can I conditionally add menu entries? For example: >> >> >> [...] >> Read fvwm-functions-starters-common.fvwm >> Read fvwm-functions-starters-games.fvwm quiet >> Read fvwm-functions-starters-local.fvwm quiet >> [...] >> >> >> DestroyMenu Main >> AddToMenu Main >> + "Main"Title >> + "Common" PopUp Common >> + "Games" PopUp Games >> + "Local" PopUp Local >> >> >> I want the "Common" and "Games" entries in the menu only when the files >> defining them (like fvwm-functions-starters-games.fvwm) can be read. >> >> I thought I could use something like >> >> DestroyMenu Main >> AddToMenu Main >> + Test (f fvwm-functions-starters-games.fvwm) AddToMenu Main "Games" PopUp >> Games >> >> >> and that doesn't work in that the menu entry doesn't show up regardless >> of the existance of the file. There doesn't seem to be a way to test >> whether something is defined or not; if there was, I could test if a >> menu has been defined and only then add it to another menu. > > Try PipeRead. Use shell, Perl, Python, your choice. How would that work? I'm trying to make a kinda dynamic configuration, meaning that there is supposed to be a basic configuration accompanied by optional configurations. An optional configuration needs to make an entry for its sub-menu into the root menu if the optional configuration is available. If I was to write some program to create the root menu, I would always need to modify the program when new optional configurations are to be added so it could recognize them. That is something I would prefer to avoid. Hm, having that said, I can make it so that the optional configurations add themselves to the root menu. All they need is a line like AddToMenu Main "Games" PopUp Games Unfortunately, that raises the question how I can make it so that the entries in the root menu appear in a desired order and with the title at the top rather than somewhere in between the entries ... Is there a way to sort menu entries once no more entries are being added? I'm probably not the first one to try this. It can't be this difficult, can it?
Re: FVWM: howto conditionally add menu entries?
Thomas Adam writes: > On Fri, 2 Aug 2019 at 20:34, hw wrote: >> DestroyMenu Main >> AddToMenu Main >> + Test (f fvwm-functions-starters-games.fvwm) AddToMenu Main "Games" PopUp >> Games > > That's not going to work, because when the '+' command is run for a > menu-context, the menu code doesn't understand/execute things like the > 'Test' command. > > In your case, you need to wrap the menu definitions in a function: > > DestroyFunc foo > AddToFunc. foo > + Test () AddToMenu . AddToFunc StartFunction + Test (F fvwm-functions-starters-games.fvwm) AddToMenu Main "Games" PopUp Games ... doesn't work However, I can't tell if the test is successful or not. Yet AddToFunc StartFunction + AddToMenu Main "Games" PopUp Games ... doesn't work, either. Otherwise, how would I make sure that the function that adds the menu entry is being exectued only once, and at the right time?
Re: FVWM: howto conditionally add menu entries?
On Fri, 2 Aug 2019 at 20:34, hw wrote: > DestroyMenu Main > AddToMenu Main > + Test (f fvwm-functions-starters-games.fvwm) AddToMenu Main "Games" PopUp > Games That's not going to work, because when the '+' command is run for a menu-context, the menu code doesn't understand/execute things like the 'Test' command. In your case, you need to wrap the menu definitions in a function: DestroyFunc foo AddToFunc. foo + Test () AddToMenu . -- Thomas Adam
Re: FVWM: howto conditionally add menu entries?
hw writes: > Hi, > > how can I conditionally add menu entries? For example: > > > [...] > Read fvwm-functions-starters-common.fvwm > Read fvwm-functions-starters-games.fvwm quiet > Read fvwm-functions-starters-local.fvwm quiet > [...] > > > DestroyMenu Main > AddToMenu Main > + "Main"Title > + "Common" PopUp Common > + "Games" PopUp Games > + "Local" PopUp Local > > > I want the "Common" and "Games" entries in the menu only when the files > defining them (like fvwm-functions-starters-games.fvwm) can be read. > > I thought I could use something like > > DestroyMenu Main > AddToMenu Main > + Test (f fvwm-functions-starters-games.fvwm) AddToMenu Main "Games" PopUp > Games > > > and that doesn't work in that the menu entry doesn't show up regardless > of the existance of the file. There doesn't seem to be a way to test > whether something is defined or not; if there was, I could test if a > menu has been defined and only then add it to another menu. Try PipeRead. Use shell, Perl, Python, your choice. -- Dan Espen
Re: FVWM: meaning of '+ I', '+ M', '+ D'?
Dan Espen writes: > hw writes: > >> Hi, >> >> what is the meaning of '+ I', '+ M', '+ D' when adding stuff to >> functions or menues? That doesn't seem to be explained in the man page >> ... >> >> Why does '+ I' work and '+I' doesn't? > > The description of plus from the man page: > > + > Used to continue adding to the last specified decor, function or menu. > See the discussion for AddToDecor, AddToFunc, and AddToMenu. > > So this lets you do: > > AddToFunc ExecWarp > + I $1 > + I Wait $0 > + I Warp $0 > > which is the same as: > > AddToFunc ExecWarp I $1 > AddToFunc ExecWarp I Wait $0 > AddToFunc ExecWarp I Warp $0 > > The reason "+I" is invalid, is because the "+" is a command and > must be space separated from it's arguments. > > The letters are explained in the description of AddToFunc: > > The letter before the action tells what kind of action triggers the > command which follows it. 'I' stands for "Immediate", and is executed as > soon as the function is invoked. 'M' stands for "Motion", i.e. if the > user starts moving the mouse. 'C' stands for "Click", i.e., if the user > presses and releases the mouse button. 'H' stands for "Hold", i.e. if > the user presses a mouse button and holds it down for more than > ClickTime milliseconds. 'D' stands for "Double-click". The action 'I' > causes an action to be performed on the button-press, if the function is > invoked with prior knowledge of which window to act on. > > These letters are only used in functions, menus have a different syntax. Thanks!
Re: FVWM: meaning of '+ I', '+ M', '+ D'?
hw writes: > Hi, > > what is the meaning of '+ I', '+ M', '+ D' when adding stuff to > functions or menues? That doesn't seem to be explained in the man page > ... > > Why does '+ I' work and '+I' doesn't? The description of plus from the man page: + Used to continue adding to the last specified decor, function or menu. See the discussion for AddToDecor, AddToFunc, and AddToMenu. So this lets you do: AddToFunc ExecWarp + I $1 + I Wait $0 + I Warp $0 which is the same as: AddToFunc ExecWarp I $1 AddToFunc ExecWarp I Wait $0 AddToFunc ExecWarp I Warp $0 The reason "+I" is invalid, is because the "+" is a command and must be space separated from it's arguments. The letters are explained in the description of AddToFunc: The letter before the action tells what kind of action triggers the command which follows it. 'I' stands for "Immediate", and is executed as soon as the function is invoked. 'M' stands for "Motion", i.e. if the user starts moving the mouse. 'C' stands for "Click", i.e., if the user presses and releases the mouse button. 'H' stands for "Hold", i.e. if the user presses a mouse button and holds it down for more than ClickTime milliseconds. 'D' stands for "Double-click". The action 'I' causes an action to be performed on the button-press, if the function is invoked with prior knowledge of which window to act on. These letters are only used in functions, menus have a different syntax. -- Dan Espen
Re: FVWM: Bindings and/or mouse clicks going wonky
Hi Jamie, I feel rather sheepish now. I recall Thomas Adam telling me the same thing on this list, that FVWM + numlock do not play well together, something like 10 or so years ago. As soon as I read your message, I knew that was going to be the answer, and sure enough, it seems to be solved. Thanks so much for the reply. On Tue, 9 Jul 2019 at 09:06, Jaimos Skriletz wrote: > > Most likely your numlock key is on, there are instructions on how to > ignore this modifier. > > http://www.fvwm.org/documentation/faq/#a-few-minutes-after-fvwm-is-started-my-keyboard-and-mouse-bindings-stop-working--what-can-i-do > > jaimos > > On Mon, Jul 8, 2019 at 3:43 PM Jake Moe wrote: > > > > Hi all, > > > > I've done a new Gentoo install, and put FVWM on it. Started putting a > > config on it and using it. It worked fine for a little while, but > > after a while, my menu seems to have reverted back to the system > > default menu. If I open a console and tell it to re-read my menu > > config, it doesn't throw any errors, but the menu doesn't change, > > either. Also, while this is happening, my title bar bindings stop > > working. The buttons are still there, but clicking them does nothing. > > > > While looking into it, I came across the FvwmDebug module, but when I > > load that up, nothing gets output to the console, and if I try to > > output to a file, no file gets created. > > > > I'm not sure where to continue troubleshooting this one. If the > > bindings were disappearing or getting overwrtten somehow, I'd expect > > the title bar buttons to go away, and the root window menu binding to > > just stop working, not show the default/system menu. Does anyone know > > why this might be happening, or be able to offer guidance on where to > > look for signs of trouble? > > > > -- > > Cheers, > > > > Jake > > -- Cheers, Jake
Re: FVWM: Bindings and/or mouse clicks going wonky
Most likely your numlock key is on, there are instructions on how to ignore this modifier. http://www.fvwm.org/documentation/faq/#a-few-minutes-after-fvwm-is-started-my-keyboard-and-mouse-bindings-stop-working--what-can-i-do jaimos On Mon, Jul 8, 2019 at 3:43 PM Jake Moe wrote: > > Hi all, > > I've done a new Gentoo install, and put FVWM on it. Started putting a > config on it and using it. It worked fine for a little while, but > after a while, my menu seems to have reverted back to the system > default menu. If I open a console and tell it to re-read my menu > config, it doesn't throw any errors, but the menu doesn't change, > either. Also, while this is happening, my title bar bindings stop > working. The buttons are still there, but clicking them does nothing. > > While looking into it, I came across the FvwmDebug module, but when I > load that up, nothing gets output to the console, and if I try to > output to a file, no file gets created. > > I'm not sure where to continue troubleshooting this one. If the > bindings were disappearing or getting overwrtten somehow, I'd expect > the title bar buttons to go away, and the root window menu binding to > just stop working, not show the default/system menu. Does anyone know > why this might be happening, or be able to offer guidance on where to > look for signs of trouble? > > -- > Cheers, > > Jake >
Re: FVWM: Controlling initial size of a "gThumb" window
Stephen, On Friday, 2019-06-21 15:29:05 -0400, you wrote: > ... > Style gThumb NoPPosition, InitialMapCommand Resize 20 20 I modified this to Style gThumb InitialMapCommand ResizeMove 56 93 -0p 6p and, as I've already let everybody know, it worked. So I tried the same with "evince": Style Evince InitialMapCommand ResizeMove 56 93 0p 6p and that worked, too. But when I opened a PDF annotation from within an "evince" window, the sub-window was positioned and sized the same as the main window. So I did Style Evince InitialMapCommand Current (!Transient) ResizeMove 56 93 0p 6p which solved the latter problem but at the same time stubbornly posit- ioned the main window at "20p 0p". I ended up splitting the single "Re- sizeMove" command into two: Style Evince InitialMapCommand Current (!Transient) Resize 56 93 Style Evince PositionPlacement 0p 6p This worked, but what's going on here? Why is "ResizeMove" not posit- ioning correctly when a conditional is involved? Finally, I also experimented with "scantailor". I ended up with Style scantailor InitialMapCommand Current (!Transient, !URxvt) \ Resize frame 100 93 Style scantailor NoPPosition, PositionPlacement 0p 6p because without the "Current (...)" clause again sub-windows were sized the same as the main window, and without the "!URxvt" the terminal wind- ow from which I started "scantailor" was unconditionally resized, too (does anybody have any explanation for THIS?). But what's worse: even with the "NoPPosition" (and also with "FixedPPosition") in effect each call to "scantailor" placed the window exactly 15p lower than the pre- ceding call. And I have not yet found a remedy for this. Yes, there is a file ~/.config/scantailor-advanced/scantailor-advanced.ini and yes, it contains a line nonMaximizedGeometry="@ByteArray(...)" But removing this line causes a default size to be used for the window, upon terminating "scantailor" a new "nonMaximizedGeometry=" will be add- ed to the "*.ini" file, and each following call to "scantailor" will ag- ain place the window 15p lower than the preceding call. Any takers? Sincerely, Rainer PS: Before I forget: $ fvwm -V fvwm 2.6.5 compiled on Jan 26 2016 at 23:13:57 with support for: ReadLine, RPlay, Stroke, XPM, PNG, SVG, Shape, XShm, SM, Bidi text, Xinerama, XRender, XCursor, XFT, NLS $
Re: FVWM: Controlling initial size of a "gThumb" window
On Mon, 24 Jun 2019 07:06:47 +0200 Michael Großer wrote: > > Do you really use the right distribution (Ubuntu) for your need ? > > BR, Bob > > > > Looks like Gentoo could be the distribution of your choice :-) > No, it's Fedora :-)
Re: FVWM: Controlling initial size of a "gThumb" window
Bob Marcan wrote: > On Sun, 23 Jun 2019 19:13:19 +0200 > Dr Rainer Woitok wrote: > >> Dan, >> >> On Thursday, 2019-06-20 12:12:49 -0400, you wrote: > ... >> >> No. There are already way too many packages I install from source be- >> cause I really need more recent versions than Ubuntu provides or because >> I have to patch them before compiling. So as long as I can solve minor >> anoyances by just adapting my "fvwm" configuration, I prefer that over >> compiling from source. >> >> Sincerely, >> Rainer > > Do you really use the right distribution (Ubuntu) for your need ? > BR, Bob > > Looks like Gentoo could be the distribution of your choice :-)
Re: FVWM: Controlling initial size of a "gThumb" window
On Sun, 23 Jun 2019 19:13:19 +0200 Dr Rainer Woitok wrote: > Dan, > > On Thursday, 2019-06-20 12:12:49 -0400, you wrote: ... > > No. There are already way too many packages I install from source be- > cause I really need more recent versions than Ubuntu provides or because > I have to patch them before compiling. So as long as I can solve minor > anoyances by just adapting my "fvwm" configuration, I prefer that over > compiling from source. > > Sincerely, > Rainer Do you really use the right distribution (Ubuntu) for your need ? BR, Bob
Re: FVWM: Controlling initial size of a "gThumb" window
Stephen, On Friday, 2019-06-21 15:29:05 -0400, you wrote: > ... > Style gThumb NoPPosition, InitialMapCommand Resize 20 20 > > The motivation for NoPPosition is so it wont be able to move itself to > it's remembered position at 0 0 when it was fullscreen and as for the > Resize you'd probably want to pick a different value. Now we're on target! I wasn't aware of the "InitialMapCommand" command. This works! :-D Tanks a lot. Sincerely, Rainer
Re: FVWM: Controlling initial size of a "gThumb" window
Dan, On Thursday, 2019-06-20 12:12:49 -0400, you wrote: > ... > Try one of these: > > http://ftp.acc.umu.se/pub/GNOME/sources/gthumb/ > > versions 1.105 to 3.8. No. There are already way too many packages I install from source be- cause I really need more recent versions than Ubuntu provides or because I have to patch them before compiling. So as long as I can solve minor anoyances by just adapting my "fvwm" configuration, I prefer that over compiling from source. Sincerely, Rainer
Re: FVWM: Controlling initial size of a "gThumb" window
On Thu, Jun 20, 2019 at 12:13 PM Dan Espen wrote: > > Dr Rainer Woitok writes: > > > Dan, > > > > On Thursday, 2019-06-20 08:43:02 -0400, you wrote: > > > >> ... > >> I don't think Fvwm will do that, especially for an application going > >> full screen. If the application was in a window, you might be able to > >> use Fvwm resize. > > > > That's what I've feared ... :-( > > Full screen windows are commonly called override-redirect or unmanaged > windows. > > >> However, it seemed to me that it was pretty straight forward to > >> configure gthumb not to use full screen. > > > > No. The "gthumb" you fought with was version 3.6.2, mine is version > > 3.4.3. Neither is there any point where right-clicking produces a "Re- > > size" option, does removing ~/.config/gthumb/" or pressing the Escape > > key have the effect you described, nor is there a "Fullscreen" option > > under "Settings -> Browser". Bummer. > > Try one of these: > > http://ftp.acc.umu.se/pub/GNOME/sources/gthumb/ > > versions 1.105 to 3.8. > > -- > Dan Espen > I wasn't able to get it to behave in the same way, but the following may work: Style gThumb NoPPosition, InitialMapCommand Resize 20 20 The motivation for NoPPosition is so it wont be able to move itself to it's remembered position at 0 0 when it was fullscreen and as for the Resize you'd probably want to pick a different value.
Re: FVWM: Controlling initial size of a "gThumb" window
Dr Rainer Woitok writes: > Dan, > > On Thursday, 2019-06-20 08:43:02 -0400, you wrote: > >> ... >> I don't think Fvwm will do that, especially for an application going >> full screen. If the application was in a window, you might be able to >> use Fvwm resize. > > That's what I've feared ... :-( Full screen windows are commonly called override-redirect or unmanaged windows. >> However, it seemed to me that it was pretty straight forward to >> configure gthumb not to use full screen. > > No. The "gthumb" you fought with was version 3.6.2, mine is version > 3.4.3. Neither is there any point where right-clicking produces a "Re- > size" option, does removing ~/.config/gthumb/" or pressing the Escape > key have the effect you described, nor is there a "Fullscreen" option > under "Settings -> Browser". Bummer. Try one of these: http://ftp.acc.umu.se/pub/GNOME/sources/gthumb/ versions 1.105 to 3.8. -- Dan Espen
Re: FVWM: Controlling initial size of a "gThumb" window
Stephen, On Thursday, 2019-06-20 09:03:48 -0400, you wrote: > ... > Perhaps try the style option NoPPosition on the window in question? I do not want to control the position but rather the size. And at least on my system man fvwm | grep -B3 PSize only turn up "FixedPSize" and "VariablePSize" as Boolean options. Thus they can't be used to SET an initial size. Sincerely, Rainer
Re: FVWM: Controlling initial size of a "gThumb" window
Dan, On Thursday, 2019-06-20 08:43:02 -0400, you wrote: > ... > I don't think Fvwm will do that, especially for an application going > full screen. If the application was in a window, you might be able to > use Fvwm resize. That's what I've feared ... :-( > However, it seemed to me that it was pretty straight forward to > configure gthumb not to use full screen. No. The "gthumb" you fought with was version 3.6.2, mine is version 3.4.3. Neither is there any point where right-clicking produces a "Re- size" option, does removing ~/.config/gthumb/" or pressing the Escape key have the effect you described, nor is there a "Fullscreen" option under "Settings -> Browser". Bummer. Sincerely, Rainer
Re: FVWM: Controlling initial size of a "gThumb" window
On Thu, Jun 20, 2019 at 8:44 AM Dan Espen wrote: > > Dr Rainer Woitok writes: > > > Greetings, > > > > On Wednesday, 2019-06-19 14:32:06 -0700, Ronald F. Guilmette wrote: > > > >> In message , > >> Dan Espen wrote: > >> > >> >So, I'm afraid I can't duplicate your issue but I can see gthumb > >> >is really buggy. > >> > >> I'm not sure that's a proper assumption. > >> ... > > > > Sorry, it was not my intention to fire up a discussion about "gthumb". > > And in particular not on this list. It was just the unwanted behaviour > > of this particular programme which made me look for a way to counter it. > > Sorry, was trying to explain why I could only do so much testing. > > > So let me rephrase my request without mentioning a particular programme: > > > > Is there a way to tell "fvwm" to open a window using a particular init- > > ial size? I'm aware of > > > >Style xxx PositionPlacement HOR VERT > > > > but I'm interested in specifying exactly the other two parameters from a > > normal "WIDTHxHEIGHT+HOR+VERT" X11 geometry specification. And I only > > want to specify an INITIAL size, the user should be able to later manu- > > ally change the window size. > > I don't think Fvwm will do that, especially for an application going > full screen. If the application was in a window, you might be able to > use Fvwm resize. > > However, it seemed to me that it was pretty straight forward to > configure gthumb not to use full screen. > > -- > Dan Espen > Perhaps try the style option NoPPosition on the window in question?
Re: FVWM: Controlling initial size of a "gThumb" window
Dr Rainer Woitok writes: > Greetings, > > On Wednesday, 2019-06-19 14:32:06 -0700, Ronald F. Guilmette wrote: > >> In message , >> Dan Espen wrote: >> >> >So, I'm afraid I can't duplicate your issue but I can see gthumb >> >is really buggy. >> >> I'm not sure that's a proper assumption. >> ... > > Sorry, it was not my intention to fire up a discussion about "gthumb". > And in particular not on this list. It was just the unwanted behaviour > of this particular programme which made me look for a way to counter it. Sorry, was trying to explain why I could only do so much testing. > So let me rephrase my request without mentioning a particular programme: > > Is there a way to tell "fvwm" to open a window using a particular init- > ial size? I'm aware of > >Style xxx PositionPlacement HOR VERT > > but I'm interested in specifying exactly the other two parameters from a > normal "WIDTHxHEIGHT+HOR+VERT" X11 geometry specification. And I only > want to specify an INITIAL size, the user should be able to later manu- > ally change the window size. I don't think Fvwm will do that, especially for an application going full screen. If the application was in a window, you might be able to use Fvwm resize. However, it seemed to me that it was pretty straight forward to configure gthumb not to use full screen. -- Dan Espen
Re: FVWM: Controlling initial size of a "gThumb" window
Greetings, On Wednesday, 2019-06-19 14:32:06 -0700, Ronald F. Guilmette wrote: > In message , > Dan Espen wrote: > > >So, I'm afraid I can't duplicate your issue but I can see gthumb > >is really buggy. > > I'm not sure that's a proper assumption. > ... Sorry, it was not my intention to fire up a discussion about "gthumb". And in particular not on this list. It was just the unwanted behaviour of this particular programme which made me look for a way to counter it. So let me rephrase my request without mentioning a particular programme: Is there a way to tell "fvwm" to open a window using a particular init- ial size? I'm aware of Style xxx PositionPlacement HOR VERT but I'm interested in specifying exactly the other two parameters from a normal "WIDTHxHEIGHT+HOR+VERT" X11 geometry specification. And I only want to specify an INITIAL size, the user should be able to later manu- ally change the window size. Sincerely, Rainer
Re: FVWM: Controlling initial size of a "gThumb" window
In message , Dan Espen wrote: >So, I'm afraid I can't duplicate your issue but I can see gthumb >is really buggy. I'm not sure that's a proper assumption. Gthumb works well enough for me on both Ubuntu (18.04) and FreBSD (12.0). No crashes at all so far. And anyway, even if the thing crashes, it might not be the thing itself. I reported a bug to the FreeBSD folks recently where Opera was crashing every time I tried to opne the print menu: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238413 It turned out that the actual bug was in a thing called libproxy that it was using. (The version number for that library is currently 0.4.15 :-)
Re: FVWM: Controlling initial size of a "gThumb" window
Dr Rainer Woitok writes: > Greetings, > > even though I'm using Xubuntu 16.04 I nevertheless use Gnome's "gthumb" > as image viewer. However, I cannot find a way to keep "gthumb" from op- > ening a fullscreen window when fired up. > > So I ran "man fvwm" and checked the stlye options, but "MaxWindowSize" > isn't really what I want, because it prevents me from later manually in- > creasing the window. Is there some way to just specify an INITIAL wind- > ow size or even window geometry? I'm on Fedora. I installed gthumb and tried to start it up without any input files. Core dump. So, I gave it an input png file. It started up in a window. I clicked the big square in the bogus extra window options bar and got a screen sized window. I was able to right click and select resize to make the window smaller. Then I looked in settings/browser and selected open image in full screen. Then I quit and restarted. Rather I attempted to restart, now even with an image on the command line gthumb crashes on start up. So, I removed the user configuration it created: rm -rf .config/gthumb Now it crashes on startup. Nope, another test, now it starts and it starts with the image in full screen mode. So, I can hit escape to get a regular size window. Now I click on settings/browser and turn off full screen. No joy, back to crashing on start up. So, I'm afraid I can't duplicate your issue but I can see gthumb is really buggy. Starting from a command line, I see various error messages, this is one recent one: home> gthumb me.jpg (gthumb:23283): GLib-ERROR **: 08:48:49.891: gmem.c:170: failed to allocate 140737488355328 bytes Trace/breakpoint trap (core dumped) home> gthumb -v gthumb 3.6.2, Copyright © 2001-2010 Free Software Foundation, Inc. Hopefully, this post shows how to clear an existing set of options or if you can get gthumb started, you can see where to turn off full screen. Damn thing just started again for me. I'm going to uninstall it. -- Dan Espen
[SOLVED] Re: FVWM: Strange problem with localhost
Ok, so, I deleted the line setenv DISPLAY localhost:0.0 from my ~/.login file and then exited X, logged out (console) and then logged back in (console again) and checked. At that point, the environment variable DISPLAY wasn't set at all. I then started up X (via xinit) as I am accustomed to doing, which in turn started up fvwm, and I then got an xterm window and checked again. Now I have the following: DISPLAY=:0 Now all of the following are working happily: firefox opera chrome xpdf evince gimp vlc So everybody is happy, it seems, and I am back in the saddle again. My thanks to Stephen Dennison for taking me right to the heart of the matter. (It serves me right. This is the kind of thing that happens when/if one neglects to upgrade things for years and years. What can I say? I was busy. :-) Regards, rfg
Re: FVWM: Strange problem with localhost
In message <20190617205926.mwzkffi363jut...@bennettconstruction.us>, chris wrote: >> 127.0.0.1 localhost localhost.tristatelogic.com > > >Having localhost.tristatelogic.com after localhost seems to be wrong to >me. Forgive me if I am mistaken. This reminds me of that old saying... "In the land of the blind, the one-eyed man is king." In this context, I am just one of the blind men, groping my way around... and I am neither too proud nor too ashamed to admit it. In short, I have no idea if you are right or wrong, or if the content of my /etc/hosts file even makes much bloody difference to anything, in practice. (I have a question pending abuot that very issue on the freebsd-net mailing list. It appears to me that manual edits of my /etc/hosts file aren't even having any effect at all. I'm trying to find out why.) >Anything I can learn is a plus to me! Ditto. Regards, rfg
Re: FVWM: Strange problem with localhost
In message , Stephen Dennison wrote: >There's probably nothing wrong with localhost per se... OK. I guess that's the good news. >> Basically, once I start up X and fvwm, I see that all of my xterm >> windows are automagically inheriting the following environment variable >> and the value shown: >How did you start up "X"? Which "X" are you running? What OS and are >you using a login manager, display manager, etc? I am using: FreeBSD 11.0-RELEASE xorg-7.7_3 (installed from packages) I start X by just logging in (console) and then running xinit. I have a (slightly) personally tailored .xinitrc file. I am *not* using any X login manager. >Perhaps you inadvertently set the value of DISPLAY in one of your dot >files and that's the actual problem? O! Good lord! Good catch! I just now checked, and yes, the ancient .login file (used by my prefered shell, tsch) does indeed contain: setenv DISPLAY localhost:0.0 I probably put that in there 10+ years ago to solve some problem and then never looked at it ever again since. So I just simply need to remove that?? Marvelous. I'll try it. >> I futzed around trying to fix this problem for awhile and I managed to >> discover that if I manually set DISPLAY instead to just :0.0 then suddenly >> all my X applications start to work again. >Right, because it stops trying to use the TCP transport and uses local instead. I see. I am probably stating the obvious, but for a person like me who is not at all steeped in the current machinations and/or machanisms of the X server, this was/is rather entirely non-obvious. >> Here is the output from the command "getent hosts localhost" on the system >> in question: >> >> ::1 localhost >> 127.0.0.1 localhost localhost.tristatelogic.com >> >> >> What am I doing wrong? Why doesn't the default value of localhost:0.0 >> for DISPLAY work just as well as :0.0 ? >In summary, localhost:0.0 says to use the TCP transport for the >connection instead of local and your system is probably not listening >on tcp. So, just out of curiosity, when did that change? (I must sheepishly admit that I haven't updated this system in years, so it might even have changed 6 ofr more years ago. Obviously, I didn't get the memo. :-)
Re: FVWM: Strange problem with localhost
On Mon, Jun 17, 2019 at 01:08:43PM -0700, Ronald F. Guilmette wrote: > Here is the output from the command "getent hosts localhost" on the system > in question: > > ::1 localhost > 127.0.0.1 localhost localhost.tristatelogic.com > > > What am I doing wrong? Why doesn't the default value of localhost:0.0 > for DISPLAY work just as well as :0.0 ? > > 127.0.0.1 localhost localhost.tristatelogic.com Having localhost.tristatelogic.com after localhost seems to be wrong to me. Forgive me if I am mistaken. Shouldn't tristatelogic.com have it's own IP in hosts? Or at least be in the myname equivalent file? I'm not sure what OS you are using, so it may be different. I use OpenBSD and we do this: X.X.X.X tristatelogic.com tristatelogic (last is optional) FVWM is built into base OpenBSD and I am finally giving a real go at using it. I'm very confused so far but working on it. I am also going to try to get tmux working too, since that is built into base too. Anything I can learn is a plus to me! Chris Bennett
Re: FVWM: Strange problem with localhost
On Mon, Jun 17, 2019 at 4:09 PM Ronald F. Guilmette wrote: > > Sorry if this is off topic, but I'm having a very weird problem with > the name "localhost" and I wonder if perhaps any of you folks could > help me to sort it out. There's probably nothing wrong with localhost per se... > > Basically, once I start up X and fvwm, I see that all of my xterm > windows are automagically inheriting the following environment variable > and the value shown: How did you start up "X"? Which "X" are you running? What OS and are you using a login manager, display manager, etc? > > DISPLAY localhost:0.0 Xorg inherits the DISPLAY value from its environment which is generally set by your display manager (or xinit?) but I thought modern X servers didn't listen on TCP by default. AFAIK, having the host specified in your DISPLAY will make it use tcp for the connection even if the value is localhost and it sounds like maybe your system isn't listening on TCP, which is pretty normal these days. > > For reasons I'm none too clear on, this worked just fine for me earlier, > but I diddled a few things on this system since then and now I seem to > have broken it somehow. Now, when I try to start up *any* browser (and > probably also any X application) I get rather cryptic failure messages. > The one from teh Opera browser is clear enough. It says it cannot connect > to the X server on startup. Perhaps you inadvertently set the value of DISPLAY in one of your dot files and that's the actual problem? > > I futzed around trying to fix this problem for awhile and I managed to > discover that if I manually set DISPLAY instead to just :0.0 then suddenly > all my X applications start to work again. Right, because it stops trying to use the TCP transport and uses local instead. > > Here is the output from the command "getent hosts localhost" on the system > in question: > > ::1 localhost > 127.0.0.1 localhost localhost.tristatelogic.com > > > What am I doing wrong? Why doesn't the default value of localhost:0.0 > for DISPLAY work just as well as :0.0 ? In summary, localhost:0.0 says to use the TCP transport for the connection instead of local and your system is probably not listening on tcp. Not sure how you ended up there, though. I suggest a liberal use of "grep -r DISPLAY" in your home and maybe etc to try and locate the culprit.
Re: FVWM: Two small oddities
In message ,
Dan Espen wrote:
>"Ronald F. Guilmette" writes:
>> What about the second issue I mentioned? That one is far more serious.
>> Why doesn't chrome{ium} behave itself in a normal fashion, just like
>> everything else, and pop to the foreground when you click on some visible
>> part of it (e.g. along the very top edge on the window)?
>>...
>You might like:
>
>Style * MouseFocusClickRaises
Sorry that I didn't respond to this sooner.
All I want to say is "Thanks, that did indeed fix the problem."
Re: FVWM: One more question...
I had asked about how to get a digital xclock in the empty space just under the analog xclock and the xbiff thingy in the default theme for fvwm... In message , Jaimos Skriletz wrote: >Add this command to your StartFunction > >AddToFunc StartFunction I Test (Init) Exec exec xlock -digtal -strftime '%a %b >%d %T' > >The test is just to ensure it is only run during the init (first >start) And not after ever restart. OK, so I tried that, fixing the one small typo (digtal->digital), which was my fault, since it was present in my original question. The bad news is that just adding that one line top my ~/.fvwm2rc file -did- create an effect, but not at all what was intended. What happened was that the original analog xclock in the default theme got pushed out to a place on my destop that is sort-of near to the center top of my screen (and it was rendered MUCH bigger than before) and the digital xclock got kind-of stuffed into the little box where the analog xclock formerly was (in the default theme)... except of course that the text of my new digital xclose could not fix in that small space, so it just got cut off after the first few (leftmost) characters. So, bottom line, I'm still hoping that someone will tell me how to get a digital xclock into the empty space in the default theme that sits below the xbiff icon thingy and the analog xclock. I can't imagine that this should be too awfully difficult, but I quite certainly have no idea how to do it properly.
Re: FVWM: two questions about icons
Sorry. My bad, I forgot to attach the xprop output file to my prior
emssage. It is attached to this one.
GDK_TIMESTAMP_PROP(GDK_TIMESTAMP_PROP) = 0x61
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x40018a
_NET_FRAME_EXTENTS(CARDINAL) = 7, 7, 31, 7
_KDE_NET_WM_FRAME_STRUT(CARDINAL) = 7, 7, 31, 7
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CHANGE_DESKTOP,
_NET_WM_ACTION_CLOSE, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MAXIMIZE_HORZ,
_NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_MOVE,
_NET_WM_ACTION_RESIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_STICK
_NET_WM_DESKTOP(CARDINAL) = 0
_NET_WM_ICON_VISIBLE_NAME(UTF8_STRING) = "FreeBSD Handbook - Mozilla Firefox"
_NET_WM_VISIBLE_NAME(UTF8_STRING) = "FreeBSD Handbook - Mozilla Firefox"
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
bitmap id # to use for icon: 0x147
bitmap id # of mask for icon: 0x14e
window id # of group leader: 0x141
_GTK_THEME_VARIANT(UTF8_STRING) =
WM_WINDOW_ROLE(STRING) = "browser"
XdndAware(ATOM) = BITMAP
_NET_WM_ICON(CARDINAL) =Icon (64 x 64):
.^
_-
-;-:
`_";-`
_~"";-'
.~i/)1}})|?>~^_;""";-. .
` ^|xYYUJCCLLtffjz\_";-. '!
}>>xOOZXYUJCLLtffjzz<-"";-'<(`
>U? >LQ00OZXYJJCLLtffjzu_-~I|!
,CUv:nooQ0OOZYUJCCLttfjzz{_-";?/:
{UJJl !QaooQ0OZXfnvnLLtffjzz\_~"";!l.
'CUUJL:]hhaooQ0Xx[1){tLLtffjzx?_-i-
YUJCCLtfzxnucr]}{1[cr]}{)|/tLtffjjt>+++~;;;~-_
zYUJCCLtfzxnvcr[}{1[cr]}{)||LLttffjfx-~.
-ZYUJCLLtjzxnvcr[}{1{cr]}{)(tCLLttfffLu-~~---
[XYUJCLLtjzxuvcr[}{))cr][{cUJCCLLLttffLn_~~---__+
.JXYUJCLLtjzxuvcr[}{))[rrzOZYUJCCtttLji<<<+--_.
><_--__+;
+CXYUJCLLtjzxuvcr[}{))(X0OOZXYUUJJCCLLY1/+_+++<
;OZYUJCLLtjzxnvcr[}{1)(Y00OZZXYYUJJJLLUt/|i>>i+__+>,
IOZYUJCCLtfzxnvcuxnun})0Q00OOZXYYUUCCCJZI)|<<<>I
1OZYUJCCLtfzxnntLfjQkhJaQQ00OOZZXYYUUUJO}l)/iii!<<>/
nOZYUJCCLtfjxxLLtjfbhaaaoQQ00OOZZXX0x_|(I<<<>>i/
LOZXUJJCLLfjzfCtfjfbhhaaooQQ000OOZZZXXX0L_I\\l!!li!?
z0ZXYUJCLLfjzLLfjznakhhaaooQQOOOZZZQY_>/\?>>ii!I
)0ZXYUJCLLtjzLtfzxuxhkhhaaoooQQoY_+?//IllI!iiiI!
<0OXYUJCCLtfjtfjxnucvakhhaaaooQQQ00aJ++!!!?i
`QOZYUJCCLtfffjzxuvr}}YkhhhQCnrvL00kj++I???III?!!lI+
.ZOZXYJJCLLfjfjznucr}{1]xx]\//?II|YQQQok}<>??//^
v0OZYUJCCLtfjjxnvcr]}{1))(|\\/??IIfaaaooobC>>>?///?I?I
\QOZXUUJCLLtjjxnnvcr]}{1)((|\\|xULoahd|iii/??<
"Q0ZXYUJCCLtfjzuvc][}{1))fbdbbhhbj!!!l///\/\\\///^
.L0OZYUJJCLLtjzxnuvztzxnvcutkpbkkhkb0Ill!?/\l
)Q0ZXYUJCCLtfjzxuvvaqbahpwqdbbkkkba\IIll/\\||\\"
^00OXYUJJCLLtfzxnuvvopdbd0|?III?\|?
.cQOZXYUJCCLtfjzxnuvcYdpf//(||_
;00OXYUJJCLLtfjzxnuvcnXbppddkC1\\\||]-
.rQOZXYUJCCLLtfzxnuuvrr]nLYZZYtc((|||||{u:
:O0OZYUJJCCLtfjzxnuvvcr][}{{11))(((((()))1t1
.\Q0ZXYUJJCLLtfjzxnuvvcr][[}{111)))(()))1z{?
'x0OZXYUJCCLLtfjzxnuuvcr]][}}{{11)))111r{{'
^Y0OZYUUJCCLLtfjzxnnuvcrr][[}}{{1)1{{{}}_
-O0ZXYUJJCCLLtfjzxxnuvvcrr][[}}{{}}}[[!
.>OOZXYUJJCCLLtfjzzxnuuvccrr]][[}{{}[[[]]i
.>OOZXYUJJCCLLtfjjzxxnuuvccrrr]][[]rrr]-
.-YOZXYUJJCCLLttfjzzxnnuuvvcc]]]|'
:tOZXYUJJCCLLLtfjjzzxnnuuuvvvvvvr".
')OZXYUJJCCCLLttfjjzzxxnnvuuuj?.
.-CZXYUUJJCCLLLtffjjzzxxxnnnxjYX|
'\UXYUUJJCCCLLLttffjjzzztJXJj|
.`/LYYUJJJCCttfffjjjzzv;
.'-[CYUJJtttfz{;.
Re: FVWM: two questions about icons
In message firefox.xprop wrote: >This is probably because my memory is failing me (I wasn't able to >double check what resource/class firefox uses these days). > >Use FvwmIdent or xprop and figure out the correct resource/class of >firefox on your system and use that instead of 'firefox' in the Style >line. Please see attached fle which is the output from xprop. I seriously have no idead= what I am looking for in this file, but I do see several places where the name "Firefox" (capitalized) appears. My assumption was that perhaps this is the magic string I needed to be using, so I substituted that in, in place of "firefox" in the Style lines within both ~/.fvwm2rc and also ~/.fvwm/config and then I again exited X and restarted it, and I'm still getting the BIG icons. Maybe you can look at this xprop output and intuit what name, precisely, I should be using in the Style line, but I'm totally ignorant of all of this stuff so it's a complete enigma to me. >One really needs to read the docs and understand what commands are >doing in fvwm to make the most out of it. For a Style you need to >ensure you match the name/class/resource of the window. OK, two things... First, at this point my goals are -very- modest. I don't really need to "make the most" out of fvwm. I'm mostly happy with the default fuctionality -and- with the default theme. Second, to be frank, I've already been throughly intimidated by the gigantic size of the fvwm man page. I mean seriously... holy moses! It's wonderful that fvwm provides such massive flexibility and such massive configurability, but unless and until I need to write a Master's thesis on this one tool, I don't believe that I'll have time to delve seriously into even the first couple of layers of the complexity here. Don't get me wrong. I admire this tool and also every person who has worked to create it. But my needs are simple and my time, limited. If I can just get these three simple things fixed then I'll be a happy camper: (1) proper (48x48) icon size for Firefox, (2) a proper sort of an icon being used for minimized xterm windows and (3) a nice digital xclock displaying in the space below where the default theme is putting the xbiff thingy and analog xclock. I've already received a suggestion on how to do that last one... which I have yet to try, but which I am hoping will work... so now I just need some simple fixes for the other two. As I say, I greatly admire fvwm and all of this ornate configurability. It apparently gives the user that ability to configure just about everything. That's wonderful, of course. I just wish that it had an option also to select a preferred icon size. That would have simplified everything a lot, I think. Regards, rfg P.S. Many UNIX programs/utilities that support their own config files document the format of allowable entries in those files in a separate man page from the one that documents the program itself (e.g. ntp.conf and many others). This makes it a bit easier to find what one is looking for, either by looking at the man page for the program or at the man page for the configuration file. I only mention this because it seems to me that the man page for fvwm might benefit from such a separation of concerns (into two separate man pages). Just a thought. Probably worth what you paid for it. :-)
Re: FVWM: two questions about icons
On Fri, May 31, 2019 at 4:01 PM Ronald F. Guilmette wrote: > > > In message > > Jaimos Skriletz wrote: > > >If you don't like the icon provided by the application you can > >configure fvwm to use custom icons via the Icon Style (or > >WindowStyle). For example if you find a firefox icon and put it in > >your ImagePath, you can tell fvwm to use it for firefox as follows: > > > >Style firefox Icon firefox.png > > > >(you could also just use a full path for your icon specification). > This is probably because my memory is failing me (I wasn't able to double check what resource/class firefox uses these days). Use FvwmIdent or xprop and figure out the correct resource/class of firefox on your system and use that instead of 'firefox' in the Style line. https://fvwmforums.org/wiki/Config/Style/ One really needs to read the docs and understand what commands are doing in fvwm to make the most out of it. For a Style you need to ensure you match the name/class/resource of the window. jaimos
Re: FVWM: two questions about icons
In message Jaimos Skriletz wrote: >If you don't like the icon provided by the application you can >configure fvwm to use custom icons via the Icon Style (or >WindowStyle). For example if you find a firefox icon and put it in >your ImagePath, you can tell fvwm to use it for firefox as follows: > >Style firefox Icon firefox.png > >(you could also just use a full path for your icon specification). I've now tried to do this in multiple different ways and it just ain't working for me. I was able to find and download an appropriate 48x48 firefiox .png icon file and I've now tried to get fvwm to make us eof that in mutiple different ways and so far it is just refusing. So if some kind soul can tell me what I'm doing wrong, I'd appreciate it. I started out by just putting the .png file into my own home directory (permissions 0644) and then I added the following single line at some random point in the ~/.fvwm2rc file which I had copied from the systemwide default file /usr/local/rfg/system.fvwm2rc Style firefox Icon /home/rfg/.Firefox-icon-48x48.png And yes, I double-checked that the file really did exist at that exact path. After doing this, I shutdown X and restarted it. No change. Firefox still minimized to an oversized icon. I wasn't sure whether or not the use of full pathnames was supported, so I copied the .png file into a directory, /usr/local/rfg/icons/ (removing the leading period in the filename as I did so) and then changed the above to the following and tried again: ImagePath /usr/local/rfg/icons Style firefox Icon Firefox-icon-48x48.png Still no joy. I noted that someone here had saidf that the cannonical location of the per-user fvwm config file is now ~/.fvwm/config so I copied my tailored config file to that location and again exited X and restarted, and still the Firefox icons are the big fat ones. I guess I'm doing something wrong, but it isn't obvious what that might be. Does fvwm create a detailed log file anywhere that I should be studying for hints about what files it is reading and what went wrong?
Re: FVWM: One more question...
On Thu, 30 May 2019, Ronald F. Guilmette wrote: On the new system I'm configuring, I'm running without any .fvwmrc file in the home directory of the account that I start X from. So I guess this means that Fvwm is picking up some default .fvwmrc file from someplace. I just discovered that fvwm-config -S will tell you where system.fvwm2rc is (on my machine it looks to be in /etc/X11/fvwm2. just below those things there is an empty space. I would very much like to place another xclock in that empty space as follows: Copy the system.fvwm2rc in ~/.fvwm/.fvwm2rc and edit it freely (some examples of mine are in the link in signature) -- Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) http://sax.iasf-milano.inaf.it/~lucio/WWW/Opinions/window.html
Re: FVWM: two questions about icons
On Fri, May 31, 2019 at 12:12 AM elliot s wrote: > > fvwm should be able to resize icons so theyre of iconable size. > Presently, either you get supersized icons in menus or a fragment of > an icon in the "taskbar". I'm presently manually scaling icons and > writing out resized ones. > It depends on the icon type. Fvwm only supports .xpm, .png, and .svg images. Both .xpm and .png images cannot be resized by fvwm (since the libraries fvwm uses don't support this). If you want to resize either of these icon types you have to use some third party tool. Imagemagick is one such tool that you can use to automate resizing if you want to write custom functions. If you use .svg, these can be scaled by the library and fvwm supports setting the size of these icons (check the man page for details). So if you want to have fvwm resize icons for you, use .svg icons. jaimos
Re: FVWM: two questions about icons
fvwm should be able to resize icons so theyre of iconable size. Presently, either you get supersized icons in menus or a fragment of an icon in the "taskbar". I'm presently manually scaling icons and writing out resized ones.
Re: FVWM: two questions about icons
In message <20190531001538.084a9320...@apps1.cs.toronto.edu>,
Chris Siebenmann wrote:
> The bad news is that modern EWMH X programs generally don't supply
>their icons as files in the filesystem; instead, they provide multiple
>sizes of icons as X properties, which you can usually see by using
>'xprop' on a suitable window (it's all of the _NET_WM_ICON stuff, and
>I think the WM_HINTS stuff, although I don't know how the bitmap ids
>are used).
Thanks much. I really -am- just to dumb end-luser, and thus didn't even
know about xprop until just now.
But I ran it on (non-minimized) Firefox and Opera browser windows on my
system of interest and it appears that Opera only offers up a single 48x48
icon, whereas Firefox now offers all of: 16x16, 32x32, 48x48, 64x64, and
128x128 versions.
Strangely, the output of xprop executed on a Chrome{ium} browser window
-seems- to say to me that Chrom{ium} is only offering up a 128x128 icon
for itself, but when minimized, the icon displayed in actually way smaller
than that... somwhere between the 48x48 icon size used by Opera and what
I am just guessing is probably the somewhat larger 64x64 size used , at
present, for Firefox.
I just mention this because it appears to me that in that (Chrom{ium}) case,
someboyd may be doing some sort of scaling or something.
So, anyuway, what I want is for Fvwm to be using the 48x48 icon for its
representation of a minimized Firefox window.
Surely there -must- be -some- way to force that, no?
>If you want to see what size of icon fvwm is using for some
>window, you can use 'xwininfo' on the icon; this will tell you the
>icon's Width and Height.
Thanks. Yet another thing I learned today.
>The actual source PNGs for these Firefox icons are present in the
>source code but are magically bundled into the compiled and installed
>Firefox.
I guess that me offering this observation is rather pointless, but I'll
offer it anyway: This choice, to embed the icons into the compailed
binaries, is, in my humble opinion, of debatable merit.
I know. I know. If I want to grouse about -that- questionable design
decision, then I'm in the entirely Wrong Place for doing so. (If I get
motivated, I'll register my opinion on this topic elsewhere.)
>Never the less you can simply pull the PNGs out of the source
>code, once you know the magical location. Probably the simplest way is
>through the Github Firefox mirror, where I believe you can find all of
>the sizes in the default*.pngs here:
>
>https://github.com/mozilla/gecko-dev/tree/master/browser/branding/official
OK, I -think- I understand what you are suggesting. I'd basically be
telling/forcing Fvwm to override the icon size choice it is currently
making in the case of Firefox. And I'd be doing it by forcing Fvwm to
use a .png of my choosing... which is exactly the kind of localized hack
that I myself had suggested earlier. But please answer me this: Why
should I even have to go through all this if the Firefox binary that
I'm using already has an built-in/compiled-in 48x48 icon? Why can't
I just tell Fvwm that my first preference for icon sizes in 48x48 in
all cases?
>So, basically, you probably want to use xwininfo on an Opera icon to
>find out how big it is, then download the appropriate sized defaultNN.png
>file and set it as Firefox's icon. This will override anything Firefox
>is hinting to fvwm and fvwm is picking up on.
See above. I'm still perplexed as to why I even need to resort to such a
hack.
And BTW, who or what is doing the apparent scaling on the Chromium icon?
Maybe I just need to get that thing working on my side, eh?
Re: FVWM: One more question...
On Thu, May 30, 2019 at 5:22 PM Ronald F. Guilmette wrote: > > > Other than the questions I've alreasdy posted, I just have one > more and then I think I'm done. If i can find a solution for > this and the others I've posted, then I think I'll be a happy > camper. > > On the new system I'm configuring, I'm running without any > .fvwmrc file in the home directory of the account that I start > X from. So I guess this means that Fvwm is picking up some > default .fvwmrc file from someplace. That's fine, and > whereever it is, and whatever it contains, it seems to -mostly- > fit my needs rather well, so I don't really need to diddle it... > much. I've got a nice traditional clock face, and a nice xbiff > thingy to tell me know when I have new mail. Perfect. But > just below those things there is an empty space. I would very > much like to place another xclock in that empty space as follows: > The new location for the fvwm config file is $HOME/.fvwm/config If you are using a new version of fvwm it comes with a default theme, this is located in $PREFIX/share/fvwm/default-config (where $PREFIX is often /usr or /usr/local) If using the default-config, there is a script in the menu to copy the default config to $HOME/.fvwm/config and then you can just edit away. >xclock -digtal -strftime '%a %b %d %T' > > Can someone tell me how to do that? > Add this command to your StartFunction AddToFunc StartFunction I Test (Init) Exec exec xlock -digtal -strftime '%a %b %d %T' The test is just to ensure it is only run during the init (first start) And not after ever restart. You may find the wiki useful if looking up configs and tips https://fvwmforums.org/wiki/ jaimos
Re: FVWM: two questions about icons
On Thu, May 30, 2019 at 5:14 PM Ronald F. Guilmette wrote: > > > In message <20190530185519.b4840320...@apps1.cs.toronto.edu>, > Chris Siebenmann wrote: > > This seems like such a simple thing. I just want the Firefox icon smaller. > given all fo teh obvciously massive configurability of Fvwm, I have to > believe that there -must- be a simple solution to this fairly trivial > little problem. And I'm holding out hope that somebody will just tell > me what it is. > I gave you a simple solution. Go find a firefox icon you like (google firefox icon and you'll have plenty of choice) and if it is a .png resize it to the size you want. If it is an .svg you can just tell fvwm what size to make it then use the Icon style. In general that is the best way in my experience is just tell fvwm what icon you want to use. Not try to extract this icon from the EWMH spec. jaimos
Re: FVWM: two questions about icons
> >On Wed, May 29, 2019 at 9:43 PM Ronald F. Guilmette > > wrote: [...] > >> So, is there an alternative minimized icon available for Firefox? > > > >Fvwm doesn't come with a set of icons. Fvwm will honor the apps icon > >that it provides via EWMH standards. This is also the case for xterm > >or any other program. > > > >If you don't like the icon provided by the application you can > >configure fvwm to use custom icons via the Icon Style (or > >WindowStyle). For example if you find a firefox icon and put it in > >your ImagePath, you can tell fvwm to use it for firefox as follows: [...] > Thanks for all this info. I'm going to try to fish the old Firefox > icon out of my old FreeBSD system. If I can find it, then I'll try > to see if I can get fvwm to use it as you've instructed. > > If all else fails, I suppose that I can always RTFM, although I didn't > (and don't) really know anything at all about this EWMH you mentioned. > (But Google is my friend.) > > Hummm... did a find on my old system's /usr directory, searching for > .png files, and I found several candidates that may be what I'm looking > for, but I don't know which one is the Right One. The bad news is that modern EWMH X programs generally don't supply their icons as files in the filesystem; instead, they provide multiple sizes of icons as X properties, which you can usually see by using 'xprop' on a suitable window (it's all of the _NET_WM_ICON stuff, and I think the WM_HINTS stuff, although I don't know how the bitmap ids are used). If you want to see what size of icon fvwm is using for some window, you can use 'xwininfo' on the icon; this will tell you the icon's Width and Height. The actual source PNGs for these Firefox icons are present in the source code but are magically bundled into the compiled and installed Firefox. Never the less you can simply pull the PNGs out of the source code, once you know the magical location. Probably the simplest way is through the Github Firefox mirror, where I believe you can find all of the sizes in the default*.pngs here: https://github.com/mozilla/gecko-dev/tree/master/browser/branding/official So, basically, you probably want to use xwininfo on an Opera icon to find out how big it is, then download the appropriate sized defaultNN.png file and set it as Firefox's icon. This will override anything Firefox is hinting to fvwm and fvwm is picking up on. - cks
Re: FVWM: two questions about icons
In message <20190530185519.b4840320...@apps1.cs.toronto.edu>, Chris Siebenmann wrote: >> Fvwm doesn't come with a set of icons. Fvwm will honor the apps icon >> that it provides via EWMH standards. This is also the case for xterm >> or any other program. > > There is a tricky qualification on this, which is that applications >can supply a range of sizes for their icons and Fvwm has a hard-coded >default and maximum size it will use. I'm not sure if this default size >has changed over time, but if it has, this is one of the potential causes. >It's also possible that Firefox is now offering bigger icons and fvwm is >picking them now that they're available. > >(I ran into this when I switched to a HiDPI display and started looking >at why fvwm was now only using tiny icons even when various programs had >larger ones available.) > > Interested parties can look at the various #define's related to >icon size in fvwm/ewmh_icons.c in the source code. Unfortunately I >don't think there's a way to set these in your fvwmrc, although >maybe I overlooked some icon size settings in the manual page. Thanks for all of this additional info. As I said earlier, this is all more than a little bit bewidering to me. I'm just an (exceptionally ignorant) fvwm end-luser, and I had hoped not to have to go groveling around in the source code -or- that I might have to diddle something and then rebuild the thing from the FreeBSD ports tree. This seems like such a simple thing. I just want the Firefox icon smaller. given all fo teh obvciously massive configurability of Fvwm, I have to believe that there -must- be a simple solution to this fairly trivial little problem. And I'm holding out hope that somebody will just tell me what it is. Just one more thing: It may perhaps -seem- as if I'm fretting about something that's really inconsequential, but for me, it actually isn't, and none of you have ever seen my destop. I routinely have dozens and dozens of Firefox windows active, but minimized, and even with the small sized icons, they often line up along the botom edge of my screen, from left to right, often until some of them end up partially obscured by the block of Fvwm stuff that, but default, apparently, appears in the lower right hand corner of my primary (upper left) desktop. (And that's something else I wish I could find a solution for. It's too bad that whatever logic is responsible for placing those icons in a neat row along the bottom edge of my screen doesn't seem to realize that if enough of them get all lined up there, some of them will be obscured by the Fvwm-generated box in he lower right hand corner.)
Re: FVWM: two questions about icons
In message , you wrote: >On Wed, May 29, 2019 at 9:43 PM Ronald F. Guilmette > wrote: >> >> >> >> Greetings, >> >> First, the icon used to repreesent minimuzed Firefox windows is >> substantially larger than t was for the prior version(s) of fvwm >> that I had been accustomed to using. Since I tend to have a LOT >> of different brwosers windoes open and minimized on my screen, >> this is likely to cause me some consternation, over the long run. >> >> So, is there an alternative minimized icon available for Firefox? >> > >Fvwm doesn't come with a set of icons. Fvwm will honor the apps icon >that it provides via EWMH standards. This is also the case for xterm >or any other program. > >If you don't like the icon provided by the application you can >configure fvwm to use custom icons via the Icon Style (or >WindowStyle). For example if you find a firefox icon and put it in >your ImagePath, you can tell fvwm to use it for firefox as follows: > >Style firefox Icon firefox.png > >(you could also just use a full path for your icon specification). > >If you like the minimized window look, there are some custom functions >that do this using imagemagick to create an icon image and use it. > >https://fvwmforums.org/wiki/Tips/ThumbnailsAsIcons/ Thanks for all this info. I'm going to try to fish the old Firefox icon out of my old FreeBSD system. If I can find it, then I'll try to see if I can get fvwm to use it as you've instructed. If all else fails, I suppose that I can always RTFM, although I didn't (and don't) really know anything at all about this EWMH you mentioned. (But Google is my friend.) Hummm... did a find on my old system's /usr directory, searching for .png files, and I found several candidates that may be what I'm looking for, but I don't know which one is the Right One. I guess that it might help if I knew the size of the icon that fvwm on the new system was using to represent Opera. That's the size I want. So, how can I figure out the location, in the file system, of the icon that fvwm is using (on the new system I am configuring) for the Opera browser? I looked at a couple of man pages and didn't files any FILES sections at the end. :-( Regards, rfg P.S. I've just -quickly- glanced at the man page for fvwm. I think that it is marvelous that someone went to all of the trouble to well and properly document this tool. However, that having been said, please forgive me for just noting that in all of my multiple decades of using UNIX systems, this has got to be, by far, the single biggest/longest man page that I personally have ever seen. That's -not- a bad thing. More documentation is almost always better documentation. It's just a bit bewildering for a casual user, such as myself, who doesn't really have a year or two to become familiar with all of this stuff. But I guess that's why this mailing list exists, eh?
Re: FVWM: two questions about icons
> On Wed, May 29, 2019 at 9:43 PM Ronald F. Guilmette > wrote: > > > Greetings, > > > > First, the icon used to repreesent minimuzed Firefox windows is > > substantially larger than t was for the prior version(s) of fvwm > > that I had been accustomed to using. Since I tend to have a LOT > > of different brwosers windoes open and minimized on my screen, > > this is likely to cause me some consternation, over the long run. > > > > So, is there an alternative minimized icon available for Firefox? > > > > Fvwm doesn't come with a set of icons. Fvwm will honor the apps icon > that it provides via EWMH standards. This is also the case for xterm > or any other program. There is a tricky qualification on this, which is that applications can supply a range of sizes for their icons and Fvwm has a hard-coded default and maximum size it will use. I'm not sure if this default size has changed over time, but if it has, this is one of the potential causes. It's also possible that Firefox is now offering bigger icons and fvwm is picking them now that they're available. (I ran into this when I switched to a HiDPI display and started looking at why fvwm was now only using tiny icons even when various programs had larger ones available.) Interested parties can look at the various #define's related to icon size in fvwm/ewmh_icons.c in the source code. Unfortunately I don't think there's a way to set these in your fvwmrc, although maybe I overlooked some icon size settings in the manual page. - cks
Re: FVWM: two questions about icons
On Wed, May 29, 2019 at 9:43 PM Ronald F. Guilmette wrote: > > > > Greetings, > > First, the icon used to repreesent minimuzed Firefox windows is > substantially larger than t was for the prior version(s) of fvwm > that I had been accustomed to using. Since I tend to have a LOT > of different brwosers windoes open and minimized on my screen, > this is likely to cause me some consternation, over the long run. > > So, is there an alternative minimized icon available for Firefox? > Fvwm doesn't come with a set of icons. Fvwm will honor the apps icon that it provides via EWMH standards. This is also the case for xterm or any other program. If you don't like the icon provided by the application you can configure fvwm to use custom icons via the Icon Style (or WindowStyle). For example if you find a firefox icon and put it in your ImagePath, you can tell fvwm to use it for firefox as follows: Style firefox Icon firefox.png (you could also just use a full path for your icon specification). If you like the minimized window look, there are some custom functions that do this using imagemagick to create an icon image and use it. https://fvwmforums.org/wiki/Tips/ThumbnailsAsIcons/ jaimos
Re: FVWM: how to escape F1?
Hi Thomas, On 3/8/19 9:53 AM, Thomas Adam wrote: Hi, Key F1 A A -- Apparently thats a misunderstanding. Sorry for my bad English. I would like fvwm to *ignore all key bindings for one keypress* to forward it directly to the app with input focus. Some kind of "escape" key entered before the actual key. For example, I have Key F1 A N Switch-Iconic Key F2 ... : in my .fvwmrc. Assuming the window "xyz" has input focus: If I press and release some [magic_escape_key], followed by [F1], then "xyz" should *not* be changed to an icon, but [F1] should be sent to "xyz" instead. Do you think this could be possible? Regards Harri
Re: FVWM:
2019-01-05 1:33 GMT+01:00, Thomas Adam : > On Sat, Jan 05, 2019 at 01:27:38AM +0100, Peter Holm wrote: >> Best would be if I could get the buttons to show up in the same order >> as the windows is layered. > > Sounds as though you want to use FvwmIconMan then. > > -- Thomas Adam > Then it seems that I am, at least partially - on the right track. But I don't success with the DontShow options for numerical states or WindowId Can I do something like *FvwmIconMan: DontShow WindowId=0x1c7 *FvwmIconMan: DontShow State=7 Or should I use something else instead.? /Peter Holm
Re: FVWM: Escaping calls to State and Infosostore in piperead
So I guess for the moment I have to use SetEnv transi 31 I have a number of state "constants" planned to use in short future to define groups of windows, groups of behaviors and eh, groups of groups. 2018-12-26 17:52 GMT+01:00, Thomas Adam : > Well, that likely requires a code change. I'll do that later on. > > Kindly, > Thomas > > On Wed, 26 Dec 2018, 16:35 Peter Holm >> This is more or less a follow up from my earlier question. >> I have this >> --- >> Key Space A M State >> $[infostore.transi] True >> Key Space A C State >> $[infostore.transi] False >> >> .. >> AddToFunc StartFunction >> + I InfostoreAdd transi 31 >> >> >> >> Then when I switch desk/workspace I let the window(s) follow me >> .. >> DestroyFunc GoLeft >> AddToFunc GoLeft >> ... >> + I PipeRead "\ >> if [ $[page.nx] -gt 0 ]; then\ >> echo All '(State 31)' MovetoPage -1p 0p;\ >> echo GotoPage -1p 0p;\ >> elif [ $[desk.n] -eq 0 ]; then\ >> ... >> I would like to replace >> All '(State 31)' >> with >> All '(State $[infostore.transi] )' >> but it makes the GoLeft function not work >> >> >> Any suggestions.? >> >> And why I don't use transient windows instead, well I have further >> plans to use the state call - which I described shortly in my previous >> post. >> >> > -- Med vänlig hälsning / With kind regards ⼃Pᵉᵗᵉʳ Hᵒˡᵐ
