unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Eric Klaus" <etklaus@gmail.com>
To: "Michael Albinus" <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Ange-ftp: Getting files with no extension on dumb hosts
Date: Thu, 9 Oct 2008 10:11:03 -0500	[thread overview]
Message-ID: <612c9da00810090811p541fb238g14ddba0006d62a5b@mail.gmail.com> (raw)
In-Reply-To: <87myhdx2u5.fsf@alcatel-lucent.de>

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

Interestingly, I can't get Ange-FTP to correctly open _any_ file from my
dumb host. I'm not sure what I was doing differently before, but I can't
seem to open any file now.

I suppose that this error message means that I'm going to have to roll my
own set of commands for this particularly dumb host? I believe my host is an
AS/400; I'm not sure why it seems to have such lackluster ftp support.


On Thu, Oct 9, 2008 at 9:25 AM, Michael Albinus <michael.albinus@gmx.de>wrote:

> "Eric Klaus" <etklaus@gmail.com> writes:
>
> > quote mdtm /home/prodjava/start_batch_PostureNote/
> > 250 List completed.
> > ftp: 91 bytes received in 0.00Seconds 91000.00Kbytes/sec.
> > 500 Subcommand MDTM not valid.
>
> I would say this is rather the problem. Ange-FTP does not know how to
> handle the error message.
>
> However, in order to compare the behaviour, I'd like to see another
> ange-ftp buffer, when opening a file successfully (i.e., a file with a
> name extension).
>
> Best regards, Michael.
>

[-- Attachment #2: Type: text/html, Size: 1435 bytes --]

  reply	other threads:[~2008-10-09 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 21:41 Ange-ftp: Getting files with no extension on dumb hosts Eric
2008-10-09  7:20 ` Michael Albinus
2008-10-09 14:21   ` Eric Klaus
2008-10-09 14:25     ` Michael Albinus
2008-10-09 15:11       ` Eric Klaus [this message]
2008-10-10 12:20         ` Michael Albinus

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=612c9da00810090811p541fb238g14ddba0006d62a5b@mail.gmail.com \
    --to=etklaus@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).