Linux fvwm1.24r-25 vs Sun fvwm1.24r

1997-04-03 Thread Steve Hsieh

Has anyone else had problems using a working .fvwmrc file from a Sun
system on Debian?  Since fvwm on both systems is the same, I wouldn't
expect such difficulties, but it seems that some things which work on fvwm
for SunOS/Solaris cause a seg fault on Debian fvwm.  Maybe the true
culprit lies with a utility program somewhere and not fvwm itself?

For example, the following .fvwmrc line works on Sun, but not on Debian
for me (it's the backquotes that are the problem):

# Personal items
Popup My Utilities
Title   My Utilities
ExecXterm exec xterm -n `hostname|cut -f1 -d.` -T 
`hostname` -e tcsh 
EndPopup

On debian linux this results in the message
NONE:0: m4: ERROR: EOF in string
and then a fvwm segmentation fault.

Using the stock fvwmrc file provided with Debian of course works just
fine, but since we use a mix of different operating machine types here,
this is a problem I hope can be resolved. 

Can anyone tell from the above if this is due to a user configuration
error, or a bug that I should report to the fvwm maintainer? 

Thanks.

--
Stephen Hsieh  Dept. of Electrical Engineering and Computer Science
[EMAIL PROTECTED]  Univ. of Michigan at Ann Arbor
---



Re: Linux fvwm1.24r-25 vs Sun fvwm1.24r

1997-04-03 Thread Rick Macdonald
On Thu, 3 Apr 1997, Steve Hsieh wrote:

 Has anyone else had problems using a working .fvwmrc file from a Sun
 system on Debian?  Since fvwm on both systems is the same, I wouldn't
 expect such difficulties, but it seems that some things which work on fvwm
 for SunOS/Solaris cause a seg fault on Debian fvwm.  Maybe the true
 culprit lies with a utility program somewhere and not fvwm itself?

 On debian linux this results in the message
 NONE:0: m4: ERROR: EOF in string
 and then a fvwm segmentation fault.

You might look through the Info file for the m4 utility.
It states that the GNU m4 is different fom the Unix Sys V.

A good time to check out tkinfo!   :-)

...RickM...


Re: Linux fvwm1.24r-25 vs Sun fvwm1.24r

1997-04-03 Thread Austin Donnelly
On Thu, 3 Apr 1997, Rick Macdonald wrote:

 On Thu, 3 Apr 1997, Steve Hsieh wrote:
 
  Has anyone else had problems using a working .fvwmrc file from a Sun
  system on Debian?  Since fvwm on both systems is the same, I wouldn't
  expect such difficulties, but it seems that some things which work on fvwm
  for SunOS/Solaris cause a seg fault on Debian fvwm.  Maybe the true
  culprit lies with a utility program somewhere and not fvwm itself?
 
  On debian linux this results in the message
  NONE:0: m4: ERROR: EOF in string
  and then a fvwm segmentation fault.
 
 You might look through the Info file for the m4 utility.
 It states that the GNU m4 is different fom the Unix Sys V.

This is most likely the cause.

Steve, can you please mail me the .fvwmrc which is failing for you.
I'll take a look to make sure that this is the case.

Austin
Debian fvwm/fvwm2 maintainer


SOLUTION: Linux fvwm1.24r-25 vs Sun fvwm1.24r

1997-04-03 Thread Steve Hsieh
For the benefit of the archive lists and in case anyone else was
wondering, here's the answer to my problem. 

The default fvwm behavior is not to use m4, but the Debian/Linux fvwm
package has been compiled to use m4. Since m4 quotes using ` and ', the
result is that the backquotes in the .fvwmrc file causes an error.  The
solutions are: 

1. call fvwm with the -no-m4 option 
2. redfine how m4 quotes literals.  Using the fvwm -m4-squote and
-m4-equote options may also do the trick (I didn't try).

Thanks to Dan Astoorian [EMAIL PROTECTED], Niels
[EMAIL PROTECTED], and Rick Macdonald [EMAIL PROTECTED] for their help
in solving this problem.

Steve


On Thu, 3 Apr 1997, Rick Macdonald wrote:

 On Thu, 3 Apr 1997, Steve Hsieh wrote:
 
  Has anyone else had problems using a working .fvwmrc file from a Sun
  system on Debian?  Since fvwm on both systems is the same, I wouldn't
  expect such difficulties, but it seems that some things which work on fvwm
  for SunOS/Solaris cause a seg fault on Debian fvwm.  Maybe the true
  culprit lies with a utility program somewhere and not fvwm itself?
 
  On debian linux this results in the message
  NONE:0: m4: ERROR: EOF in string
  and then a fvwm segmentation fault.
 
 You might look through the Info file for the m4 utility.
 It states that the GNU m4 is different fom the Unix Sys V.
 
 A good time to check out tkinfo!   :-)
 
 ...RickM...