[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: Linda Walsh
Subject: Re: don't just seek to the next line if the script has been edited
Date: Sun, 09 Jun 2013 13:59:15 -0700
User-agent: Thunderbird

address@hidden wrote:

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
If they were C programs, and you were to edit binary in place, while it was
executing, using memory-mapped I/O, the machine might very well start executing
garbage and your C program would dump core or similar.

Chances are, your text editor is writing to the same file as it read from
rather than writing your program to a new file and moving the old off to a

If your text editor always stored your new input in a new file you wouldn't
see this behavior.  Emacs is supposed to be configurable .. I know vim will
do different things based on if the file has hard links or not (it will try
not to break them, otherwise it's a new file each time)...

reply via email to

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