Gnus development mailing list
 help / color / mirror / Atom feed
From: Hynek Schlawack <hynek@ularx.de>
Subject: Re: Viewing HTML-mails with external browsers - proposed code
Date: Fri, 13 Jan 2006 18:13:52 +0100	[thread overview]
Message-ID: <87k6d459v3@ularx.de> (raw)
In-Reply-To: <v9psmwp1de.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 13 Jan 2006 16:57:01 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> wrote:

>> Just being curious: Is it the code-quality 
> No, I didn't read the code yet. ;-)

I nearly guessed so. ;)

>> or the purpose of the code 
> Personally, I'm quite happy with the text part.  If this fails or is
> not present, emacs-w3m is sufficient for me.

This was my position for a pretty long time too. But there are
exceptions and I though, it might open Gnus even a bit more to a broader
audience.

>> Anyway: As I started to get more and more Mails (mostly newsletters
>> etc) that make sense only if readen with an graphical browser like
>> Firefox, I was wondering whether there's some easy way to display
>> them in Gnus? As I haven't found anything, I wrote a little elisp to
>> solve this.
> My first though was: We probably already have something similar in
> Gnus.  But I couldn't find it.

Well, I searched pretty hard too. Good to know, that if there is code,
it isn't obvious.

>> It's kindof my first lisp ever, so please be tolerant. ;)
> There are some minor issues.

I'd be glad to hear them.

>> I'd be happy about some feedback or even inclusion though.
> If we don't have such a feature already, I think it would be good to
> install your code.

Nice to hear.

[ Legal ]
> AFAICS, you haven't filed a copyright assignment for work on Gnus or
> Emacs to the Free Software Foundation yet.  If you're willing to
> assign your code, I can send you the required request form.  After the
> assignment process completes (you get sent forms which you have to
> read and sign and send back), we can install your code.

I'd be happy to sign it for Emacs do that so go on and send them. Is it
a file I can print out or do you need my postal address?

Meanwhile, could we start making the code "technically" installable
(ie. resolve issues)?

Cheers,
-hs



  reply	other threads:[~2006-01-13 17:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-18 21:49 Hynek Schlawack
2006-01-13 13:42 ` Hynek Schlawack
2006-01-13 15:57   ` Reiner Steib
2006-01-13 17:13     ` Hynek Schlawack [this message]
2006-01-19 19:35 ` Reiner Steib
2006-01-22 12:40   ` Hynek Schlawack
2006-01-25 14:44     ` Reiner Steib
2006-01-25 16:29       ` Hynek Schlawack
2006-01-25 17:41         ` Reiner Steib
2006-01-31 12:38           ` Hynek Schlawack
2006-02-10 18:15             ` Reiner Steib
2006-02-13  0:06               ` Katsumi Yamaoka
2006-02-13 14:53                 ` Reiner Steib
2006-02-13 15:24                   ` Hynek Schlawack
2006-02-13 15:37                   ` Hynek Schlawack
2006-02-13 22:16                     ` Reiner Steib
2006-02-14  0:11                       ` Katsumi Yamaoka
2006-02-14 11:50                         ` Katsumi Yamaoka
2006-02-15  8:39                           ` mm-make-temp-file (was Re: Viewing HTML-mails with external browsers - proposed code) Katsumi Yamaoka
2006-02-14 20:08                         ` Viewing HTML-mails with external browsers - proposed code Hynek Schlawack

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=87k6d459v3@ularx.de \
    --to=hynek@ularx.de \
    /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).