From: Alan Shutko <ats@acm.org>
Subject: Re: void function make-annotation
Date: 28 Mar 1999 12:23:43 -0600 [thread overview]
Message-ID: <m3zp4xpj68.fsf@hubert.wuh.wustl.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "28 Mar 1999 19:24:40 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> This should only happen if
> [...]
> evaluates to t. Is that the case for you?
Yup... it looks like W3's devices.el defines device-type on Emacs.
--
Alan Shutko <ats@acm.org> - By consent of the corrupted
Skydivers are good till the last drop.
next prev parent reply other threads:[~1999-03-28 18:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-26 21:55 Alan Shutko
1999-03-28 17:24 ` Lars Magne Ingebrigtsen
1999-03-28 18:23 ` Alan Shutko [this message]
1999-04-02 13:43 ` Lars Magne Ingebrigtsen
1999-04-02 18:08 ` Kim-Minh Kaplan
1999-04-05 20:27 ` Colin Rafferty
1999-04-13 7:00 ` Hrvoje Niksic
1999-04-13 13:58 ` Colin Rafferty
1999-04-13 15:01 ` Hrvoje Niksic
1999-04-13 15:11 ` Colin Rafferty
1999-04-13 15:12 ` Kai.Grossjohann
1999-04-13 15:20 ` Hrvoje Niksic
1999-04-17 6:06 ` Lars Magne Ingebrigtsen
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=m3zp4xpj68.fsf@hubert.wuh.wustl.edu \
--to=ats@acm.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).