File-system wise, on save, the file is created from 0 bytes and repopulated,
so SEC might not know that it was a user-edit.
This could happen with nano (pico), try a more powerful editor like vim (or
emacs).
--
Justin J. Novack
Official Disturber of the Peace
On Wed, Oct 19, 2011 at 6:55 AM,
Yes it is happening with vim.
Is there any way to tell SEC not to repopulate?
On Wed, Oct 19, 2011 at 5:01 PM, Justin J. Novack jnov...@gmail.com wrote:
File-system wise, on save, the file is created from 0 bytes and repopulated,
so SEC might not know that it was a user-edit.
This could
Even if it were possible to delete say 100 bytes from the front of the
file, how would SEC know that it needed to skip back 100 bytes to keep
it's concept of the current location in the file? Imagine a scenario
with multiple write to the end of the file, some of which SEC has
processed, but some
