From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/76249 Path: news.gmane.org!not-for-mail From: Michael Welsh Duggan Newsgroups: gmane.emacs.gnus.general Subject: Re: Imap split, does not work (of course) Date: Wed, 02 Feb 2011 19:13:00 -0500 Message-ID: <87d3narn5f.fsf@maru.md5i.com> References: <87r5bsleui.fsf@gnus.org> <87bp2uap6c.fsf@ucl.ac.uk> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1296692004 1898 80.91.229.12 (3 Feb 2011 00:13:24 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 3 Feb 2011 00:13:24 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M24601@lists.math.uh.edu Thu Feb 03 01:13:18 2011 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Pkmp4-0004GM-9E for ding-account@gmane.org; Thu, 03 Feb 2011 01:13:18 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1Pkmoy-0007mi-29; Wed, 02 Feb 2011 18:13:12 -0600 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Pkmox-0007mX-0s for ding@lists.math.uh.edu; Wed, 02 Feb 2011 18:13:11 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.72) (envelope-from ) id 1Pkmov-0005hv-Si for ding@lists.math.uh.edu; Wed, 02 Feb 2011 18:13:10 -0600 Original-Received: from md5i.com ([75.151.244.229] helo=maru.md5i.com) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1Pkmou-0004rs-P0 for ding@gnus.org; Thu, 03 Feb 2011 01:13:08 +0100 Original-Received: from md5i by maru.md5i.com with local (Exim 4.72) (envelope-from ) id 1Pkmon-0006He-77 for ding@gnus.org; Wed, 02 Feb 2011 19:13:01 -0500 In-Reply-To: (Richard Riley's message of "Wed, 02 Feb 2011 12:25:36 +0100") User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:76249 Archived-At: Richard Riley writes: > If someone could explain the concept of "backend slots" vs using "setq" > it would help me a lot. Well, in the manual they are not called "backend slots". They are called "server variables", or "server parameters". There is even an info page devoted to describing this, section 6.1.5. Their purpose is as variables that can differ from server to server if your setup contains multiple servers. These variables are set as part of the `gnus-select-method' or `gnus-secondary-select-method's. A select method is a list consisting of a symbol, a name, and then an optional set of "server variable" pairs. An example from the docs: (nnml "public" (nnml-directory "~/my-mail/") (nnml-active-file "~/my-mail/active") (nnml-newsgroups-file "~/my-mail/newsgroups")) The `nnml' symbol is the actual select method. The name of the server is "public", and it set three server variables associated with this server. > I have been unable to see when something should be set with setq and > when things are passed as a parameter to secondary-methods call. Now, the `gnus-select-method' is usually set using `setq'. For the above example: (setq gnus-select-method '(nnml "public" (nnml-directory "~/my-mail/") (nnml-active-file "~/my-mail/active") (nnml-newsgroups-file "~/my-mail/newsgroups"))) On the other hand, `gnus-secondary-select-method' is a set of servers, so it would set there like this: (setq gnus-select-method '((nnml "public" (nnml-directory "~/my-mail/") (nnml-active-file "~/my-mail/active") (nnml-newsgroups-file "~/my-mail/newsgroups")))) Note the extra pair of parentheses. A second would be added like this: (setq gnus-select-method '((nnml "public" (nnml-directory "~/my-mail/") (nnml-active-file "~/my-mail/active") (nnml-newsgroups-file "~/my-mail/newsgroups")) (nnbogus "bogus" (bogus-var-1 "string value") (bogus-var-1 symbol-value)))) All this probably went into more detail than you actually needed, but I feel it is better to give too much information than too little. (I now wait for someone to tell me that I am mistaken about what was meant by "backend slots" in the first place.) -- Michael Welsh Duggan (md5i@md5i.com)