From: Richmond <dnomhcir@gmx.com>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: info-gnus-english@gnu.org
Subject: Re: Error message Process nntpd not running
Date: Tue, 20 Jul 2021 18:35:16 +0100 [thread overview]
Message-ID: <7zv954opm3.fsf@example.com> (raw)
In-Reply-To: <m2r1fthz6q.fsf@codeisgreat.org> (Pankaj Jangid's message of "Tue, 20 Jul 2021 19:20:21 +0530")
Pankaj Jangid <pankaj@codeisgreat.org> writes:
> Richmond <dnomhcir@gmx.com> writes:
>
>> I tried creating a new linux user, and copied the files .gnus and
>> .gnu-emacs-custom and then ran emacs -nw -f gnus, but still got the
>> same error.
>
> Is this emacs-27? I can see that that could be the only difference. I am
> using Emacs from the git master (i.e. 28.x).
>
> If you have access to emacs from git master then could you please try
> reproducing it?
I was using 26.
I have now tried 27.2, and 28.0.50 (and 25) and all produce the same
error.
I think it is odd that I get the error if I start gnus from the command
line, with emacs -nw -f gnus, but if I start emacs first, emacs -nw,
then start gnus from within emacs. I get no error.
So perhaps I just need to delay the start of gnus a little?
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2021-07-20 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 10:16 Richmond
2021-07-20 10:57 ` Pankaj Jangid
2021-07-20 11:15 ` Richmond
2021-07-20 11:26 ` Pankaj Jangid
2021-07-20 11:31 ` Richmond
2021-07-20 12:24 ` Pankaj Jangid
2021-07-20 12:44 ` Richmond
2021-07-20 13:50 ` Pankaj Jangid
2021-07-20 17:35 ` Richmond [this message]
2021-07-20 17:55 ` Richmond
2021-07-20 19:12 ` Eric Abrahamsen
2021-07-21 3:19 ` Pankaj Jangid
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=7zv954opm3.fsf@example.com \
--to=dnomhcir@gmx.com \
--cc=info-gnus-english@gnu.org \
--cc=pankaj@codeisgreat.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).