From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: Command for browsing article URLs?
Date: Sat, 19 Jan 2019 11:08:52 +0000 [thread overview]
Message-ID: <87r2d8c3az.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87sgxpzvsr.fsf@ericabrahamsen.net>
On Friday, 18 Jan 2019 at 10:04, Eric Abrahamsen wrote:
> 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:
These were the active places (i.e. where I can TAB to and do something
on) in an email that includes previous messages, things highlighted by
gnus especially when using the mechanisms in gnus for hiding part of a
citation. The particular message was the previous one you had posted to
this group (mailing list but I'm reading it via gwene/gmane).
HTH,
eric
--
Eric S Fraga via Emacs 27.0.50 & org 9.1.14 on Debian buster/sid
next prev parent reply other threads:[~2019-01-19 11:08 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 [this message]
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=87r2d8c3az.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).