Your message dated Wed, 3 Jan 2007 20:22:38 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: fvwm95
The FvwmM4 manpage mentions that the '-outfile' flag can be used
to specify the name of the temporary file that FvwmM4 writes to. This
doesnt work. Here is a patch for this :
-------------------------- Patch begins ------------------------------
diff -ur fvwm95-2.0.43ba.debian/modules/FvwmM4/FvwmM4.c
fvwm95-2.0.43ba.new/modules/FvwmM4/FvwmM4.c
--- fvwm95-2.0.43ba.debian/modules/FvwmM4/FvwmM4.c Tue Dec 10
10:41:45 1996
+++ fvwm95-2.0.43ba.new/modules/FvwmM4/FvwmM4.c Tue May 11 23:53:41 1999
@@ -67,6 +67,7 @@
int m4_default_quotes; /* Use default m4 quotes */
char *m4_startquote = "`"; /* Left quote characters for m4 */
char *m4_endquote = "'"; /* Right quote characters for m4 */
+char outfile[256] = "";
/***********************************************************************
*
@@ -156,6 +157,10 @@
{
m4_debug = 1;
}
+ else if(strcasecmp(argv[i], "-outfile") == 0)
+ {
+ strcpy(outfile,argv[++i]);
+ }
else
filename = argv[i];
}
@@ -204,13 +209,17 @@
/* Generate a temporary filename. Honor the TMPDIR environment
variable,
if set. Hope nobody deletes this file! */
- if ((vc=getenv("TMPDIR"))) {
- strcpy(tmp_name, vc);
- } else {
- strcpy(tmp_name, "/tmp");
+ if(strlen(outfile) != 0)
+ strcpy(tmp_name,outfile);
+ else{
+ if ((vc=getenv("TMPDIR"))) {
+ strcpy(tmp_name, vc);
+ } else {
+ strcpy(tmp_name, "/tmp");
+ }
+ strcat(tmp_name, "/fvwmrcXXXXXX");
+ mktemp(tmp_name);
}
- strcat(tmp_name, "/fvwmrcXXXXXX");
- mktemp(tmp_name);
if (*tmp_name == '\0')
{
----------------------------- Patch ends ------------------------------
Could you please see that this makes its way upstream, please?
Note that the html doc for FvwmM4 in /usr/doc/fvwm95 does not
mention this option. But before you "fix" this bug by removing this option
from the manpage (in /usr/X11R6/man/man1), let me explain to you why this
feature is very useful and should be preserved.
The only way of getting macros to work in fvwm95 (that I know off)
is via FvwmM4. And as far as I can tell, this means that the entire
fvwm95rc file must be preprocessed by FvwmM4. This is not good in terms
of performance since FvwmM4 is called upon to process stuff which are not
macros.
Using the 'outfile' flag, one can have an ordinary fvwm95rc file
and preprocess using FvwmM4 any external files having macros in them. What
one needs to do in the system.fvwm95rc file is :
FvwmM4 -debug -outfile <filename1> <filename2>
Read <filename1>
where <filename1> represents the output file produced by FvwmM4
and <filename2> is the file containing the macro definitions that needs to
be processed by FvwmM4. Here is an example :
>From /etc/X11/fvwm95/system.fvwm95rc :
AddToFunc "InitFunction" "I" Exec flame -root -delay 6000000
FvwmM4 -debug -outfile ~/.fvwmm4rc /etc/X11/fvwm95/init.hook
Read .fvwmm4rc
Read /etc/X11/fvwm95/init-restart.hook
Read .fvwm95/init.hook
Read .fvwm95/init-restart.hook
>From /etc/X11/fvwm95/init.hook :
#
# See the fvwm95 manual page for details (the AddToFunction
# command).
+ "I" Exec xterm -T "HOSTNAME"
Unfortunately, since the "Read" builtin cannot interpret the "~"
correctly, the command produced by the FvwmM4 invocation (and placed in
the pipe to process) is "Read ~/.fvwmm4rc" - and this causes an error to
appear in the ~/.xsession-errors file. However, this is totally harmless.
Jor-el
--- End Message ---
--- Begin Message ---
fvwm95 has been removed from Debian unstable/tesing because it's
unmaintained and abandoned upstream. Please move to fvwm2. If your
bug also shows up in fvwm2 please file a new bug report or let me
know.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
