From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org, bugs@gnus.org
Subject: Re: major problem with recent cvs
Date: 14 Mar 2000 00:58:23 +0100 [thread overview]
Message-ID: <iluhfeawhgg.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: Laura Conrad's message of "13 Mar 2000 11:54:56 -0500"
Laura Conrad <lconrad@gamesville.lycos.com> writes:
> I had killed my editor over the weekend, so I upped the cvs before
> restarting it this morning.
...
> I poked around, and regenerated the nov databases, and finally did "ls
> -l" in my Mail directory, and discovered that the messages got written
> by this morning's CVS gnus as files like Mail/world1699 instead of
> Mail/world/1699.
Glancing recent modifications made me came up with this patch. Please
test if it work and I'll commit it.
2000-03-14 Simon Josefsson <jas@pdc.kth.se>
* nnheader.el (nnheader-group-pathname): Add "/".
* nnmail.el (nnmail-group-pathname): Ditto.
Index: nnmail.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/nnmail.el,v
retrieving revision 5.48
diff -w -u -r5.48 nnmail.el
--- nnmail.el 2000/03/13 19:43:14 5.48
+++ nnmail.el 2000/03/13 23:56:44
@@ -470,12 +470,14 @@
;; If this directory exists, we use it directly.
(if (or nnmail-use-long-file-names
(file-directory-p (concat dir group)))
- (expand-file-name group dir)
+ (expand-file-name (concat group "/") dir)
;; If not, we translate dots into slashes.
(expand-file-name
+ (concat
(mm-encode-coding-string
(nnheader-replace-chars-in-string group ?. ?/)
nnmail-pathname-coding-system)
+ "/")
dir)))
(or file "")))
Index: nnheader.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/nnheader.el,v
retrieving revision 5.35
diff -w -u -r5.35 nnheader.el
--- nnheader.el 2000/03/13 13:50:38 5.35
+++ nnheader.el 2000/03/13 23:56:44
@@ -730,11 +730,13 @@
(let ((dir (file-name-as-directory (expand-file-name dir))))
;; If this directory exists, we use it directly.
(if (file-directory-p (concat dir group))
- (expand-file-name group dir)
+ (expand-file-name (concat group "/") dir)
;; If not, we translate dots into slashes.
- (expand-file-name (mm-encode-coding-string
+ (expand-file-name (concat
+ (mm-encode-coding-string
(nnheader-replace-chars-in-string group ?. ?/)
nnheader-pathname-coding-system)
+ "/")
dir)))
(cond ((null file) "")
((numberp file) (int-to-string file))
next prev parent reply other threads:[~2000-03-13 23:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 16:54 Laura Conrad
2000-03-13 23:58 ` Simon Josefsson [this message]
2000-03-14 10:48 ` Kai Großjohann
2000-03-14 11:42 ` Simon Josefsson
2000-03-14 14:56 ` lconrad
2000-03-14 15:07 ` Karl Kleinpaste
2000-03-14 15:37 ` Laura Conrad
2000-03-14 15:59 ` Kai Großjohann
2000-03-14 16:18 ` Laura Conrad
2000-03-14 16:55 ` Gunnar Evermann
2000-03-14 16:57 ` Kai Großjohann
2000-03-14 16:47 ` Kai Großjohann
2000-03-14 20:18 ` lconrad
2000-03-17 17:12 ` Resolution (was: Re: major problem with recent cvs) lconrad
2000-03-15 10:43 ` major problem with recent cvs Per Abrahamsen
2000-03-15 18:07 ` Jan Vroonhof
2000-03-16 10:34 ` Per Abrahamsen
2000-03-16 11:40 ` Jan Vroonhof
2000-03-17 13:20 ` Per Abrahamsen
2000-03-14 16:43 ` Jan Vroonhof
2000-03-14 17:17 ` Jan Vroonhof
[not found] <8aj6qv$qvc$1@quimby.gnus.org>
2000-03-13 20:48 ` Emerick Rogul
2000-03-14 17:35 ` Matt Swift
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=iluhfeawhgg.fsf@badis.pdc.kth.se \
--to=jas@pdc.kth.se \
--cc=bugs@gnus.org \
--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).