unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stuart D. Herring" <herring@lanl.gov>
Cc: Juanma Barranquero <lekktu@gmail.com>,
	Eli Zaretskii <eliz@gnu.org>, Jason Rumney <jasonr@gnu.org>,
	Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Ftp freezes on w32
Date: Tue, 7 Nov 2006 09:00:15 -0800 (PST)	[thread overview]
Message-ID: <50172.128.165.123.18.1162918815.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <4550A650.7000808@student.lu.se>

> Am I the only person here using ange-ftp (through tramp of course) on
> w32???

I may have some helpful comments on your previous email, but they're not
solid yet.  For now:

> I have tried a couple of workarounds, but none has worked as I wish yet.
> What I thought would work was to kill and restart the ange ftp process
> in ange-ftp-send-cmd when ange-ftp-process-filter finds that the  ftp
> process sends just nulls. I tried something like this then
>
>     (delete-process proc)
>    (while (not (eq 'exit (process-status proc)))
>      (sit-for 1)
>      (sleep-for 1) ;; Hope one of them works
>     (message "process-status=%s" (process-status proc)))
>
> This just loops and tells that the process is "signaled". Is there
> something else I can do here? (I have tried kill-process too with the
> same result.) I thought that sit-for or sleep-for would give Emacs a
> chance to finish the ftp process, but it does not seem so.

Look at the docs for `process-status'.  A return of `signal' means that
the process -is dead-, and that it was killed by a signal (rather than
exiting of its own volition, which yields `exit').  You got exactly what
you wanted.  (You can check which signal killed it with
`process-exit-status'.)

Davis

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.

  parent reply	other threads:[~2006-11-07 17:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-04 11:21 Ftp freezes on w32 Lennart Borgman
2006-11-05  0:29 ` Lennart Borgman
2006-11-05 12:51   ` Lennart Borgman
2006-11-07  1:14     ` Lennart Borgman
2006-11-07  8:13       ` Lennart Borgman
2006-11-07  8:23       ` Lennart Borgman
2006-11-07 15:29         ` Lennart Borgman
2006-11-07 16:53           ` Jason Rumney
2006-11-07 17:02             ` Lennart Borgman
2006-11-07 17:00           ` Stuart D. Herring [this message]
2006-11-07 18:45             ` Lennart Borgman
2006-11-07 22:30               ` Lennart Borgman
2006-11-08  4:08                 ` Eli Zaretskii
2006-11-08  7:20                   ` Lennart Borgman
2006-11-09  4:23                     ` Eli Zaretskii
2006-11-12 12:13                       ` Lennart Borgman
2006-11-09  0:53                   ` Richard Stallman
2006-11-07  8:25       ` Lennart Borgman

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=50172.128.165.123.18.1162918815.squirrel@webmail.lanl.gov \
    --to=herring@lanl.gov \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=lekktu@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 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).