all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 7383@debbugs.gnu.org
Subject: bug#7383: 24.0.50; end-of-line style on remote files
Date: Wed, 04 May 2011 15:04:22 +0200	[thread overview]
Message-ID: <87ei4eaa7d.fsf@gmx.de> (raw)
In-Reply-To: <BANLkTin_UAsMHYyUKzg5fy1hkxiu5qMnsA@mail.gmail.com> (Dani Moncayo's message of "Wed, 4 May 2011 11:32:19 +0200")

Dani Moncayo <dmoncayo@gmail.com> writes:

> So now I wonder two things:
> 1. In what cases do we want to have text-mode ftp transfers when
> working with remote files?
>    Because, IMO TRT would be to always use binary mode, i.e., always
> work with the file
>    in its actual EOL format. I think that is what users expect, don't they?

See the code of `ange-ftp-write-region'. Binary transfer is explicitely
disabled for Emacsen on MS Windows machines, if not said otherwise by
`ange-ftp-binary-file-name-regexp':

	       (binary (or (ange-ftp-binary-file filename)
			   (and (not (memq system-type
					   '(ms-dos windows-nt)))
				(memq (ange-ftp-host-type host user)
				      '(unix dumb-unix)))))

Similar (but not identical) checks are in `ange-ftp-insert-file-contents'
and `ange-ftp-copy-file-internal'.

And there are comments about it, like "Binary file transfers between
machines of different architectures can be a risky business.".

> 2. This bug report has showed that the modeline flag corresponding to the EOL
>    format isn't always correct. So I think this should be fixed if possible,
>    and if not, this limitation should be documented at least.

Emacs can show only, what it knows. It sends a given file to the FTP
client. It cannot know, whether that external program changes EOL
conversion.

Likely, we shall add a note to section 8.3 of the "GNU Emacs FAQ for MS
Windows", see <http://www.gnu.org/software/emacs/windows/Network-access.html#Network-access>

> Thanks for your time, Michael.

Best regards, Michael.





  parent reply	other threads:[~2011-05-04 13:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 10:37 bug#7383: 24.0.50; end-of-line style on remote files Dani Moncayo
2011-04-28  8:48 ` Dani Moncayo
2011-04-28 10:17   ` Michael Albinus
     [not found]     ` <BANLkTi=0FH=h2oEupQnsLPvvfTD7+_jsYA@mail.gmail.com>
2011-05-04 10:27       ` bug#7383: Fwd: " Dani Moncayo
     [not found]       ` <BANLkTi=+ygu=_h78Agus=iLc_eGxFf4DGA@mail.gmail.com>
2011-05-04 10:29         ` Dani Moncayo
     [not found]         ` <87wriek4ke.fsf@gmx.de>
2011-05-04 10:31           ` Dani Moncayo
     [not found]           ` <BANLkTimqmhxaMNGuC8cffR76hgN=yXeghQ@mail.gmail.com>
2011-05-04 10:32             ` Dani Moncayo
     [not found]             ` <87oc3qjxbl.fsf@gmx.de>
2011-05-04 10:33               ` Dani Moncayo
     [not found]               ` <BANLkTikRfEWAZc1ZPTYjeFqgLrp-8FZdqQ@mail.gmail.com>
2011-05-04 10:33                 ` Dani Moncayo
     [not found]                 ` <87bozmitut.fsf@gmx.de>
2011-05-04 10:34                   ` Dani Moncayo
     [not found]                   ` <BANLkTin_UAsMHYyUKzg5fy1hkxiu5qMnsA@mail.gmail.com>
2011-05-04 10:36                     ` Dani Moncayo
2011-05-04 13:04                     ` Michael Albinus [this message]
2011-05-04 15:14                       ` Stefan Monnier
2011-05-04 15:42                         ` Michael Albinus
2011-05-04 17:23                         ` Eli Zaretskii
2011-05-04 18:47                           ` Stefan Monnier
2011-05-04 20:17                             ` Eli Zaretskii
2011-05-05 10:24                               ` Michael Albinus
2011-05-06 17:49                                 ` Glenn Morris
2011-05-06 18:00                                   ` Michael Albinus
2011-05-06 18:07                                     ` Dani Moncayo

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=87ei4eaa7d.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=7383@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    /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.