Re: Running editor while `cvs commit' not on terminal

[J. Cone]

There was a conversation sometime about changing the default behaviour to
something other than 'continue'.  That would be an improvement in this
situation.

At 14:14 04/06/01 -0400, Donald Sharp wrote:
>The '>' symbol tells the users shell to do something with the
>output.  cvs can do nothing( it doesn't know where it's stdout and
>stderr are going ) when the user does this.
>
>donald
>On Sun, Jun 03, 2001 at 08:41:05PM +0400, Alexey Mahotkin wrote:
>> 
>> I've seen several times report on the following misfeature: 
>> 
>> sometimes one inadvertantly runs 
>> 
>>        $ cvs commit > results 2>errors
>> 
>> After that things depend upon user's editor.  
>> 
>> In one case (vi not checking if on terminal) the user had to blindly
>> type "ESC:q!" and things seemed to be ok.
>> 
>> 
>> I checked that with VIM and got the following:
>> 
>> === <errors> ===
>> cvs commit: Examining .
>> ex/vi: Vi's standard input and output must be a terminal
>> cvs commit: warning: editor session failed
>> === </errors> ===
>> 
>> === <stdout> ===
>> Log message unchanged or not specified
>> a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining dirs
>> Action: (continue) Checking in hello.c;
>> /repos//testing/hello.c,v  <--  hello.c
>> new revision: 1.3; previous revision: 1.2
>> done
>> === </stdout> ===
>> 
>> 
>> I think that it is rare but very annoying case that should be fixed.
>> 
>> --alexm
>> 
>> _______________________________________________
>> Bug-cvs mailing list
>> Bug-cvs@gnu.org
>> http://mail.gnu.org/mailman/listinfo/bug-cvs
>
>_______________________________________________
>Bug-cvs mailing list
>Bug-cvs@gnu.org
>http://mail.gnu.org/mailman/listinfo/bug-cvs
>
>