From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Gnus Users <ding@gnus.org>
Subject: Re: How to setup new nnselect group from init file?
Date: Fri, 06 Nov 2020 10:43:06 +0530 [thread overview]
Message-ID: <m2r1p7m5jx.fsf@codeisgreat.org> (raw)
In-Reply-To: <87361n8c7i.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 05 Nov 2020 18:13:05 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> This isn't going to behave the way you want. There can be only one
> "query" key, and the query itself will look like
> "recipient:pgsql-general@lists.postgresql.org or
> recipient:pgsql-announce@lists.postgresql.org or
> recipient:pgsql-novice@lists.postgresql.org..."
>
>
> You'll probably want quotes around that value "from:\"Cron? Daemon\"".
Thanks worked.
> I don't believe there's any way to create and subscribe to a group
> from your init files. You can certainly set parameters as above, but
> you'll need to create the groups from the Group buffer before the
> parameters take effect. That would also prevent the above incorrect
> search queries, since the group creation would be prompting you
> directly.
Ok. But I went into trouble. That I think needs to be fixed.
I made the above settings in the .gnus.el and probably these got saved
into my .newsrc.eld and probably did few more experiments that I don't
remember exactly what. I did it to make it work from the init file. And
Gnus wasn't starting then. Group buffer wasn't coming up. I had to
manually delete nnselect sexps to bring it back.
But after creating groups from group buffer I am loving it. Really
changed the whole experience.
prev parent reply other threads:[~2020-11-06 5:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 10:27 Pankaj Jangid
2020-11-06 2:13 ` Eric Abrahamsen
2020-11-06 5:13 ` Pankaj Jangid [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=m2r1p7m5jx.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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).