-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Sep 28, 2015 at 04:00:30PM -0400, Bob Bernstein wrote:
> I run alpine, built from source, on my Jessie:
>
> $ uname -a
> Linux debian.localdomain 3.16.0-4-amd64 #1 SMP Debian
> 3.16.7-ckt11-1+deb8u4 (2015-09-19) x86_64 GNU/Linux
[...]
Independently of what others have said...
> But wait! Now I see my new hand-cranked config is not behaving;
> changes made are not working. I close alpine, and as I edit in jed
> the .pinerc lines that are misbehaving I notice they have been
> altered ("corrupted"). Then (my hand to God I) AS I STARE AT THE
> LINES IN JED CHARACTERS ARE CHANGING "ON THEIR OWN" WITHOUT ME
> TOUCHING A KEY.
...this strikes me most. I haven't jed (nor have I any experience
with it), but is jed set up to re-sync with changes made to the
file behind its back? For other editors this isn't typical (at least
not by default).
So even if "anything" (perhaps some rouge instance of alpine) is
making changes to the file, why/how should jed display those "real
time"?
That said, lsof would tell you which processes hold a file open
at a given time.
Bizarre, to put it mildly :-)
regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlYKM3EACgkQBcgs9XrR2kbEkACfQPFgn2zmAK57ymTYeLKHS3AF
54MAnA2LTvqCWL+itKMRvj/STSALInO2
=Qanv
-----END PGP SIGNATURE-----
