Re: FVWM: FVWM Logo Competition

[John Wiggins]

> On Sep 6, 2016, at 10:27 AM, Lucio Chiappetti  wrote:
> 
> On Tue, 6 Sep 2016, Werner Scheinast wrote:
> 
>> FVWM has shrunk down to a - as you call it - crackpot project. Only few 
>> people are using it, these are mainly old guys like me (I'm 45) who know
> 
> Well then, who am I (61) ? Methuselah ? :-)
> 

Nope, guess would be me, as I turn 68 next month.  :-)

I copied a TWM config from a colleague at work around 1987/1988.   I switched 
to fvwm in the early 90s, perhaps from the same colleague at work.
FVWM was obviously better than TWM, and the virtual desktops was probably the 
major reason for the change.

I’ve stuck with fvwm all these years and platforms,  bothering to compile FVWM 
for systems that did not have it, because this WM does all I want and my 
interest was to preserve my workflow.
I am a touch typist, and similar to using emacs, my fingers just automatically 
do what I want, and I would probably need to look at what my fingers/hands do 
automatically to tell you about key or mouse-button bindiings.

There are perhaps a few folks even older than me on this list, and perhaps some 
who still use FVWM for similar reasons.
Perhaps  even a few (like me) who are using only slightly-modified .fvwm2rc 
files that hey copied from friends for colleagues ages ago.

BTW, my desktop bitmaps go back to TWM and have been dragged along all this 
time, too.

jw

FVWM: compile fvwm2.6.6 on macOS

[John Wiggins]

I am on MacOS and am still running an fvmw2 version  2.6.5  binary I compiled 
back in 2014 on two OSes and older development tools.
Does anyone have instructions on how to build fvwm for the latest macOS and 
XCode tools? 

I obtained fvwm-2.6.6.tar distribution from the http://fvwm.org root page.

My ./configure with the version 2.6.6 aborts.  I added echo to show shell 
variables before the abort.  Do I need to use set CPP to use clang?

$ ./configure
…snip…
checking whether it is safe to define __EXTENSIONS__... yes
CPP  gcc -E
CFLAGS   -Wall -Wno-implicit-int -g -O2
CPPFLAGS 
configure: error: "
configure is not able to compile programs with warnings.  Please
remove all offending options like -Werror from the CFLAGS and
CPPFLAGS variables and run configure again."
$


Question 2:  If I find this on my own, is there a platform-specific tips page 
for tips for compiling the distribution.  The fvwmforums.org does not seem to 
be very active.

tks,
jw

Re: FVWM: [Draft] New Configuration Format

[John Wiggins]

The python method has some serious defficiencies when applied to input files 
like .fvwmrc2, i.e. white space you cannot see (space vs tab) matters and cause 
read errors that drive you crazy…

IMO, the 
BlockB {
line1,
line2,
line3_and_white_space_doesNotMatter,
So_This_isValid,
andSPACESORTABS_DO_NOT_MATTER}


> BlockB {
> line1,
> line2,
> line3,
> line4
> }

> On Sep 21, 2016, at 9:49 PM, elliot s  wrote:
> 
> <<
> BlockA \
> line1, \
> line2, \
> line3, \
> line4
> 
> Is less visually appealing and can be more difficult locate errors than
> 
> BlockB {
> line1,
> line2,
> line3,
> line4
> }
>>> 
> 
> There's the python method of blockingusing indentation.  WYSIWYG
> I was skeptical at first, but now i like it.
> 
> if x:   # note the :
> y=z
>a=1
>if n:
>a=3
>b=1
>else:
>b = 0
>print a,b
> print y
> 

FVWM: FYI: fvwm3 does not build on MacOS Mojave 10.14.6 (strlcpy signature issue)

[John Wiggins]

I am not sure if this new to the fvwm3 base or not, as this is my first build 
attempt of fvwm since 2.6.7 November 2016.
Not critical for me at this times as fvwm-2.6.9 build is working for me


However,  the fvwm-2.6.9 make it does have warnings, among them
In file included from gravity.c:18:
../config.h:506:12: warning: non-portable path to file ''; 
specified path differs in case from file name on disk 
[-Wnonportable-include-path]
#  include 
   ^~~
   

My steps for failed fvwm3 build were:


   $ ./autogen.sh
   $ mkdir /Users/jw/Downloads/fvwm3
   $ ./configure --prefix=/Users/jw/Downloads/fvwm3
   $ make
   
and I enclose (small) attachment with the output of the make command.  I am 
willing to try any suggestions that are simple enough for me to understand.


Thanks,
jw



make.out
Description: Binary data