From: Richard G Riley <rileyrgdev@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: gnus and nnrss html
Date: Sun, 08 Jun 2008 19:35:56 +0200 [thread overview]
Message-ID: <g2h59t$so1$1@registered.motzarella.org> (raw)
In-Reply-To: <g2h143$9qn$1@registered.motzarella.org>
Richard G Riley <rileyrgdev@gmail.com> writes:
> Richard G Riley <rileyrgdev@gmail.com> writes:
>
>> I have the following in my .gnus.el
>>
>> ,----
>> | ;; Set the default value of `mm-discouraged-alternatives'.
>> | (add-to-list
>> | 'gnus-newsgroup-variables
>> | '(mm-discouraged-alternatives
>> | . '("text/html" "image/.*")))
>> |
>> | ;;Display `text/html' parts in `nnrss' groups.
>> | (add-to-list
>> | 'gnus-parameters
>> | '("\\`nnrss:" (mm-discouraged-alternatives nil)))
>> `----
>>
>> The problem I have is that any links in the html are displayed as
>> "linkname" with the url hidden. I usually have a key bound to
>> (browse-url-firefox url &optional new-window) but this only works on
>> "visible" urls. How can I extract the underlying url in articles on nrss
>> folders which are being displayed as rendered html?
>
> The following code did what I wanted without upsetting the default
> "return" which uses w3m for me.
>
> (global-set-key (quote [f4]) (lambda()
> (interactive)(browse-url-firefox (w3m-url-valid (w3m-anchor)))))
And a slightly more robust one which prompts for a URL if there are w3m
ones under the cursor:
,----
| (global-set-key
| (quote [f4])
| (lambda()
| (interactive)
| (cond
| ((setq url (w3m-url-valid (w3m-anchor)))
| (browse-url-firefox url))
| (t (command-execute 'browse-url-firefox)))))
`----
prev parent reply other threads:[~2008-06-08 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 22:32 Richard G Riley
2008-06-08 16:24 ` Richard G Riley
2008-06-08 17:35 ` Richard G Riley [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='g2h59t$so1$1@registered.motzarella.org' \
--to=rileyrgdev@gmail.com \
--cc=info-gnus-english@gnu.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).