[comp.windows.x] Bug in xmh

fuller@isctsse.UUCP (Bill Fuller) (07/13/89)

Hi,

	I am having problems with xmh on a SUN 4/110 running SunOS 4.0.1.
The problem is that when a user wants to reply to a mail message, the program
dies stating:

 No such file or directory
RenameAndCheck(/home/kadsma/fuller/Mail/draft->/home/kadsma/fuller/Mail/drafts/4
) failed!
errno = 2
exiting.

	Can someone give me the patch that fixes this bug for SunOS 4. 

			Thanks,

			William H. Fuller
			Senior Systems Consultant

swick@ATHENA.MIT.EDU (Ralph R. Swick) (07/13/89)

> RenameAndCheck(/home/kadsma/fuller/Mail/draft->/home/kadsma/fuller/Mail/drafts/4) failed!

Sounds like something may be wrong at the mh level.  Try running repl
from a shell command level and see if it gives any mh diagnostics.

In the next release xmh will display any mh diagnostic messages rather
than hiding them as it currently does.

ntitley@cocoa.axion.bt.co.uk (Nigel Titley) (08/04/89)

There is a bug in xmh which causes the `ReplyInsertFilter' function not to
work on System V.

The bug is in the function `ExecMsgInsertAssoc' which is to be found in
module `msg.c'. It is caused by the difference in behaviour in sprintf
between BSD and System V.

The following diff fixes the problem

772,774d771
< 	sprintf(command, "%s %s",
< 		 app_resources.defInsertFilter,
< 		 MsgFileName(scrn->assocmsg));
777c774,776
< 	argv[2] = command;
---
> 	argv[2] = (char*)sprintf(command, "%s %s",
> 				 app_resources.defInsertFilter,
> 				 MsgFileName(scrn->assocmsg));

Email: NTitley@axion.bt.co.uk
Snail: British Telecom Research labs, Martlesham Heath, Ipswich, Suffolk, UK
"Well, I'm disenchanted too. We're all disenchanted." (James Thurber)

converse@EXPO.LCS.MIT.EDU (Donna Converse) (08/07/89)

> There is a bug in xmh which causes the `ReplyInsertFilter' function not to
> work on System V.

Correct, and the fix is correct once you realize that the diff was produced
with the original and fix files reversed.   Fixed here (long ago) for R4.

A reminder: please report bugs using the template in doc/bugs/bug-report,
sending it to the address in the template, xbugs@expo.lcs.mit.edu.   Doing 
so guarantees our attention; and if the bugs are severe or substantial, we
would announce a patch available to the public.    The code diffs should
show the context of the changes (use -c -b), and the original file should be
the first file, the fixed file second.   Details of the problem and sample
fixes are genuinely appreciated.

Thanks,

Donna Converse
converse@expo.lcs.mit.edu