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: Fri, 18 Jan 2019 10:04:52 -0800	[thread overview]
Message-ID: <87sgxpzvsr.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <xuu65zumjoon.fsf@ucl.ac.uk>

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

> On Friday, 11 Jan 2019 at 12:38, Eric Abrahamsen wrote:
>> Thanks, that was helpful! When you have a moment, please try this
>> updated version.
>
> Sorry for previous posting. My C-c key repeated itself and sent the post
> before I was done.
>
> In any case, trying your new version still doesn't work. It now fails
> explicitly in an ivy related function.  See attached backtrace.

Thanks for this! The built-in completion functions silently pass over
non-string completion choices; looks like ivy doesn't (though it seems
like it ought to). I'll filter those out in advance, but would also like
to know what was producing that particular gnus-data. What message were
you on when you got that error? I.e., the offending data was:

((#<marker at 285 in *Article
nntp+news.gwene.org:gmane.emacs.gnus.general*> . #<marker at 778 in
*Article nntp+news.gwene.org:gmane.emacs.gnus.general*>) #<marker at 281
in *Article nntp+news.gwene.org:gmane.emacs.gnus.general*>)

Can you tell me what's at those markers?

Thanks!
Eric




  reply	other threads:[~2019-01-18 18:04 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 [this message]
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
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=87sgxpzvsr.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).