[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV Save to disk glitch followup.
From: |
T.E.Dickey |
Subject: |
Re: LYNX-DEV Save to disk glitch followup. |
Date: |
Wed, 30 Jul 1997 13:58:10 -0400 (EDT) |
>
> On Wed, 30 Jul 1997, Larry W. Virden, x2487 wrote:
>
> > That stop_curses() call is needed though. Otherwise, if the program
> > being called tries to write to the terminal and read a response, say, like
> > ckermit, etc. the user has a dickens of a time trying to read or write
> > the info needed.
>
> Note that in this specific case, the "program being called" is just an
> invocation of whatever is defined as COPY_PATH. So unless you have an
> unusual way of copying files and have changed userdefs.h accordingly,
> it's just "cp" (or "/your/path/to/bin/cp"). No response to enter, and
> no writing to the terminal if everything goes right.
unless, of course, you are copying to a file that is readonly. then you're
likely to get a prompt, even if you don't specify the -i option.
> A possible "unusual way of copying files" might be having a script that
> does the equivalent of "cp -i" (asking for confirmation before overwriting
> a file) - in that case your point would apply.
>
> Klaus
>
>
>
> ;
> ; To UNSUBSCRIBE: Send a mail message to address@hidden
> ; with "unsubscribe lynx-dev" (without the
> ; quotation marks) on a line by itself.
> ;
>
--
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;