Gnus development mailing list
 help / color / mirror / Atom feed
From: Felix Lee <flee@teleport.com>
Cc: ding@gnus.org
Subject: Re: gnus-asynchronous
Date: Mon, 23 Nov 1998 01:56:49 -0800	[thread overview]
Message-ID: <199811230956.EAA22646@sclp3.sclp.com> (raw)
In-Reply-To: <199811230014.TAA11828@sclp3.sclp.com> on Sun, 22 Nov 1998 16:14:16 PST.

urggg.  I finally reproduce the problem, and after banging
against the wall for a while, I discover it's a bug in emacs
20.3.  after-change-functions aren't run when a process
spews into a buffer.  (unless emacs does encoding stuff,
which is never going to happen in this case.)

this changes everything.  sort of.  maybe.

gnus-async is going to be useless in emacs 20.3
unless.. something.. nasty.. happens...
--


  reply	other threads:[~1998-11-23  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-22 21:25 gnus-asynchronous Istvan Marko
1998-11-22 23:31 ` gnus-asynchronous Felix Lee
1998-11-22 23:45   ` gnus-asynchronous Raja R Harinath
1998-11-23  0:14   ` gnus-asynchronous Felix Lee
1998-11-23  9:56     ` Felix Lee [this message]
2000-06-21  9:47 gnus-asynchronous Simon Josefsson

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=199811230956.EAA22646@sclp3.sclp.com \
    --to=flee@teleport.com \
    --cc=ding@gnus.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).