unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Ehud Karni" <ehud@unix.mvs.co.il>
Cc: help-gnu-emacs@gnu.org
Subject: Re: File truncated at ^Z character in windows
Date: Wed, 18 Feb 2004 10:26:06 +0200	[thread overview]
Message-ID: <200402180826.i1I8Q6kP008705@beta.mvs.co.il> (raw)
In-Reply-To: <1438-Tue17Feb2004221318+0200-eliz@elta.co.il> (message from Eli Zaretskii on Tue, 17 Feb 2004 22:13:18 +0200)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 17 Feb 2004 22:13:18 +0200, Eli Zaretskii <eliz@elta.co.il> wrote:
>
> > From: John Russell <jorussel AT cisco.com>
> > Date: 17 Feb 2004 14:15:12 -0500
> >
> > I copied the offending file from a samba share on my linux machine
> > over to the windows machine.  I didn't open it or edit it with any
> > editor until NTEmacs opened it.
>
> So it sounds like samba did this.

I don't think it is a samba problem. We employ a samba (on GNU/Linux)
with a share of over 50GB and about 200 M$Windows users. It is working
over 3 years and no one reported any such problem.

- From my experience it work just like any M$Windows share.

The only way it can happen is if the copy was a TEXT copy (i.e. not
binary).  The M$Windows `copy' has switches that control its mode:
  /A           Indicates an ASCII text file.
  /B           Indicates a binary file.

> Anyway, the advice to move the files in an archive, like a tar.gz
> file, is still valid, I think.

I think that is because the M$Windows `copy' select the mode (text/
binary) according to the file extension if not specified explicitly.

Ehud.


- --
 Ehud Karni           Tel: +972-3-7966-561  /"\
 Mivtach - Simon      Fax: +972-3-7966-667  \ /  ASCII Ribbon Campaign
 Insurance agencies   (USA) voice mail and   X   Against   HTML   Mail
 http://www.mvs.co.il  FAX:  1-815-5509341  / \
 GnuPG: 98EA398D <http://www.keyserver.net/>    Better Safe Than Sorry
-----BEGIN PGP SIGNATURE-----
Comment: use http://www.keyserver.net/ to get my key (and others)

iD8DBQFAMyGdLFvTvpjqOY0RAvnKAJ0fE0Im1u2jdYuXVfLiJX/Y0X30lwCfcIZ0
QHq11DqDKOBokIxd6C5Bbdk=
=f9mi
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-02-18  8:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 21:03 File truncated at ^Z character in windows John Russell
2004-02-14  8:43 ` Alan Mackenzie
2004-02-17 19:17   ` John Russell
2004-02-14 11:52 ` Eli Zaretskii
     [not found] ` <mailman.2383.1076759638.928.help-gnu-emacs@gnu.org>
2004-02-17 19:15   ` John Russell
2004-02-17 20:13     ` Eli Zaretskii
2004-02-18  8:26       ` Ehud Karni [this message]
2004-02-18 10:51         ` Eli Zaretskii
     [not found]     ` <mailman.2587.1077048825.928.help-gnu-emacs@gnu.org>
2004-02-18 10:14       ` Michael M Mason
2004-02-18 10:36         ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200402180826.i1I8Q6kP008705@beta.mvs.co.il \
    --to=ehud@unix.mvs.co.il \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).