Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Slow decoding
Date: 01 Dec 1998 15:59:55 +0100	[thread overview]
Message-ID: <kiglnkrnc0k.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lee Willis's message of "01 Dec 1998 12:12:26 +0000"

Lee Willis <lee@gbdirect.co.uk> writes:

> Markus Dickebohm <m.dickebohm@uni-koeln.de> writes:
> 
> > This went quite smooth with TM, but now with pgnus (though I really
> > like all the new features and the look-and-feel) it takes extremely
> > long to decode a say 2MB attachment. Here on my little DEC Alpha
> > Workstation Emacs freezes for approximately 5 minutes, then asks for a
> > filename and freezes again for 5-10 minutes.
> 
> Hmm, well at the moment all base-64 en/decoding is done in Emacs Lisp
> which isn't exactly the nippiest language in the world. Apparently in
> future versions of (x?)emacs there will be base-64 encoding/decoding
                      ^^
> which will be in C so should be less lethargic ...

Yes.  The latest XEmacs 21.2 also supports native base64 en/decoding.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
* Q: What is an experienced Emacs user?
* A: A person who wishes that the terminal had pedals.


  reply	other threads:[~1998-12-01 14:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-01 11:54 Markus Dickebohm
1998-12-01 12:05 ` Kai.Grossjohann
1998-12-01 12:20   ` Markus Dickebohm
1998-12-01 14:56     ` Jake Colman
1998-12-01 16:58       ` Kai.Grossjohann
1998-12-01 20:49         ` François Pinard
     [not found]   ` <6f7lwcrqmb.fsf@dna.lth.se>
1998-12-01 12:34     ` Kai.Grossjohann
1998-12-01 12:12 ` Lee Willis
1998-12-01 14:59   ` Hrvoje Niksic [this message]
     [not found] ` <6fbtlorrg3.fsf@dna.lth.se>
1998-12-01 23:01   ` Lars Magne Ingebrigtsen
     [not found]     ` <6f3e6yzz2s.fsf@dna.lth.se>
1998-12-02 17:13       ` Lars Magne Ingebrigtsen

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=kiglnkrnc0k.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).