Re: FVWM: Perform action, one in a time - at every open window at all desks and workspaces.
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.? If No - then, Simple solution, I have to loop thrpugh all desks and pages, and for every page perform thumbnail_minicons. If there are no active window - the action will fail. That means - I have to perform GotoDeskAndPage for every Desk and Page that is on my system. (9 desks * 9 pages = 81 pages) eitherway I would really like to find a more generic solution. /Peter 2020-02-07 11:56 GMT+01:00, Peter Holm : > No go with > AddtoFunc StartFunction > + I All Thumbnail_MiniIcons > -- 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.
No go with AddtoFunc StartFunction + I All Thumbnail_MiniIcons
Re: FVWM: Document mime type compliance?
I will try it out. Thank you. /Peter Holm 2020-01-06 14:18 GMT+01:00, Stefan Blachmann : > On 1/6/20, Mark Nejedlo wrote: >> If you want different actions based on the >> extension, you'll need to write a more sophisticated script that is >> extension aware to use in the place of fvwm_make_directory_menu.sh. > > This might be what you want: https://github.com/kernschmelze/meowpurr > > It is a full-blown freedesktop standards supporting application and > file browser for FVWM using MissingMenuFunction. > > It of course supports file extensions according to freedesktop > specifications and the like, with very comfortable OpenWith menus etc > etc. It memorizes the applications you prefer for particular file > types, too, etc etc. > > It is still WIP - the freedesktop specification for recent opened > files thing is still not finished (when it works, it gives a complete > "Recent" menu not only for apps, but for files not opened by the > file/app browser, but inside other applications, too. There are also > still a few minor bugs. > > Right now, I have no time to work on that, as it works fine for what I > need. > If others are interested in that stuff, it would motivate me to finish > the uncompleted parts. > > So I'd suggest to play around with it... if you have any questions, just > ask. > > Have fun, > Stefan > > -- Med vänlig hälsning / With kind regards /Peter Holm
FVWM:
Is it possible to add an already started application (for example xterm) to fvwmbuttons.? Or is it better to use FvwmIconMan .? I don't get how to get FvwmIconMan to use numbered states. Reason to ask - I have managed to make some grouped windows which I want to add a buttonbar to, or on the fly or add and remove the windows into FvwmButtons, and ther have a Button.Panel for the windows. Best would be if I could get the buttons to show up in the same order as the windows is layered. Here is the main part of the config for my grouped windows. - AddToFunc StartFunction + I InfostoreAdd tabbs 29 ... Key T A SM ToggleWindow ThisWindow DetachWindow ThisWindow AttachWindow # ToggleWindow is planned to be used for much else, for example -right now with correct # parameters It is used to stick and unstick single or grouped windows. # I guess I will rewrite this function a few times DestroyFunc ToggleWindow AddToFunc ToggleWindow + I ThisWindow (CurrentPage, State $[infostore.tabbs]) + I TestRc (Match) KeepRc $[0] $[1] + I TestRc (NoMatch) $[2] $[3] # + I TestRc (Error) DestroyFunc AttachWindow AddToFunc AttachWindow + I None (State $[infostore.tabbs]) + I TestRc (Match) SetMainWindowSpecs + I ThisWindow State $[infostore.tabbs] True + I ThisWindow (State $[infostore.tabbs]) ResizeMoveMaximize $[infostore.TabWindow_Width]p DestroyFunc SetMainWindowSpecs AddToFunc SetMainWindowSpecs + I InfoStoreAdd TabWindow_Width $[w.width] + I InfoStoreAdd TabWindow_Heigth $[w.height] + I InfoStoreAdd TabWindow_X $[w.x] + I InfoStoreAdd TabWindow_Y $[w.y] DestroyFunc CycleWindows AddToFunc CycleWindows + I Next (CurrentPage, State $[infostore.tabbs]) Raise ... #Also some functions for manage the position of grouped or not grouped windows. ... Key 1 A SM ToggleWindow "All (CurrentPage, State $[infostore.tabbs])" LeftUpper\ ThisWindow LeftUpper Aside from my question, any comments or suggestions regarding this config are highly welcomed. -- Med vänlig hälsning / With kind regards /Peter Holm
Re: FVWM: Escaping calls to State and Infosostore in piperead
> Aside from avoiding asking the more obvious question of why you want to do it > this way, .. I just remember why I didn't like to use sticky windows for that. I just don't want to accidentally unstick any of those windows I randomly use to have floating around. Earlier I switched to use BOOKMARKED_WINDOW, but since I like to mark multiple windows in cthe same way one can do with toogle the sticky-ness, I asked in an earlier post how to do that. Jaimos Skriletz pointed me to use states - so now I hope to go that way full out. > ...there's.no code change required. The above is wrong -- don't > quote > '(State 31)' as this will throw the parser out. Try: > > All (State $[infostore.transi]) MoveToPage -1p -0p > > -- Thomas Adam > I can't get it to work that way. But as I now got infostore to work in the piperead, I feel I can live with that I need to use quotes until I find out why it not work as you described. -- /Peter Holm
Re: FVWM: Escaping calls to State and Infosostore in piperead
I Wrote earlier "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." I used the wrong term here. I meant sticky, not transient. And also - a few years ago I used sticky windows for that, but it was something with the behavior of sticky windows that didn't fill my needs - I don't remember what it was. But I decided to switch to bookmarked_window. And now I make the switch to states. which will take my config way further from what it is today because I can have multiple states to one window. It's more about to explore and learn the advantages of whats possible than find the simplest solution. 2018-12-26 19:26 GMT+01:00, Jaimos Skriletz : > On Wed, Dec 26, 2018 at 9:35 AM Peter Holm wrote: >> >> 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 > > Why not just use Sticky for this. No need to define a custom state to > make it so windows move to a new workspace (pages/desktops) when you > do. > > (sorry for the duplicate reply, forgot to CC the list) > > jaimos > -- Med vänlig hälsning / With kind regards ⼃Pᵉᵗᵉʳ Hᵒˡᵐ
FVWM: Escaping calls to State and Infosostore in piperead
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.
FVWM: bookmark/unbookmark multiple windows
To select a window for moving there is afaik two methods. Either you make the window sticky, and then unstick it - or you bookmark the window. I would like to do this : -- 1), Select a windoiw 2), Add the window to a list, lets call it LIST_OF_BOOKMARKED_WINMDOWS 3), Add a new window to the list. 4), Search the list for select window - if window is found then do something with the windows. 5), remoive the window from the list. --- Further goal . - Ideally I would like to have multiple lists and swithch between them Any ideas.? /Peter Holm
