Gnus development mailing list
 help / color / mirror / Atom feed
From: Ketil Z Malde <ketil@ii.uib.no>
Subject: Fixed! (was: mail-abbrev?)
Date: 22 May 1996 17:18:40 +0200	[thread overview]
Message-ID: <KETIL-egafz0zqgf.fsf@due.ii.uib.no> (raw)
In-Reply-To: Ketil Z Malde's message of Wed, 22 May 1996 15:45:57 +0200


I wrote:

> Switching to sgnus-0.90, I get the message that mail-abbrev could not
> be loaded.  Compiling gave me the same kind of messages about it not
> existing.  What gives?

I found out.  Or, at least, I made the problem go away by renaming the
require for 'mail-abbrev with a require for 'mail-abbrevs.  That's
abbrevS, with an S at the end.

Possibly a new name from Xemacs-19.14 (I use a beta version -- but so
does a lot of other people on the list, don't they?  Steve?)

However, now I feel that getting new articles take an insurmountably
long time - is it just my NFS/NNTP connection not being up to par, or is
there in fact a slowdown from 0.76?  Is there anything I can do in the
way of profiling or something to measure where the sluggishness stems
from?

Ah, one more thing - when citing an article that already contain cited
text, I often get something like this (the prepended tab not included):

	> >blah blah

	> gobble gobble

..but C-c C-q mangles the first one, due to, I think the spaces used.
Perhaps message-fill-yanked-message could be made more intelligent --
maybe using some heuristics used in the highlighting code?  Or is there
something I can do about it?

~kzm


  parent reply	other threads:[~1996-05-22 15:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-22 13:45 mail-abbrev? Ketil Z Malde
1996-05-22 14:53 ` mail-abbrev? Jack Vinson
1996-05-22 15:22   ` mail-abbrev? Paul D. Smith
1996-05-22 16:40     ` mail-abbrev? Mark Borges
1996-05-22 17:49       ` mail-abbrev? Per Abrahamsen
1996-05-22 15:18 ` Ketil Z Malde [this message]
1996-05-22 18:51   ` Fixed! (was: mail-abbrev?) Lars Magne Ingebrigtsen
1996-05-22 19:42   ` Steven L Baur

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=KETIL-egafz0zqgf.fsf@due.ii.uib.no \
    --to=ketil@ii.uib.no \
    /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).