From: William Perry <wmperry@aventail.com>
Cc: ding@ifi.uio.no
Subject: Re: The Emacs Widget and Custom Libraries, version 0.8
Date: Sun, 15 Sep 1996 21:42:26 -0700 [thread overview]
Message-ID: <199609160442.VAA01212@wmperry.oz.net> (raw)
In-Reply-To: <w8sg24jp7cq.fsf@ylfing.ifi.uio.no>
Lars Magne Ingebrigtsen writes:
>Per Abrahamsen <abraham@dina.kvl.dk> writes:
>
>> I have now released the first version of the rewritten custom
>> library.
>
>Yay!
>
>> It is totally incompatible with the old library, so packages that
>> depends on the old library will (i.e. Gnus) will break horribly.
>
>Uhm... yay?
I hope it is backwards compatible with widget 0.5, or else W3 will break
too. :)
>> See <URL:http://www.dina.kvl.dk/~abraham/custom/> for information
>> about the this release.
>
>Should I just go ahead an include the widget/custom files in the next Red
>Gnus distribution, and start rewriting gnus-cus to support the new
>customize thingies?
BOOM BABY!
-Bill P.
prev parent reply other threads:[~1996-09-16 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-15 21:08 Per Abrahamsen
1996-09-16 1:38 ` Lars Magne Ingebrigtsen
1996-09-16 4:42 ` William Perry [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=199609160442.VAA01212@wmperry.oz.net \
--to=wmperry@aventail.com \
--cc=ding@ifi.uio.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).