From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: [patch] Display what's really being executed
Date: Sun, 29 Dec 2002 23:45:00 +0100 [thread overview]
Message-ID: <m3u1gwv40j.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <sxslm7ay5c3.fsf@florida.munich.redhat.com>
Hrvoje Niksic <hniksic@xemacs.org> writes:
> BTW isn't mm-* supposed to be independent from Gnus? What's the call
> to gnus-configure-windows doing in the guts of mm-display-external?
It's supposed to be independent, but these things have a tendency to
creep in... The window config stuff should probably be passed from
Gnus in a hook function or the like, to make it unnecessary for mm to
know anything about Gnus internal.
> The patch follows.
Applied.
> I will apply the patch unless someone objects.
Oops. It didn't look like it had been applied, so perhaps you
changed your mind? Should I reverse the patch?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2002-12-29 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 18:35 Hrvoje Niksic
2002-12-29 22:45 ` Lars Magne Ingebrigtsen [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=m3u1gwv40j.fsf@quimbies.gnus.org \
--to=larsi@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).