Gnus development mailing list
 help / color / mirror / Atom feed
From: "Clemens Schüller" <cs.mlists+gnus@mailbox.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Command for browsing article URLs?
Date: Tue, 22 Jan 2019 21:50:20 +0100	[thread overview]
Message-ID: <m2zhrsju2b.fsf@warhorse.home.aneadesign.com> (raw)
In-Reply-To: <878szwwdjw.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 07 Jan 2019 10:03:15 -0800")

Hello!

Eric Abrahamsen wrote:

> I'd like to have a command, call it `gnus-article-browse-url', which
> collects all the links/URLs in the article body, and then offers to
> browse one of them (choosing with completion). Bound to "K l",
> naturally.
>
> Does anyone have anything like this already-written? I made a custom
> function to open links from my Hacker News gwene group, but realized it
> would be better to have something generalized.
>
> If no one has this written already, I can make one.

You remind me in this second on an error in my gnus config:

I have following in my .gnus


#+begin_src emacs-lisp
(setq browse-url-browser-function 'browse-url-generic
;;    browse-url-generic-program "/usr/bin/konqueror"
;;    browse-url-generic-program "/usr/bin/chromium"
      browse-url-generic-program "/Applications/Safari.app/Contents/MacOS/Safari"
          browse-url-new-window-p t)
#+end_src

But, if I wanna open an URL, the URL is malformed and I got an error,
that the website could not be opened.



--8<---------------cut here---------------start------------->8---
file:///Users/mente/Library/Containers/com.apple.Safari/Data/http:/localhost:631
^^
stands in the URL line in Safari



http:/localhost:631
^^
is the original one.
--8<---------------cut here---------------end--------------->8---


How can I fix that?
-- 
Best Regards, Clemens Schüller



  parent reply	other threads:[~2019-01-22 20:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 18:03 Eric Abrahamsen
2019-01-07 20:15 ` Eric S Fraga
2019-01-07 21:53   ` Eric Abrahamsen
2019-01-08 17:07 ` Haider Rizvi
2019-01-08 20:53   ` Eric Abrahamsen
2019-01-10 18:47     ` Haider Rizvi
2019-01-10 22:27       ` Eric Abrahamsen
2019-01-10 17:53   ` Eric Abrahamsen
2019-01-10 22:46     ` Eric Abrahamsen
2019-01-11 10:17     ` Eric S Fraga
2019-01-11 20:38       ` Eric Abrahamsen
2019-01-18  9:24         ` Eric S Fraga
2019-01-18  9:32         ` Eric S Fraga
2019-01-18 18:04           ` Eric Abrahamsen
2019-01-19 11:08             ` Eric S Fraga
2019-01-21 18:03               ` Eric Abrahamsen
2019-01-22 23:45                 ` Eric Abrahamsen
2019-01-30  8:13                   ` Eric S Fraga
2019-01-30 19:23                     ` Eric Abrahamsen
2019-01-31  8:38                       ` Eric S Fraga
2019-01-31 17:18                         ` Eric Abrahamsen
2019-01-31 17:25                           ` Eric S Fraga
2019-01-31 17:49                             ` Eric Abrahamsen
2019-01-31 18:31                               ` Eric S Fraga
2019-06-22 10:30         ` Lars Ingebrigtsen
2019-01-22 20:50 ` Clemens Schüller [this message]
2019-01-22 20:59   ` Eric Abrahamsen
2019-02-10  8:55     ` Clemens Schüller

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=m2zhrsju2b.fsf@warhorse.home.aneadesign.com \
    --to=cs.mlists+gnus@mailbox.org \
    --cc=cs.mlists@mailbox.org \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    /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).