+2001-09-04 Simon Josefsson <jas@extundo.com>
+
+ * imap.el (imap-search): Don't error if server is broken.
+
2001-09-02 Benjamin Rutt <brutt@bloomington.in.us>
* nnmbox.el (nnmbox-find-article): Fix infinite loop when
(imap-mailbox-put 'search 'dummy)
(when (imap-ok-p (imap-send-command-wait (concat "UID SEARCH " predicate)))
(if (eq (imap-mailbox-get-1 'search imap-current-mailbox) 'dummy)
- (error "Missing SEARCH response to a SEARCH command")
+ (progn
+ (message "Missing SEARCH response to a SEARCH command (server not RFC compliant)...")
+ nil)
(imap-mailbox-get-1 'search imap-current-mailbox)))))
(defun imap-message-flag-permanent-p (flag &optional mailbox buffer)
+2001-09-04 Kai Gro\e,A_\e(Bjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
+
+ * gnus.texi (Optional Backend Functions): More detail about the
+ DATE arg for nnchoke-request-newgroups. Reported by Paul Jarc.
+
2001-09-01 Kai Gro\e,A_\e(Bjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
* gnus.texi (Hooking New Backends Into Gnus): Say where to put the
@item (nnchoke-request-newgroups DATE &optional SERVER)
-\e$B$3$N4X?t$+$iJV$5$l$k7k2L$N%G!<%?$O!"\e(B@samp{date} \e$B0J9_$K:n@.$5$l$?\e(B
-\e$BA4$F$N%0%k!<%W$G$9!#\e(B@samp{date} \e$B$ODL>o$N?M4V$,FI$a$kF|IU$N7A<0$G\e(B
-\e$B$9!#%G!<%?$O\e(B active \e$B%P%C%U%!$N7A<0$G$J$1$l$P$J$j$^$;$s!#\e(B
+\e$B$3$N4X?t$+$iJV$5$l$k7k2L$N%G!<%?$O!"\e(B@samp{date} \e$B0J9_$K:n@.$5$l$?A4$F$N%0\e(B
+\e$B%k!<%W$G$9!#\e(B@samp{date} \e$B$ODL>o$N?M4V$,FI$a$kF|IU$N7A<0\e(B (\e$B$9$J$o$A!"%a!<%k\e(B
+\e$B$d%K%e!<%9$N%X%C%@!<$G;H$o$l$k7A<0$G!"%G%#%U%)%k%H$G$O4X\e(B
+\e$B?t\e(B @code{message-make-date} \e$B$+$iJV$5$l$?$b$N\e(B) \e$B$G$9!#%G!<%?$O\e(B active \e$B%P%C\e(B
+\e$B%U%!$N7A<0$G$J$1$l$P$J$j$^$;$s!#\e(B
+
+\e$B$3$N4X?t$,B?$9$.$k%0%k!<%W$rJV$7$F$b%*!<%1%$$G$9!#$$$/$D$+$N%P%C%/%(%s%I\e(B
+\e$B$O?7$7$$%0%k!<%W$r8+$D$1$k$h$j$b!"3Z$r$7$FA4$F$N%0%k!<%W$N%j%9%H$rJV$9$+\e(B
+\e$B$b$7$l$^$;$s!#$7$+$7%P%C%/%(%s%I$,JV$9B?$/$N%0%k!<%W$KBP$7$F$3$l\e(B (\e$BLuCm\e(B:
+\e$B?7$7$$%0%k!<%W$H$7$F07$&$3$H\e(B) \e$B$r$7$F$O$$$1$^$;$s!#IaDL!"%f!<%6!<<+?H$,:n$C\e(B
+\e$B$?%0%k!<%W$J$i$PB?$9$.$k$3$H$O$J$$$G$7$g$&!#$G$9$+$i\e(B nnml \e$B$H$=$l$KN`$9$k\e(B
+\e$B$b$N$O$?$V$s?4G[$"$j$^$;$s!#$7$+$7\e(B nntp \e$B$N$h$&$J%P%C%/%(%s%I$G$O%0%k!<%W\e(B
+\e$B$O%5!<%P!<$K$h$C$F:n$i$l$F$$$^$9$+$i!"B?$/$N%0%k!<%W$,JV$C$F$/$k$3$H$,$"\e(B
+\e$B$j$($^$9!#\e(B
@item (nnchoke-request-create-group GROUP &optional SERVER)
@item (nnchoke-request-newgroups DATE &optional SERVER)
The result data from this function should be all groups that were
-created after @samp{date}, which is in normal human-readable date
-format. The data should be in the active buffer format.
+created after @samp{date}, which is in normal human-readable date format
+(i.e., the date format used in mail and news headers, and returned by
+the function @code{current-time-string} by default). The data should be
+in the active buffer format.
+
+It is okay for this function to return `too many' groups; some backends
+might find it cheaper to return the full list of groups, rather than
+just the new groups. But don't do this for backends with many groups.
+Normally, if the user creates the groups herself, there won't be too
+many groups, so nnml and the like are probably safe. But for backends
+like nntp, where the groups have been created by the server, it is quite
+likely that there can be many groups.
@item (nnchoke-request-create-group GROUP &optional SERVER)
projects / elisp / gnus.git- / commitdiff