From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Emacs/W3 4.0pre31 updloaded...
Date: 03 Dec 1998 06:49:59 -0500 [thread overview]
Message-ID: <86vhjt30ns.fsf@kramer.bp.aventail.com> (raw)
Mostly changes to deal with Gnus content-id handling, but it will also now
work with the new Emacs redisplay, so you can now see very pretty large
fonts under an appropriately patches Emacs 20.3
One thing you might want to change in your stylesheets though is the use of
multifont or unifont instead of xemacs or emacs in any media chunks. The
old default.css used '@media xemacs { ... }' for specifying all font
information. Now that Emacs can do it as well, this is wrong. :)
multifont is the appropriate way.
-Bill P.
1998-12-03 William M. Perry <wmperry@aventail.com>
* Emacs/W3 4.0pre31 released
* configure.in (CIDFILE): Stop spitting out a warning about
multipart/related stuff if we can't find Gnus at configure time. We're
hacking around it in a different way now.
* lisp/Makefile.in (URLSOURCES): Add url-cid.el into the definition via
configure substitutions ONLY. It will still get installed because we
stick it in EXTRAS. This means 1 extra file copy at install time, but
who cares? The file isn't that large.
* lisp/url-cid.el: New file to contain the content-id handling stuff,
because we cannot compile this file unless we can find a very recent
version of Gnus at compile time (without .emacs).
* etc/default.css: Use the newer @media tags instead of @x*emacs so that
everything will work right with the new Emacs redisplay.
* lisp/css.el (css-active-device-types): Added new @media tags.
multifont is now defined if the Emacsen we are running in can display
multiple font families and sizes correctly (new emacs redisplay or
XEmacs), and unifont if it cannot.
* lisp/font.el (font-set-face-font-new-redisplay): New function for
dealing with the new Emacs redisplay font abstraction. You can now beat
the crap out of the new redisplay engine with Emacs/W3. Ahh, feels like
the heady old days of Lucid Emacs 19.10 and XEmacs 19.12.
1998-12-02 Simon Josefsson <jas@pdc.kth.se>
* lisp/mm.el (mm-parse-mailcaps): Deal gracefully with bad entries in the
MAILCAP list, or it would bug out with things like 'file:' where it
would try to open the current directory.
1998-11-29 William M. Perry <wmperry@aventail.com>
* lisp/docomp.el (load-path): Append the GNUSDIR environment variable to
the load-path, similar to how we deal with WIDGETDIR
* INSTALL: Document the new --with-gnus arguments.
* configure.in: Use AC_CHECK_GNUS and spit out appropriate warnings about
cid URLS not working when appropriate.
* aclocal.m4 (AC_CHECK_GNUS): Try to find mm-get-content-id in mm-decode
for newer gnus releases that can handle the content-id stuff. Also
added new configure switch '--with-gnus=/path/to/gnus/lisp/dir' to
override this, similar to how the custom stuff works.
* lisp/url-misc.el (url-cid-gnus): Try to load mm-decode at compile time.
(url-cid-gnus): Fixed some compilation warnings.
* lisp/url.el (url-cid): Ooops - forgot to add an autoload for url-cid
next reply other threads:[~1998-12-03 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-03 11:49 William M. Perry [this message]
1998-12-04 1:44 ` Lloyd Zusman
1998-12-04 5:40 ` Norbert Koch
1998-12-04 14:33 ` William M. Perry
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=86vhjt30ns.fsf@kramer.bp.aventail.com \
--to=wmperry@aventail.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).