From: Ken Goldman <kgold@watson.ibm.com>
To: help-gnu-emacs@gnu.org
Subject: Re: ange-ftp using binary mode
Date: Thu, 23 Feb 2012 14:59:41 -0500 [thread overview]
Message-ID: <ji65re$kpg$1@dough.gmane.org> (raw)
In-Reply-To: <874nur9i0f.fsf@gmx.de>
On 2/16/2012 5:42 AM, Michael Albinus wrote:
> Ken Goldman<kgold@watson.ibm.com> writes:
>
>> On 2/10/2012 4:55 PM, Ken Goldman wrote:
>>> I have to use ange-ftp because the server I'm connecting to doesn't run
>>> ssh. When I transfer, it uses binary, which does not work. The server is
>>> a mainframe and likely uses ebcdic.
>>>
>>> If I ftp from the command line in ascii mode, the file comes over to
>>> Windows correctly. If I enter the commands by hand in the ange-ftp,
>>> setting ascii, it works.
>>>
>>> How do I tell ange-ftp to use ascii?
>>
>> Following up my own post, I edited ange-ftp.el and changed 'binary' to
>> ascii'. Files now come across absolutely perfectly.
>>
>> I know that's an awful hack, but it's a proof of concept. Now, how do
>> I convince ange-ftp to use ascii without editing the elisp source?
>
> Which Emacs version are you running?
>
> Last year, there was a bug report about ange-ftp's binary mode, see
> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7383>. IIRC, it was about
> ange-ftp always using binary mode, when your local system is MS
> Windows. This is fixed meanwhile.
>
> Chances are good, that a prerelease of Emacs 24.1 works for you out-of-the-box.
I looked at the bug reports, but they seem to be cases where people
__wanted__ binary mode. I have the opposite issue. I always want ASCII
mode so ftp will do the EBCDIC <-> ASCII conversion.
I'm running 23.1.1. I won't risk a pre-release when I have a source
code hack that works. I'll retest when 24 goes into production.
prev parent reply other threads:[~2012-02-23 19:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 21:55 ange-ftp using binary mode Ken Goldman
2012-02-11 7:01 ` Eli Zaretskii
2012-02-15 20:17 ` Ken Goldman
2012-02-15 20:49 ` Eli Zaretskii
2012-02-15 21:25 ` Ken Goldman
2012-02-14 13:54 ` Michael Albinus
2012-02-15 19:59 ` Ken Goldman
2012-02-15 21:30 ` Ken Goldman
2012-02-16 10:42 ` Michael Albinus
2012-02-23 19:59 ` Ken Goldman [this message]
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='ji65re$kpg$1@dough.gmane.org' \
--to=kgold@watson.ibm.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.
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).