Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Command for browsing article URLs?
Date: Thu, 31 Jan 2019 09:18:12 -0800	[thread overview]
Message-ID: <87sgx8hhkb.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <xuu6imy5mdb1.fsf@ucl.ac.uk>

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Wednesday, 30 Jan 2019 at 11:23, Eric Abrahamsen wrote:
>> Not at all, thanks for testing. I'll probably add this as it is, then,
>> and fix further bugs as they arise. 
>
> I modified your code. If the target is an http link, I explicitly ask to
> browse the url instead of activating the widget. I found that doing the
> latter would simply create a new buffer and not display it (I use eww
> for browsing the web).  I probably should have used funcall but I'm not
> sure when one would or would not use such... I have much to learn about
> elisp.
>
> Alternatively, it may be that the final bit of your code could be
> adjusted as it may be that we should check for article as well as
> summary buffers?  Sometimes, I will invoke the url browsing when viewing
> just the article buffer, especially on a small device.

Oh, I hadn't tested it with eww, I should have. If you just click on the
http url in the article buffer with your mouse (ie, don't use this
function at all), what behavior do you get? I think you're right that
the best approach is to modify how the windows are manipulated
afterwards (or just drop that bit of the code altogether). I'd like this
to behave exactly as if you'd clicked the mouse, and would rather not
put special-casing in there.

Thanks again,
Eric




  reply	other threads:[~2019-01-31 17:18 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 [this message]
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
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=87sgx8hhkb.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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).