From: Garjola Dindi <garjola@garjola.net>
To: info-gnus-english@gnu.org
Subject: Re: Maybe a bug after df89d6d6dc429e638e425536d1c201b5373f2abd
Date: Sat, 28 Dec 2019 08:42:18 +0100 [thread overview]
Message-ID: <877e2gvqud.fsf@pc-117-162.ovh.com> (raw)
In-Reply-To: <871rspdyqf.fsf@gnus.org>
On Sat 28-Dec-2019 at 02:29:12 +01, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Adam Sjøgren via info-gnus-english <info-gnus-english@gnu.org> writes:
>
>> Is this a fix for:
>
> [...]
>
>> * lisp/gnus/gnus-start.el: Use lexical-binding
>
> Yup.
Thank you for the quick answer and fix!
I lost my .newrc.eld, but this is my fault for forgetting to add it to
my backup script.
--
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2019-12-28 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 0:11 Garjola Dindi
2019-12-28 0:26 ` Adam Sjøgren via info-gnus-english
2019-12-28 0:50 ` Lars Ingebrigtsen
2019-12-28 1:17 ` Adam Sjøgren via info-gnus-english
2019-12-28 1:19 ` Adam Sjøgren via info-gnus-english
2019-12-28 1:29 ` Lars Ingebrigtsen
2019-12-28 7:42 ` Garjola Dindi [this message]
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=877e2gvqud.fsf@pc-117-162.ovh.com \
--to=garjola@garjola.net \
--cc=info-gnus-english@gnu.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).