From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: Re: Configuration weirdness
Date: Thu, 14 Jan 2016 07:52:45 -0800 [thread overview]
Message-ID: <877fjcrwdu.fsf@nwalsh.com> (raw)
In-Reply-To: <87r3hniw7r.fsf@nwalsh.com> (Norman Walsh's message of "Mon, 11 Jan 2016 14:32:08 -0800")
[-- Attachment #1: Type: text/plain, Size: 2925 bytes --]
Hello again,
Contrary to what I reported about hacking .newsrc.eld to fix this,
further attempts to do so have failed. Depending on how I hack things,
I get variously errors about missing directories, or groups with no
mail, etc.
I even tried moving my ~/Mail directory out of the way and “restarting”
to see if I could get an example of what a clean setup would look like.
That wasn't fruitful.
I also tried making some other method (nndiary) my primary select
method so that the nnml: prefix would be expected. Also not fruitful.
I've now got a whole bunch of useless
*, 0: nnml:group-name
groups *and*
2, 234: group-name
groups. Which is kind of annoying.
I'm happy to have nnml: if that's what makes nnir happy. And I would like
to get nnir working with notmuch since that seemed to do a quite nice job
for the actual searching.
Norman Walsh <ndw@nwalsh.com> writes:
> This message is a kind of carry on to my message about searching. I wanted
> to try notmuch. Historically I use gnus just for email (all nnml). So my
> gnus-select-method is:
>
> (setq gnus-select-method '(nnml ""))
>
> Well, I also have:
>
> (setq gnus-secondary-select-methods
> '((nndiary "")))
>
> but I haven't actually used nndairy in a while. My group display is:
>
> 0, 229: acmecorp
> 0, 7: acmecorp.engineering
> 38, 194: acmecorp.discuss
>
> etc.
>
> The setup instructions for nnir, suggested doing this:
>
> (setq gnus-select-method '(nnml ""
> (nnir-search-engine notmuch)
> ))
>
> When I restart gnus, I get all of my existing groups, but I also get these
>
> 2342, 0: nnml:acmecorp
> 222, 0: nnml:acmecorp.engineering
> 3332, 0: nnml:acmecorp.discuss
>
> I don't actually care about the nnml: prefix, but I'd like to have a
> single list and I'd like not to loose all my existing marks.
>
> Anyone have any idea why my change had the effect that it did? Or how
> to get it fixed?
>
> Be seeing you,
> norm
>
> --
> Norman Walsh <ndw@nwalsh.com> | At least two-thirds of our miseries
> http://nwalsh.com/ | spring from human stupidity, human
> | malice and those great motivators and
> | justifiers of malice and stupidity:
> | idealism, dogmatism and proselytizing
> | zeal on behalf of religous or political
> | ideas.--Aldous Huxley
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | My life has a superb cast but I can’t
http://nwalsh.com/ | figure out the plot.--Ashleigh Brilliant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 172 bytes --]
next prev parent reply other threads:[~2016-01-14 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 22:32 Norman Walsh
2016-01-11 22:44 ` Norman Walsh
2016-01-12 0:51 ` Eric Abrahamsen
2016-01-12 1:01 ` Norman Walsh
2016-01-12 6:51 ` Adam Sjøgren
2016-01-12 7:04 ` Glyn Millington
2016-01-12 7:38 ` Eric Abrahamsen
2016-01-14 15:52 ` Norman Walsh [this message]
2016-01-15 1:46 ` Eric Abrahamsen
2016-01-15 17:01 ` Norman Walsh
2016-01-16 0:13 ` Norman Walsh
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=877fjcrwdu.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
--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).