From: Colin Marquardt <colin.marquardt@usa.alcatel.com>
Cc: ding@gnus.org
Subject: Re: Old bug reapqpearing in 5.8.8
Date: 16 Jan 2001 19:07:57 -0800 [thread overview]
Message-ID: <ysd6ely227w2.fsf_-_@sol-cmarquar.pet.usa.alcatel.com> (raw)
In-Reply-To: <2nofx7ylob.fsf@tiger.jia.vnet>
Hi,
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> Colin Marquardt <colin.marquardt@usa.alcatel.com> writes:
>
> > The file with the most errors:
> >
> > | While compiling rfc2047-encode-message-header in file /home/sw/cmarquar/emacs/gnus-CURRENT-20010116/lisp/rfc2047.el:
> > | ** reference to free variable enable-multibyte-characters
> > | While compiling rfc2047-encode:
> > | ** reference to free variable enable-multibyte-characters
>
> Are you sure you compile them from a clean copy?
Pretty sure, yes. I just unpacked it today. I am running configure
with the options
--with-xemacs --prefix=/home/sw/cmarquar/emacs/gnus-CURRENT-20010116
where --prefix is the same directory where I unpacked it (I do not
have write access to the system directory). Is this dangerous in any
way?
I probably should also mention that this is a non-Mule XEmacs, 21.1.9.
> > | While compiling rfc2047-b-encode-region:
> > | ** base64-encode-region called with 3 arguments, but accepts only 2
>
> For XEmacs 21.1, you'd better copy base64.el from contrib directory to
> lisp directory, the do the compilation.
That fixed it, thanks.
> > I don't have makeinfo installed on this Solaris box, so it is
> > running:
>
> [...]
>
> Perhaps, you need to update XEmacs elisp packages.
Might be, I do not have the latest XEmacs. It's not really a problem
now, the texi file is fine.
> > It puts an "X-Draft-From:" header to my reply, but on top of all the
> > headers, before the "To:" even. Could this be moved a bit further
> > down?
>
> For any particular reason?
For the only reason that I mentally connect importance with order,
and so an X-Header gets more importance than it needs.
User interface only, but for the same reason that we have
message-header-to-face and message-header-subject-face stand out
optically.
Cheers,
Colin
prev parent reply other threads:[~2001-01-17 3:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 12:37 Suddenly can't subscribe to nnslashdot groups with 'F' ? Anssi Saari
2001-01-12 22:42 ` ShengHuo ZHU
2001-01-15 11:37 ` Anssi Saari
2001-01-16 19:46 ` Old bug reappearing in 5.8.8 Colin Marquardt
2001-01-16 20:17 ` ShengHuo ZHU
2001-01-16 21:12 ` Colin Marquardt
2001-01-17 2:09 ` ShengHuo ZHU
2001-01-17 3:07 ` Colin Marquardt [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=ysd6ely227w2.fsf_-_@sol-cmarquar.pet.usa.alcatel.com \
--to=colin.marquardt@usa.alcatel.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).