From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Hirotaka Honda <hirotaka@hondalaw.com>
Cc: ding@gnus.org
Subject: Re: (wrong-type-argument number-or-marker-p nil) error at gnus startup
Date: Wed, 02 Jun 2021 16:54:43 -0700 [thread overview]
Message-ID: <87v96vq0u4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m2r1hj96hx.fsf@hondalaw.com> (Hirotaka Honda's message of "Thu, 03 Jun 2021 08:44:26 +0900")
Hirotaka Honda <hirotaka@hondalaw.com> writes:
> Dear all
>
> What a cool typo it was. Correct is:
> never happened again.
So much can ride on a word! :)
next prev parent reply other threads:[~2021-06-02 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 7:58 Julien Cubizolles
2021-05-28 2:36 ` Pankaj Jangid
2021-05-28 17:11 ` Eric Abrahamsen
[not found] ` <977D30E3-06DB-46F7-BDC9-933E591A5E78@hondalaw.com>
[not found] ` <87tumhsiw6.fsf@ericabrahamsen.net>
2021-06-02 8:40 ` Hirotaka Honda
2021-06-02 16:09 ` Eric Abrahamsen
2021-06-02 23:44 ` Hirotaka Honda
2021-06-02 23:54 ` Eric Abrahamsen [this message]
2021-06-02 21:31 ` Julien Cubizolles
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=87v96vq0u4.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
--cc=hirotaka@hondalaw.com \
/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).