Gnus development mailing list
 help / color / mirror / Atom feed
From: e20100633 <e20100633@inbox.lv>
To: gmane-discuss@hawk.netfonds.no
Cc: ding@gnus.org
Subject: Re: Podcasts in gwene ?
Date: Tue, 19 Oct 2010 22:57:43 +0200	[thread overview]
Message-ID: <871v7l529k.fsf@EVA01.wopr.org> (raw)
In-Reply-To: <m3sk02dsrh.fsf@quimbies.gnus.org>

Hello Lars,

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> e20100633 <e20100633@inbox.lv> writes:
>
>> So in this way we can say that gwene isn't actually fully supporting the
>> /podcasts feeds/. I understand that the big difference between RSS blog
>> feeds and podcasts feeds is that podcasts feed have an <enclosure url />
>> which content the URL of the media.
>
> Do you have an example group that displays this behaviour?

I'm not sure I have correctly understood your question, but I give it a
try :

Do you mean a group added by me where articles show the description but
not the content media attached to it ?

Yes, I've added 4/5 podcasts feeds, I give you an example :

gwene.fr.franceculture.lundi-histoire
(http://radiofrance-podcast.net/podcast09/rss_10193.xml)

When I subscribe to this group, I see an article named "La prostitution
au Moyen Age". The body of this article is the content of the
<description> found in the feed. Ok no news here.

When we :

--8<---------------cut here---------------start------------->8---
$ wget -q -O - http://radiofrance-podcast.net/podcast09/rss_10193.xml | \
       grep enclosure
--8<---------------cut here---------------end--------------->8---

we have a result like that :

<enclosure url="http://rf.proxycast.org/m/(...)audio/mpeg"  />

(I've cutted it, the URL is very long). So the media, the mp3, related
to this article can be found at this URL.

So the idea here is to see _in_ the body, the <description> like it is
now in gwene but too, at the bottom of the body for example, a link to
the URL pointed by <enclosure url=.

Other groups like that (added by me) are :
 - gwene.fr.franceculture.*
 - gwene.com.radio666.podcast.trafalgar

I hope I've answered to your question.

>> PS: In my fantasy I am dreaming that gnus see those media as an
>> attachment and so we'll be able to download the content with 'K o' (in
>> gnus) -- like I already download my attachment with gnus+imap. But maybe
>> that is too much.
>
> Well, shr could have a download command to just start url.el in the
> background and save the thing under point to a file?

I don't know what shr is, I made some research without any success. But
for the rest, yes I was thinking of this kind of behavior, like
emacs-wget does from emacs-w3m for example (or actually like does the
download feature of emacs-w3m which permit you to continue your surf
while your download is processing...).

Thank you for your time.

Regards,

-- 
e20100633@inbox.lv

  reply	other threads:[~2010-10-19 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wrpe4abk.fsf@EVA01.wopr.org>
2010-10-19 16:58 ` Lars Magne Ingebrigtsen
2010-10-19 20:57   ` e20100633 [this message]
2010-10-19 21:25     ` Lars Magne Ingebrigtsen
2010-10-19 21:44       ` e20100633

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=871v7l529k.fsf@EVA01.wopr.org \
    --to=e20100633@inbox.lv \
    --cc=ding@gnus.org \
    --cc=gmane-discuss@hawk.netfonds.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).