Re: FVWM: two questions about icons

2019-06-05 Thread elliot s
fvwm is a more of a window manager toolkit. You use it to build your own window manager. That used to be more obvious when the default config was really uselessly minimal.

Fwd: FVWM: two questions about icons

2019-06-05 Thread Jaimos Skriletz
(forgot to cc the mailing list) On Wed, Jun 5, 2019 at 4:30 PM Ronald F. Guilmette wrote: > > > In message <20190605213540.hmud7pziqi64a6i5@laptop.local>, > Thomas Adam wrote: > > >> For me, 3c was in fact just a blank space. I just now figured out why. On > >> FreeBSD, the xload command is

Re: FVWM: two questions about icons

2019-06-05 Thread Ronald F. Guilmette
In message <20190605213540.hmud7pziqi64a6i5@laptop.local>, Thomas Adam wrote: >> For me, 3c was in fact just a blank space. I just now figured out why. On >> FreeBSD, the xload command is in a separate package, all on its own, and that >> package is *not* currently listed as dependency of

Re: FVWM: two questions about icons

2019-06-05 Thread Thomas Adam
On Wed, Jun 05, 2019 at 02:12:07PM -0700, Ronald F. Guilmette wrote: > The default theme for fvwm includes a big box that appears in the lower > right hand corner of the screen. Is there a name for that whole thing? > If so, and if someone would be kind enough to tell me what it is, then > I'll

Re: FVWM: _NET_WM_NAME

2019-06-05 Thread Klaus Ethgen
Am Mi den 5. Jun 2019 um 16:52 schrieb Thomas Adam: > On Wed, Jun 05, 2019 at 04:30:07PM +0100, Klaus Ethgen wrote: > > Here the relevant props: > >WM_NAME(STRING) = "GNU Image Manipulation Program" > >_NET_WM_NAME(UTF8_STRING) = "[Verdon] (importiert)-1.0 (RGB-Farben > >

Re: FVWM: two questions about icons

2019-06-05 Thread Ronald F. Guilmette
In message , Lucio Chiappetti wrote: >On Tue, 4 Jun 2019, Ronald F. Guilmette wrote: > >> Grrr. I can't imagine why this would be so hard. I didn't think >> what I wanted to do would be so complex. Again, I just want a >> digital xclock to appear in the blank space below the xbiff thingy

Re: FVWM: FvwmForums: Change of engine and help with theming

2019-06-05 Thread Thomas Adam
On Wed, Jun 05, 2019 at 07:32:42AM -0600, Glenn Golden wrote: > +1 for plain old nntp, with a digest option added too, as Lucio suggested. The point of this email thread wasn't to ask the question: "how can we appease ourselves for those who want to use forums". The point was to ask to see if

Re: FVWM: _NET_WM_NAME

2019-06-05 Thread Thomas Adam
On Wed, Jun 05, 2019 at 04:30:07PM +0100, Klaus Ethgen wrote: > Here the relevant props: >WM_NAME(STRING) = "GNU Image Manipulation Program" >_NET_WM_NAME(UTF8_STRING) = "[Verdon] (importiert)-1.0 (RGB-Farben > 8-Bit-Gamma-Ganzzahl, GIMP built-in sRGB, 1 Ebene) 1024x683 \342\200\223 GIMP"

Re: FVWM: _NET_WM_NAME

2019-06-05 Thread Klaus Ethgen
Hi, Am Mi den 5. Jun 2019 um 15:42 schrieb Thomas Adam: > On Wed, Jun 05, 2019 at 03:46:49PM +0100, Klaus Ethgen wrote: > > However, the freedesktop guys are known to add often incompatible stuff > > that is not supported by other desktops than their own. And they are > > resistant to learn that

Re: FVWM: _NET_WM_NAME

2019-06-05 Thread Thomas Adam
On Wed, Jun 05, 2019 at 03:46:49PM +0100, Klaus Ethgen wrote: > However, the freedesktop guys are known to add often incompatible stuff > that is not supported by other desktops than their own. And they are > resistant to learn that what they do is stupid. So is there a way to get > that property

FVWM: _NET_WM_NAME

2019-06-05 Thread Klaus Ethgen
Hi Folks, I fond recently a problem with gimp only setting the _NET_WM_NAME property instead WM_NAME. There is a specification for _NET_WM_NAME[0] but it sounds stupid for me. The original WM_NAME is already UTF-8 so there is no need for a incompatible new property. However, the freedesktop

Re: FVWM: two questions about icons

2019-06-05 Thread Jaimos Skriletz
On Wed, Jun 5, 2019 at 3:41 AM Lucio Chiappetti wrote: > > On Tue, 4 Jun 2019, Ronald F. Guilmette wrote: > > > Grrr. I can't imagine why this would be so hard. I didn't think > > what I wanted to do would be so complex. Again, I just want a > > digital xclock to appear in the blank space

Re: FVWM: FvwmForums: Change of engine and help with theming

2019-06-05 Thread Glenn Golden
Lucio Chiappetti [2019-06-05 11:59:15 +0200]: > On Wed, 5 Jun 2019, Thomas Adam wrote: > > > On Tue, Jun 04, 2019 at 07:46:02PM -0400, Dan Espen wrote: > > > Sorry, no inclination to follow a forum. Wish we'd go back to > > > exclusively email. > > > I personally don't disagree -- but you

Re: FVWM: two questions about icons

2019-06-05 Thread Dan Espen
"Ronald F. Guilmette" writes: > In message , > Dan Espen wrote: > Sorry, for FvwmCommand to work you need this in your config: AddToFunc StartFunction I Module FvwmCommandS > > OK, so now I have the following two commands added to my ~/.fvwm2rc > file and I am still gitting the

Re: FVWM: FvwmForums: Change of engine and help with theming

2019-06-05 Thread Lucio Chiappetti
On Wed, 5 Jun 2019, Thomas Adam wrote: On Tue, Jun 04, 2019 at 07:46:02PM -0400, Dan Espen wrote: Sorry, no inclination to follow a forum. Wish we'd go back to exclusively email. I personally don't disagree -- but you know what the old maxim says: "Give the people what they want". It

Re: FVWM: two questions about icons

2019-06-05 Thread Lucio Chiappetti
On Tue, 4 Jun 2019, Ronald F. Guilmette wrote: Grrr. I can't imagine why this would be so hard. I didn't think what I wanted to do would be so complex. Again, I just want a digital xclock to appear in the blank space below the xbiff thingy in the default theme. AFAIK there is no such thing

Re: FVWM: FvwmForums: Change of engine and help with theming

2019-06-05 Thread Thomas Adam
On Tue, Jun 04, 2019 at 07:46:02PM -0400, Dan Espen wrote: > Ever since Fvwm started using forums, I find I can't track everything > going on. Sorry, no inclination to follow a forum. Wish we'd go back to > exclusively email. :) I personally don't disagree -- but you know what the old maxim