nil, you are either a newcomer to the World of Usenet, or you are very cautious, which is a nice thing to be, really. You will be given questions of the type "Are you sure you want to do this?" before doing anything dangerous.
nil, you will never ever be asked any questions by Gnus. It will simply assume you know what your are doing, no matter how strange.
nil, the user will be prompted for a group name when posting an article.
No, there's nothing here about X, so be quiet.
nil, Gnus will delete all other windows and occupy the entire Emacs screen by itself. It is
((group ([group 1.0 point] (if gnus-carpal [group-carpal 4]))) (article ([summary 0.25 point] [article 1.0])))This is an alist. The key is a symbol that names some action or other. For instance, when displaying the group buffer, the window configuration function will use
groupas the key. A full list of possible names is listed below. The value is a rule that says how much space each buffer should occupy. To take the
articlerule as an example -
(article ([summary 0.25 point] [article 1.0]))This rule says that the summary buffer should occupy 25% of the screen, and that it is placed over the article buffer. As you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all reaching for that calculator there). However, the special number
1.0is used to signal that this buffer should soak up all the rest of the space avaiable after the rest of the buffers have taken whatever they need. There should be only one buffer with the
1.0size spec. Point will be put in the buffer that has the optional third element
point. Here's a more complicated example:
(article ([group 4] [summary 0.25 point] (if gnus-carpal [summary-carpal 4]) [article 1.0])If the size spec is an integer instead of a floating point number, then that number will be used to say how many lines a buffer should occupy, not a percentage. If an element is a list instead of a vector, this list will be
evaled. If the result is non-
nil, it will be used. This means that there will be three buffers if
nil, and four buffers if
nil. Not complicated enough for you? Well, try this on for size:
(article ([group 1.0] [gnus-carpal 4]) ((horizontal 0.5) [summary 0.25 point] [summary-carpal 4] [article 1.0]))Whoops. Two buffers with the mystery 100% tag. And what's that
horizontalthingie? If the first element in one of the rule lists is a list with
horizontalas the first element, Gnus will split the window horizontally, giving you two windows side-by-side. Inside each of these strips you may carry on all you like in the normal fashion. The number following
horizontalsays what percentage of the screen is to be given to this strip. For each horizontal split, there must be one element that has the 100% tag. The splitting is never accurate, and this buffer will eat any leftover lines from the splits. Here's a list of all possible keys:
edit-score. Since this variable is so long and complicated, there's a function you can use to ease changing the config of a single setting:
gnus-add-configuration. If, for instance, you want to change the
articlesetting, you could say:
(gnus-add-configuration '(article ([group 4] [summary .25 point] [article 1.0])))
Those new-fangled mouse contraptions is very popular with the young, hep kids who don't want to learn the proper way to do things these days. Why, I remember way back in the summer of '89, when I was using Emacs on a Tops 20 system. Three hundred users on one single machine, and every user was running Simula compilers. Bah!
Well, you can make Gnus display bufferfuls of buttons you can click to
do anything by setting
t. Pretty simple,
really. Tell the chiropractor I sent you.
buttons variables are lists. The elements in these list
is either a cons cell where the car contains a text to be displayed and
the cdr contains a function symbol, or a simple string.
summary. If the corresponding symbol is present, Gnus will keep that mode line updated with information that may be pertinent. If this variable is
nil, screen refresh may be quicker.
(add-hook 'display-time-hook (lambda () (setq gnus-mode-non-string-length (+ 21 (length display-time-string)))))
nil, Gnus won't attempt to create menus or use fancy colors or fonts. This will also inhibit loading the `gnus-visual.el' file.
mono. If Gnus guesses this display attribute wrongly, either set this variable in your `~/.emacs' or set the resource
Emacs.displayTypein your `~/.Xdefaults'.
dark. If Gnus guesses this frame attribute wrongly, either set this variable in your `~/.emacs' or set the resource
Emacs.backgroundModein your `~/.Xdefaults'. `gnus-display-type'.