[comp.mail.elm] ctrl-c

cs9h7atw@cybaswan.UUCP (Alex Williams) (05/25/89)

Hello,
	has anyone a tip about why if we use ctrl-c for escape in vi when elm
brings it up that elm should say 

	"Problems invoking editor /usr/ucb/vi"

The screen then doesn`t refresh and a ctrl-l must be used. (Our escape key
which is supposed to produce a ctrl-c s fine)
	We have vt220`s (running vt100 usually) on a pyramid 9820 (aargh!).
Everything else accepts ctrl-c ok.
	Any help would be much appreciated. 

					Thanks

						Alex

rob@PacBell.COM (Rob Bernardo) (05/27/89)

In article <464@cybaswan.UUCP> cs9h7atw@cybaswan.UUCP (Alex Williams) writes:
+
+Hello,
+	has anyone a tip about why if we use ctrl-c for escape in vi when elm
+brings it up that elm should say 
+
+	"Problems invoking editor /usr/ucb/vi"

This message will occur when the shell that ELM executes for your editor
exits with non zero. Could it be that you have ^C set as your interrupt signal,
and that your shell is not ignoring it and dying and therefore not terminating
normally?
-- 
Rob Bernardo, Pacific Bell UNIX/C Reusable Code Library
Email:     ...![backbone]!pacbell!pbhyf!rob   OR  rob@pbhyf.PacBell.COM
Office:    (415) 823-2417  Room 4E850O San Ramon Valley Administrative Center
Residence: (415) 827-4301  R Bar JB, Concord, California

david@wubios.wustl.edu (David J. Camp) (05/28/89)

In article <464@cybaswan.UUCP> cs9h7atw@cybaswan.UUCP (Alex Williams) writes:
:
:Hello,
:	has anyone a tip about why if we use ctrl-c for escape in vi when elm
:brings it up that elm should say 
:
:	"Problems invoking editor /usr/ucb/vi"

elm does something like this to me when I use ^Z to suspend vi
temporarily.  Luckily, the edited message can be retrieved when I
reenter reply or forward mode.  It would be better if elm would just
send them message the first time, but I do not know what the code looks
like.
-David-

:
:The screen then doesn`t refresh and a ctrl-l must be used. (Our escape key
:which is supposed to produce a ctrl-c s fine)
:	We have vt220`s (running vt100 usually) on a pyramid 9820 (aargh!).
:Everything else accepts ctrl-c ok.
:	Any help would be much appreciated. 
:
:					Thanks
:
:						Alex


-- 
Bitnet:   david@wubios.wustl                ^      Mr. David J. Camp
Internet: david%wubios@wucs1.wustl.edu    < * >    Box 8067, Biostatistics
uucp:     uunet!wucs1!wubios!david          v      660 South Euclid
Washington University (314) 36-23635               Saint Louis, MO 63110

root@texbell.swbt.com (greg) (05/28/89)

In article <471@wubios.wustl.edu> david@wubios.UUCP (David J. Camp) writes:
>:	"Problems invoking editor /usr/ucb/vi"
>
>elm does something like this to me when I use ^Z to suspend vi
>temporarily.  Luckily, the edited message can be retrieved when I
>reenter reply or forward mode.  It would be better if elm would just
>send them message the first time, but I do not know what the code looks
>like.

In editmsg.c, the code looks like this:

	if ((stat = system_call(buffer, SH, TRUE)) != 0) { 
	  dprint(1,(debugfile, 
		  "System call failed with stat %d (edit_the_message)\n", 
		  stat));
	  dprint(1, (debugfile, "** %s - %s **\n", error_name(errno), 
		error_description(errno)));
	  ClearLine(LINES-1);
	  error1("Can't invoke editor '%s' for composition.", editor);
	  sleep(2);
	  return_value = 1;
	}

And in odd situations (like mine) can be changed
to ignore return codes:

	stat = system_call(buffer, SH, TRUE);

Some suggest using a fake shell script that invokes the editor, and always
exits with zero.

-- 
Greg        Internet: hack@texbell.swbt.com         Southwestern Bell
Hackney     UUCP: {rutgers,bellcore}!texbell!hack   Telephone Company

cs9h7atw@cybaswan.UUCP (Alex Williams) (06/01/89)

In article <970@texbell.swbt.com> root@texbell.swbt.com (Greg Hackney) writes:
>In article <471@wubios.wustl.edu> david@wubios.UUCP (David J. Camp) writes:
>>:	"Problems invoking editor /usr/ucb/vi"
>>
>>elm does something like this to me when I use ^Z to suspend vi
>>temporarily.  Luckily, the edited message can be retrieved when I
>>reenter reply or forward mode.  It would be better if elm would just
>>send them message the first time, but I do not know what the code looks
>>like.
>
>In editmsg.c, the code looks like this:
>
>	if ((stat = system_call(buffer, SH, TRUE)) != 0) { 
>	  dprint(1,(debugfile, 
>		  "System call failed with stat %d (edit_the_message)\n", 
>		  stat));
>	  dprint(1, (debugfile, "** %s - %s **\n", error_name(errno), 
>		error_description(errno)));
>	  ClearLine(LINES-1);
>	  error1("Can't invoke editor '%s' for composition.", editor);
>	  sleep(2);
>	  return_value = 1;
>	}
>
>And in odd situations (like mine) can be changed
>to ignore return codes:
>
>	stat = system_call(buffer, SH, TRUE);
>
>Some suggest using a fake shell script that invokes the editor, and always
>exits with zero.

Thanks greg,

	This is how I have *fixed* it :-)

	if ((stat = system_call(buffer, SH, TRUE)) !=0 ) { 
	  dprint(1,(debugfile, 
		  "System call failed with stat %d (edit_the_message)\n", 
		  stat));
	  dprint(1, (debugfile, "** %s - %s **\n", error_name(errno), 
		error_description(errno)));

	if(errno!=1)
	{
		ClearLine(LINES-1);
		error1("Can't invoke editor '%s' for composition.", editor);
		sleep(2);
		return_value = 1;
	}
	else
	  return_value = 0;
	
	}

-- 
Janet: pyr.swan.ac.uk					 UUCP : cybaswan.uucp

Alex Williams:	 Department of Computer Scence, University College Swansea,
		 	Singleton Park, Swansea, Wales.