From: Reiner Steib <reinersteib+gmane@imap.cc>
To: <ding@gnus.org>
Cc: Holger Sparr <sparr@mfkrs1.mw.tu-dresden.de>
Subject: Re: nndiary documentation bug
Date: Mon, 07 May 2007 18:32:27 +0200 [thread overview]
Message-ID: <v9hcqolhlw.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <mux7irk93ue.fsf@uzeb.lrde.epita.fr> (Didier Verna's message of "Mon\, 07 May 2007 15\:10\:33 +0200")
On Mon, May 07 2007, Didier Verna wrote:
> I'm actually reluctant to advertise this variable as a server one
> (although technically, I guess it's possible to use it that way).
Okay.
>> BTW, is there any reason _not_ to include (info "(gnus)Running
>> NNDiary") in the stable branch (v5-10)?
>
> If nndiary is present in the stable branch, the whole "Email Based
> Diary" node should be included in the doc.
Apart from minor issues (compatibility code) and comments (moved to
gnus.texi), the versions of nndiary.el and gnus-diary.el in trunk and
v5-10 are identical. So I will sync the lisp files and install (info
"(gnus)Email Based Diary") in v5-10 unless you'd like to do it
yourself.
Bye, Reiner.
--8<---------------cut here---------------start------------->8---
--- v5-10/lisp/nndiary.el 2007-02-04 17:09:38.000000000 +0100
+++ No/lisp/nndiary.el 2007-01-26 20:41:00.000000000 +0100
@@ -725,7 +606,7 @@
(nconc rest articles)))
(deffoo nndiary-request-move-article
- (article group server accept-form &optional last)
+ (article group server accept-form &optional last move-is-internal)
(let ((buf (get-buffer-create " *nndiary move*"))
result)
(nndiary-possibly-change-directory group server)
@@ -994,7 +875,7 @@
(search-forward id nil t)) ; We find the ID.
;; And the id is in the fourth field.
(if (not (and (search-backward "\t" nil t 4)
- (not (search-backward"\t" (gnus-point-at-bol) t))))
+ (not (search-backward"\t" (point-at-bol) t))))
(forward-line 1)
(beginning-of-line)
(setq found t)
@@ -1215,9 +1096,7 @@
(push (list group
(cons (or (caar files) (1+ last))
(max last
- (or (let ((f files))
- (while (cdr f) (setq f (cdr f)))
- (caar f))
+ (or (caar (last files))
0))))
nndiary-group-alist)))
--- v5-10/lisp/gnus-diary.el 2007-02-04 17:09:37.000000000 +0100
+++ plain_No/lisp/gnus-diary.el 2007-01-26 20:40:58.000000000 +0100
@@ -402,7 +347,7 @@
(when (re-search-forward (concat "^" header ":") nil t)
(unless (eq (char-after) ? )
(insert " "))
- (setq value (buffer-substring (point) (gnus-point-at-eol)))
+ (setq value (buffer-substring (point) (point-at-eol)))
(and (string-match "[ \t]*\\([^ \t]+\\)[ \t]*" value)
(setq value (match-string 1 value)))
(condition-case ()
--8<---------------cut here---------------end--------------->8---
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-05-07 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <lnwszpc061.fsf@mfk.tu-dresden.de>
2007-05-03 18:54 ` Reiner Steib
2007-05-07 13:10 ` Didier Verna
2007-05-07 14:29 ` Holger Sparr
2007-05-09 7:13 ` Didier Verna
2007-05-07 16:32 ` Reiner Steib [this message]
2007-05-09 7:03 ` Didier Verna
2007-05-09 9:30 ` Kamen TOMOV
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=v9hcqolhlw.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=sparr@mfkrs1.mw.tu-dresden.de \
/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).