From: Fabrice Popineau <Fabrice.Popineau@supelec.fr>
Cc: ding@gnus.org, xemacs-nt@xemacs.org
Subject: Re: problem sending mail by modem
Date: 06 Jan 2000 23:48:32 +0100 [thread overview]
Message-ID: <u7lhmolz3.fsf@supelec.fr> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "06 Jan 2000 23:22:06 +0100"
* Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> Could it be the same problem for you? Do ptys even exist on NT?
Hmmm... My performance dies way before x100k : rather around x100
bytes. And there are no ptys under native build, but if the problem is
at the elisp level, it could be something similar, assuming the
difference between net connection and modem throughput is a sufficient
explanation.
I should try to send a x1Mb file through the net connection to see if
it is reproducible. On the other hand, I recall a few monthes ago to
have been able to send messages more than 1 page long without any
problem, even by modem.
Fabrice
next prev parent reply other threads:[~2000-01-06 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-06 22:03 Fabrice Popineau
2000-01-06 22:22 ` Kai Großjohann
2000-01-06 22:48 ` Fabrice Popineau [this message]
2000-01-06 23:03 ` Kai Großjohann
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=u7lhmolz3.fsf@supelec.fr \
--to=fabrice.popineau@supelec.fr \
--cc=ding@gnus.org \
--cc=xemacs-nt@xemacs.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 NNTP newsgroup(s).