From: Dan Christensen <jdc@chow.mat.jhu.edu>
Subject: 19.34 --> 20.4, 5.6.43 --> 0.80
Date: Fri, 05 Mar 1999 18:37:31 -0500 [thread overview]
Message-ID: <x7iucfzex0.fsf@chow.mat.jhu.edu> (raw)
I've just upgraded my emacs from 19.34 to 20.4, and my Gnus
from 5.6.43 to pgnus 0.80.
Besides the new mail source stuff, is there anything I should be
updating in my init files? Do I have to turn Mime on? (I didn't use
any MIME packages like tm in the past.) Do I have to set a language
environment? Should I run emacs with --unibyte or not? I mostly use
English and don't understand much about Mule. I did install the
intlfonts package. What's a good font(set) to use for emacs?
Here are the oddities I've noticed so far:
1) I run ispell from my message-send-hook, and it gave an error
message:
Ispell misalignment: word `JSa' point 266; probably incompatible versions
locate-library shows that this is the ispell.el that comes with 20.4.
Our ispell binary is 3.1.20 which I installed just 7 months ago. I
guess this is unlikely to be a Gnus problem.
2) I set message-send-hook to nil and tried again. After `C-c C-c' I
got an error: "Can't encode a part with several charsets." Isn't Gnus
supposed to break the message into parts automatically?
[And is there an easier way to send a message without invoking
message-send-hook?]
3) When I start gnus, all my groups on levels 4 and 5 show up in the
group buffer. These are my nnfolder groups which new mail never gets
split to. gnus-activate-level is 3. If I `M-g' on one of these, and
then hit `l', the group disappears (as it should). Similarly, `5 g'
makes them go away, but this takes a long time because there are lots
of them. (This is why I have gnus-activate-level set to 3) This
didn't happen with 19.34 and 5.6.43.
Thanks for any help,
Dan
--
Dan Christensen
jdc@math.jhu.edu
next reply other threads:[~1999-03-05 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-05 23:37 Dan Christensen [this message]
1999-03-06 5:30 ` Alan Shutko
1999-03-06 13:46 ` François Pinard
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=x7iucfzex0.fsf@chow.mat.jhu.edu \
--to=jdc@chow.mat.jhu.edu \
/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).