From: physiculus <physiculus@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: physiculus <physiculus@gmail.com>, xuqi <haoyang@expoundite.net>,
info-gnus-english@gnu.org
Subject: Re: nnir with notmuch gives error; Possible solution!
Date: Wed, 25 Mar 2020 20:05:46 +0100 [thread overview]
Message-ID: <87mu84dzlh.fsf_-_@googlemail.com> (raw)
In-Reply-To: <8736a813yb.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 16 Mar 2020 12:42:52 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
Hello,
i think i find the problem, but i cannot repair it.
ALL messages with error in gnus contain a combination !2 in the file
name.
This was used on Windows for correct working of imap folders, because :
is forbidden.
if i change !2 in :2 (this assumes gnus, i read), the message is
accepted.
But how could i change the string inside the filename from !2 to :2 ?
Perhaps with dired, but i dont know how?
Any ideas?
Regards
Poul
> physiculus <physiculus@gmail.com> writes:
>
>> xuqi <haoyang@expoundite.net> writes:
>>
>> Hello,
>> thank you and Eric very much for help. I can't help, because i do not fully
>> understand, what goes wrong.
>
> No, that's perfect! That basically confirms my suspicion that some of
> your message filenames are causing nnmaildir to fail. They're probably
> these:
>
> /home/held/Maildirnm/karlderletzte/INBOX/cur/1554399542.4634_1560.shinri,U=651:2,S
> /home/held/Maildirnm/karlderletzte/Sent/cur/1554294583.6ad7d1c538e8c734.shinri:2,,U=22:2,S!2,S
> /home/held/Maildirnm/karlderletzte/Sent/cur/1554294638.4676_1518.shinri,U=23!2,S
> /home/held/Maildirnm/karlderletzte/INBOX/cur/1554292397.3889_1547.shinri,U=645:2,RS
>
> I'll open a bug report and see if anyone else can help. My last question
> for you is: do you think Gnus/nnmaildir made these files, or is there a
> chance that you're just using Gnus to read a maildir installation that
> was created by a different program?
>
> Eric
_______________________________________________
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:[~2020-03-25 19:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 18:27 nnir with notmuch gives error; sort: Wrong type argument: number-or-marker-p, nil physiculus
2020-03-12 19:09 ` Eric Abrahamsen
2020-03-13 9:46 ` physiculus
2020-03-13 17:04 ` xuqi
2020-03-14 7:52 ` physiculus
2020-03-14 11:30 ` xuqi
2020-03-14 15:31 ` physiculus
2020-03-14 16:11 ` Eric Abrahamsen
2020-03-14 16:23 ` physiculus
2020-03-14 16:47 ` Eric Abrahamsen
2020-03-15 11:45 ` physiculus
2020-03-15 18:50 ` xuqi
2020-03-16 18:42 ` physiculus
2020-03-16 19:42 ` Eric Abrahamsen
2020-03-17 8:50 ` physiculus
2020-03-17 14:22 ` physiculus
2020-03-18 1:27 ` xuqi
2020-03-18 18:02 ` physiculus
2020-03-19 22:56 ` Eric Abrahamsen
2020-03-25 19:05 ` physiculus [this message]
2020-03-25 19:19 ` nnir with notmuch gives error; Possible solution! Eric Abrahamsen
2020-03-26 19:16 ` Helmut Waitzmann
2020-03-15 22:09 ` nnir with notmuch gives error; sort: Wrong type argument: number-or-marker-p, nil Eric Abrahamsen
2020-03-13 18:51 ` Eric Abrahamsen
2020-03-14 7:54 ` physiculus
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=87mu84dzlh.fsf_-_@googlemail.com \
--to=physiculus@gmail.com \
--cc=eric@ericabrahamsen.net \
--cc=haoyang@expoundite.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).