From: Will Willis <will.willis@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: TRAMP corrupting files
Date: Fri, 8 May 2009 00:44:46 -0500 [thread overview]
Message-ID: <6ee1e6090905072244j13994d04kca17ba993a205ed0@mail.gmail.com> (raw)
I'm using Tramp from my Mac to edit remote files. Twice in the last
few days I've experienced Tramp corrupting my files.
The first corruption happened mid way through a PHP file, looking like this:
...
<option value="C"<?=$uresult['store_cluster']=="C"?"
selected":""?>>Cluster C</option>
<opv˷⌀ 䛆需戀܀㜀䜀阀
I think the characters might have been encoded above. What I see in
emacs is this
...
<option value="C"<?=$uresult['store_cluster']=="C"?"
selected":""?>>Cluster C</option>
<opv\367^B#\340\240\220\223\306...
This corruption goes on for 35,202 characters (all on one line) then
the file ends.
The second time I had a file get corrupted, interestingly also in a
PHP file inside of a <select> option group, There were not funky
characters, just a few dozen lines of missing from my file.
It's really starting to scare me as I'm not sure I can trust this
method of remote file editing... My hosting company was able to assist
me once in recovering a backup... I'd have for this to happen again..
Is TRAMP known to do this sort of thing?
Are there Emacs alternatives to remote file editing (w/o corruption)?
Thanks.
Carbon Emacs "22.2.1"
Tramp "2.0.57"
next reply other threads:[~2009-05-08 5:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 5:44 Will Willis [this message]
2009-05-18 22:35 ` TRAMP corrupting files Ian Eure
2009-05-19 1:40 ` Will Willis
2009-05-19 5:17 ` TRAMP corrupting files (it's OS X's fault) Daniel Colascione
2009-05-19 21:39 ` Will Willis
2009-05-26 19:57 ` Michael Albinus
2009-05-26 21:17 ` Daniel Colascione
2009-05-27 3:44 ` Michael Albinus
[not found] <mailman.6834.1241761494.31690.help-gnu-emacs@gnu.org>
2009-05-08 8:21 ` TRAMP corrupting files Anselm Helbig
2009-05-09 2:01 ` Will Willis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ee1e6090905072244j13994d04kca17ba993a205ed0@mail.gmail.com \
--to=will.willis@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.