Gnus development mailing list
 help / color / mirror / Atom feed
From: John Haman <>
Subject: Re: The current state of gnus-cloud
Date: Sat, 13 Jan 2024 17:34:00 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Steinar Bang's message of "Mon, 08 Jan 2024 14:11:24 +0100")

Steinar Bang <> writes:

> Second hurdle: gnus sync fails because it can't handle files with ":" in
> their names on Windows. Stack trace here:

I use the following in my gnus.el

;;; Colon is illegal on Windows filesystem
  (setq nnheader-file-name-translation-alist '((?: . ?_)))

now, no colons in score files.

Dr. John Haman
Maryland, USA

  parent reply	other threads:[~2024-01-13 22:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-05 15:50 Steinar Bang
2024-01-08 13:11 ` Steinar Bang
2024-01-13 15:16   ` John Haman
2024-01-13 22:34   ` John Haman [this message]
2024-01-15 15:54     ` Steinar Bang
2024-01-17  7:24       ` Steinar Bang
2024-01-21 19:32         ` Andy Moreton
2024-01-24 17:51           ` Steinar Bang

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).