Gnus development mailing list
 help / color / mirror / Atom feed
From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: URL buttons and new browser windows...
Date: 17 Nov 1999 11:51:01 +0000	[thread overview]
Message-ID: <uemdpfiai.fsf@lanber.cam.citrix.com> (raw)
In-Reply-To: wmperry@aventail.com's message of "16 Nov 1999 19:32:25 -0500"

Bill> William M. Perry <URL:mailto:wmperry@aventail.com>

0> In article <86g0y6yn3a.fsf@megalith.bp.aventail.com>, Bill wrote:

Bill> I'd vote for Gnus to just use browse-url... why on earth is it
Bill> trying to call the browse-url-browser-function directly?  That
Bill> seems kind of... uh, silly?

Especially since it doesn't check for (listp browse-url-browser-function).

#> browse-url-browser-function's value is
#> (("\\.\\(gif\\jpe?g\\)" . browse-url-netscape)
#>  ("." . browse-url-w3))
#>
#>
#> Documentation:
#> *Function to display the current buffer in a WWW browser.
#> This is used by the `browse-url-at-point', `browse-url-at-mouse', and
#> `browse-url-of-file' commands.
#>
#> If the value is not a function it should be a list of pairs
#> (REGEXP . FUNCTION).  In this case the function called will be the one
#> associated with the first REGEXP which matches the current URL.  The
#> function is passed the URL and any other args of `browse-url'.  The last
#> regexp should probably be "." to specify a default browser.



  parent reply	other threads:[~1999-11-17 11:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-17  0:19 Daniel Pittman
1999-11-17  0:32 ` William M. Perry
1999-11-17  0:43   ` Daniel Pittman
1999-11-17 11:51   ` Toby Speight [this message]
1999-11-17 12:27     ` William M. Perry
1999-11-17 14:03       ` David S. Goldberg
1999-11-17 14:42         ` Jan Vroonhof
1999-12-01 15:47       ` 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=uemdpfiai.fsf@lanber.cam.citrix.com \
    --to=toby.speight@streapadair.freeserve.co.uk \
    /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).