[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: don't just seek to the next line if the script has been edited

From: jidanni
Subject: Re: don't just seek to the next line if the script has been edited
Date: Sat, 08 Jun 2013 07:16:56 +0800

>>>>> "CR" == Chet Ramey <address@hidden> writes:
CR> I think the correct solution is to retain this behavior where it is
CR> required (e.g., when reading a script from the standard input) and to
CR> discard it when reading a script from a file.  This doesn't directly
CR> address the jidanni's concern, but I think the actual occurrence of this
CR> problem is infrequent enough to not do anything more elaborate.

All I know is there I am in emacs seeing things in the output of a
running bash script that I want to tweak and get busy tweaking and saving
changes before the script finishes, thinking that all this stuff will be
effective on the next run of it, when lo and behold now it begins
executing random bytes... Yes one can say that these are not C programs
and one needs to revise ones expectations, but still I think some
parental safety cap is required to keep it from munching random bytes
which will always be wrong... such overly dynamic-ness can never be a
feature and always be a wild incident unless one gets the alignment just
right etc. etc.

Anyway my problem is always for scripts on disk and not for the stdin
case so maybe I'm covered by the coming changes.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]