unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: 7383@debbugs.gnu.org
Subject: bug#7383: Fwd: bug#7383: 24.0.50; end-of-line style on remote files
Date: Wed, 4 May 2011 12:36:03 +0200	[thread overview]
Message-ID: <BANLkTinfJYLtqrF1tC6SYfNWkas0vEy2cw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin_UAsMHYyUKzg5fy1hkxiu5qMnsA@mail.gmail.com>

[I'm forwarding some messages to the mailing list, because I
unintentionally replied privately.]


---------- Forwarded message ----------
From: Dani Moncayo <dmoncayo@gmail.com>
Date: Wed, May 4, 2011 at 11:32
Subject: Re: bug#7383: 24.0.50; end-of-line style on remote files
To: Michael Albinus <michael.albinus@gmx.de>


On Sun, May 1, 2011 at 12:43, Michael Albinus <michael.albinus@gmx.de> wrote:
>
> Maybe you play with `ange-ftp-binary-file-name-regexp' settings, for
> example set it to "".
>

Sorry for the delay. These days I had no access to the Windows XP box
where I reproduce the problem.  (BTW, at home I was unable to
reproduce it using a Windows 7 client and  Ubuntu 10.10 ftp server).

Well, if I do what you said ((setq ange-ftp-binary-file-name-regexp
"")), then the problem seem to disappear in the quick test I've done.

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?

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.


Thanks for your time, Michael.

--
Dani Moncayo





  parent reply	other threads:[~2011-05-04 10:36 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 [this message]
2011-05-04 13:04                     ` Michael Albinus
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

  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=BANLkTinfJYLtqrF1tC6SYfNWkas0vEy2cw@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=7383@debbugs.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).