From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: 19.34 --> 20.4, 5.6.43 --> 0.80
Date: 06 Mar 1999 08:46:47 -0500 [thread overview]
Message-ID: <oq7lsu688o.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Alan Shutko's message of "05 Mar 1999 23:30:40 -0600"
> D> Do I have to set a language environment? Should I run emacs with
> D> --unibyte or not?
Lars told a few times Gnus works better when --unibyte is not used.
I tried both, and both were workable for me. Yet, in --unibyte, I was
unable to see much of those sexy characters, beyond French ones :-).
> D> I mostly use English and don't understand much about Mule. I did
> D> install the intlfonts package. What's a good font(set) to use
> D> for emacs?
I define these in .bash_login:
export EMACS19FONT='-adobe-courier-medium-r-normal--*-140-*-*-m-*-iso8859-1'
export EMACS20FONT='-*-fixed-medium-r-normal-*-16-*-*-*-*-*-fontset-standard'
export XEMACSFONT='-*-fixed-medium-r-normal-*-16-*-*-*-*-*-fontset-standard'
and use this code in .emacs:
(setq EMACS19 (string-match "\\<Emacs 19" (emacs-version))
EMACS20 (string-match "\\<Emacs 20" (emacs-version))
XEMACS (string-match "XEmacs\\|Lucid" (emacs-version)))
;[...]
(cond (XEMACS (set-face-font 'default (getenv "XEMACSFONT")))
(EMACS20 (set-default-font (getenv "EMACS20FONT")))
(EMACS19 (set-default-font (getenv "EMACS19FONT"))))
If you have a longish `.emacs' file (which is my case), I suggest you
execute the above code early, because it might change the dimensions of
your Emacs frame. You can then reposition the frame with the mouse while
the initialization proceeds.
> D> 1) I run ispell from my message-send-hook, and it gave an error
> D> message:
> D> Ispell misalignment: word `JSa' point 266; probably incompatible
> D> versions
I got the same, at a time I was not using --unibyte. I reported the
problem to appropriate people, and had no indication that the problem
was ever clearly identified. My intuition was that it is a Mule related
problem, but this was not confirmed. Recently, with a recent Emacs pretest,
I removed the --unibyte, and these `ispell' problems did not come back.
However, the conditions of my testing are different, as I now use the nice
Manuel Serrano's `flyspell' package (included in the pretest).
> D> locate-library shows that this is the ispell.el that comes with
> D> 20.4. Our ispell binary is 3.1.20 which I installed just 7 months
> D> ago. I guess this is unlikely to be a Gnus problem.
I'm not sure `ispell.el' fully knows how to do arithmetic in buffers with
all those internal-supposedly-invisible `\201' added in them.
> D> 2) I set message-send-hook to nil and tried again. After `C-c C-c'
> D> I got an error: "Can't encode a part with several charsets." Isn't
> D> Gnus supposed to break the message into parts automatically?
Yes, it should. But recently, Gnus gave me this unexpected message as well.
I reported the matter to Lars.
--
François Pinard mailto:pinard@iro.umontreal.ca
Join the free Translation Project! http://www.iro.umontreal.ca/~pinard
prev parent reply other threads:[~1999-03-06 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-05 23:37 Dan Christensen
1999-03-06 5:30 ` Alan Shutko
1999-03-06 13:46 ` François Pinard [this message]
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=oq7lsu688o.fsf@titan.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--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).