Mercurial > emacs
annotate doc/misc/sc.texi @ 107712:6a80fb868018
Change name of default value of calc-settings-file to ~/.emacs.d/calc.el throughout.
author | Jay Belanger <jay.p.belanger@gmail.com> |
---|---|
date | Tue, 30 Mar 2010 22:47:52 -0500 |
parents | 1d1d5d9bd884 |
children | f1266b2f017e |
rev | line source |
---|---|
84313 | 1 \input texinfo @comment -*-texinfo-*- |
2 @comment 3.48 | |
3 @comment %**start of header (This is for running Texinfo on a region.) | |
84329
3d431f1997d8
(setfilename): Go up one more level to ../../info.
Glenn Morris <rgm@gnu.org>
parents:
84313
diff
changeset
|
4 @setfilename ../../info/sc |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
5 @settitle Supercite User's Manual |
84313 | 6 @iftex |
7 @finalout | |
8 @end iftex | |
9 | |
10 @c @setchapternewpage odd % For book style double sided manual. | |
11 @comment %**end of header (This is for running Texinfo on a region.) | |
12 | |
13 @copying | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
14 This document describes Supercite, an Emacs package for citing and |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
15 attributing replies to mail and news messages. |
84313 | 16 |
105934
26b37c3219d1
(Hints to MUA Authors): MUA should do any decoding.
Glenn Morris <rgm@gnu.org>
parents:
102059
diff
changeset
|
17 Copyright @copyright{} 1993, 2001, 2002, 2003, 2004, 2005, 2006, 2007, |
106815 | 18 2008, 2009, 2010 Free Software Foundation, Inc. |
84313 | 19 |
20 @quotation | |
21 Permission is granted to copy, distribute and/or modify this document | |
99709
6de181810d0f
Relicense all texi files under FDL 1.3 or later.
Glenn Morris <rgm@gnu.org>
parents:
95937
diff
changeset
|
22 under the terms of the GNU Free Documentation License, Version 1.3 or |
84313 | 23 any later version published by the Free Software Foundation; with no |
95937
6f0fce2c3559
Remove references to external license, since doclicense is included.
Glenn Morris <rgm@gnu.org>
parents:
95874
diff
changeset
|
24 Invariant Sections, with the Front-Cover texts being ``A GNU Manual'', |
6f0fce2c3559
Remove references to external license, since doclicense is included.
Glenn Morris <rgm@gnu.org>
parents:
95874
diff
changeset
|
25 and with the Back-Cover Texts as in (a) below. A copy of the license |
6f0fce2c3559
Remove references to external license, since doclicense is included.
Glenn Morris <rgm@gnu.org>
parents:
95874
diff
changeset
|
26 is included in the section entitled ``GNU Free Documentation License''. |
84313 | 27 |
95874
eafbd7a5c9be
Update Back-Cover Text as per maintain.info.
Glenn Morris <rgm@gnu.org>
parents:
92246
diff
changeset
|
28 (a) The FSF's Back-Cover Text is: ``You have the freedom to copy and |
eafbd7a5c9be
Update Back-Cover Text as per maintain.info.
Glenn Morris <rgm@gnu.org>
parents:
92246
diff
changeset
|
29 modify this GNU manual. Buying copies from the FSF supports it in |
eafbd7a5c9be
Update Back-Cover Text as per maintain.info.
Glenn Morris <rgm@gnu.org>
parents:
92246
diff
changeset
|
30 developing GNU and promoting software freedom.'' |
84313 | 31 @end quotation |
32 @end copying | |
33 | |
34 @c @smallbook | |
35 | |
36 @dircategory Emacs | |
37 @direntry | |
38 * SC: (sc). Supercite lets you cite parts of messages you're | |
39 replying to, in flexible ways. | |
40 @end direntry | |
41 | |
42 @titlepage | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
43 @title Supercite User's Manual |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
44 @subtitle cite and attribute mail and |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
45 @subtitle news, in flexible ways |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
46 |
84313 | 47 @page |
48 @vskip 0pt plus 1filll | |
49 @insertcopying | |
50 @end titlepage | |
51 | |
102059
9bcea07061a8
consistently use @insertcopying, @direntry, @contents
Karl Berry <karl@gnu.org>
parents:
100974
diff
changeset
|
52 @summarycontents |
9bcea07061a8
consistently use @insertcopying, @direntry, @contents
Karl Berry <karl@gnu.org>
parents:
100974
diff
changeset
|
53 @contents |
9bcea07061a8
consistently use @insertcopying, @direntry, @contents
Karl Berry <karl@gnu.org>
parents:
100974
diff
changeset
|
54 |
84313 | 55 @ifnottex |
56 @node Top, Introduction, (dir), (dir) | |
57 @comment node-name, next, previous, up | |
58 | |
102059
9bcea07061a8
consistently use @insertcopying, @direntry, @contents
Karl Berry <karl@gnu.org>
parents:
100974
diff
changeset
|
59 @insertcopying |
9bcea07061a8
consistently use @insertcopying, @direntry, @contents
Karl Berry <karl@gnu.org>
parents:
100974
diff
changeset
|
60 |
9bcea07061a8
consistently use @insertcopying, @direntry, @contents
Karl Berry <karl@gnu.org>
parents:
100974
diff
changeset
|
61 The manual is divided |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
62 into the following chapters. |
84313 | 63 |
64 @menu | |
65 * Introduction:: | |
66 * Citations:: | |
67 * Getting Connected:: | |
68 * Replying and Yanking:: | |
69 * Selecting an Attribution:: | |
70 * Configuring the Citation Engine:: | |
71 * Post-yank Formatting Commands:: | |
72 * Information Keys and the Info Alist:: | |
73 * Reference Headers:: | |
74 * Hints to MUA Authors:: | |
75 * Thanks and History:: | |
76 | |
77 * GNU Free Documentation License:: | |
78 * Concept Index:: | |
79 * Command Index:: | |
80 * Key Index:: | |
81 * Variable Index:: | |
82 @end menu | |
83 @end ifnottex | |
84 | |
85 | |
86 @node Introduction, Usage Overview, Top, Top | |
87 @chapter Introduction | |
88 | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
89 Supercite is a GNU Emacs package written entirely in Emacs Lisp. It |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
90 interfaces to most of the commonly used Emacs mail user agents |
84313 | 91 (@dfn{MUAs}) and news user agents (@dfn{NUAs}), and provides |
92 sophisticated facilities for the citing and attributing of message | |
93 replies. Supercite has a very specific and limited role in the process | |
94 of composing replies to both USENET network news and electronic mail. | |
95 | |
96 The preferred way to spell Supercite is with a capital @samp{S}, | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
97 lowercase @samp{upercite}. |
84313 | 98 |
99 @ifinfo | |
100 @menu | |
101 * Usage Overview:: | |
102 * What Supercite Does Not Do:: | |
103 * What Supercite Does:: | |
104 @end menu | |
105 @end ifinfo | |
106 | |
107 @cindex MUA | |
108 @cindex NUA | |
109 Supercite is only useful in conjunction with MUAs and NUAs such as VM, | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
110 Gnus, RMAIL, MH-E, etc. Supercite is typically called by the MUA after a |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
111 reply buffer has been setup. Thereafter, Supercite's many commands and |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
112 formatting styles are available in that reply buffer until the reply is |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
113 sent. Supercite is re-initialized in each new reply buffer. |
84313 | 114 |
115 | |
116 @node Usage Overview, What Supercite Does Not Do, Introduction, Introduction | |
117 @kindex r | |
118 @kindex f | |
119 @kindex C-c C-y | |
120 @cindex yank | |
121 @cindex cite, citing | |
122 @cindex attribute, attributing | |
123 @section Usage Overview | |
124 | |
125 Typical usage is as follows. You want to reply or followup to a message | |
126 in your MUA. You will probably hit @kbd{r} (i.e., ``reply'') or @kbd{f} | |
127 (i.e., ``forward'') to begin composing the reply. In response, the MUA | |
128 will create a reply buffer and initialize the outgoing mail headers | |
129 appropriately. The body of the reply will usually be empty at this | |
130 point. You now decide that you would like to include part of the | |
131 original message in your reply. To do this, you @dfn{yank} the original | |
132 message into the reply buffer, typically with a key stroke such as | |
133 @kbd{C-c C-y}. This sequence will invoke an MUA-specific function which | |
134 fills the body of the reply with the original message and then | |
135 @dfn{attributes} this text to its author. This is called @dfn{citing} | |
136 and its effect is to prefix every line from the original message with a | |
137 special text tag. Most MUAs provide some default style of citing; by | |
138 using Supercite you gain a wider flexibility in the look and style of | |
139 citations. Supercite's only job is to cite the original message. | |
140 | |
141 @node What Supercite Does Not Do, What Supercite Does, Usage Overview, Introduction | |
142 @section What Supercite Doesn't Do | |
143 | |
144 Because of this clear division of labor, there are useful features which | |
145 are the sole responsibility of the MUA, even though it might seem that | |
146 Supercite should provide them. For example, many people would like to | |
147 be able to yank (and cite) only a portion of the original message. | |
148 Since Supercite only modifies the text it finds in the reply buffer as | |
149 set up by the MUA, it is the MUA's responsibility to do partial yanking. | |
150 @xref{Reply Buffer Initialization}.@refill | |
151 | |
152 @vindex mail-header-separator | |
153 Another potentially useful thing would be for Supercite to set up the | |
154 outgoing mail headers with information it gleans from the reply buffer. | |
155 But by previously agreed upon convention, any text above the | |
156 @code{mail-header-separator} which separates mail headers from message | |
157 bodies cannot be modified by Supercite. Supercite, in fact, doesn't | |
158 know anything about the meaning of these headers, and never ventures | |
159 outside the designated region. @xref{Hints to MUA Authors}, for more | |
160 details.@refill | |
161 | |
162 @node What Supercite Does, Citations, What Supercite Does Not Do, Introduction | |
163 @findex sc-cite-original | |
164 @section What Supercite Does | |
165 | |
166 Supercite is invoked for the first time on a reply buffer via your MUA's | |
167 reply or forward command. This command will actually perform citations | |
168 by calling a hook variable to which Supercite's top-level function | |
169 @code{sc-cite-original} has been added. When @code{sc-cite-original} is | |
170 executed, the original message must be set up in a very specific way, | |
171 but this is handled automatically by the MUA. @xref{Hints to MUA | |
172 Authors}.@refill | |
173 | |
174 @cindex info alist | |
175 The first thing Supercite does, via @code{sc-cite-original}, is to parse | |
176 through the original message's mail headers. It saves this data in an | |
177 @dfn{information association list}, or @dfn{info alist}. The information | |
178 in this list is used in a number of places throughout Supercite. | |
179 @xref{Information Keys and the Info Alist}.@refill | |
180 | |
181 @cindex nuking mail headers | |
182 @cindex reference header | |
183 After the mail header info is extracted, the headers are optionally | |
184 removed (@dfn{nuked}) from the reply. Supercite then writes a | |
185 @dfn{reference header} into the buffer. This reference header is a | |
186 string carrying details about the citation it is about to perform. | |
187 | |
188 @cindex modeline | |
189 Next, Supercite visits each line in the reply, transforming the line | |
190 according to a customizable ``script.'' Lines which were not previously | |
191 cited in the original message are given a citation, while already cited | |
192 lines remain untouched, or are coerced to your preferred style. | |
193 Finally, Supercite installs a keymap into the reply buffer so that you | |
194 have access to Supercite's post-yank formatting and reciting commands as | |
195 you subsequently edit your reply. You can tell that Supercite has been | |
196 installed into the reply buffer because that buffer's modeline will | |
197 display the minor mode string @samp{SC}. | |
198 | |
199 @cindex filladapt | |
200 @cindex gin-mode | |
201 @vindex fill-prefix | |
202 @findex fill-paragraph | |
203 When the original message is cited by @code{sc-cite-original}, it will | |
204 (optionally) be filled by Supercite. However, if you manually edit the | |
205 cited text and want to re-fill it, you must use an add-on package such | |
206 as @cite{filladapt} or @cite{gin-mode}. These packages can recognize | |
207 Supercited text and will fill them appropriately. Emacs' built-in | |
208 filling routines, e.g@. @code{fill-paragraph}, do not recognize cited | |
209 text and will not re-fill them properly because it cannot guess the | |
210 @code{fill-prefix} being used. | |
211 @xref{Post-yank Formatting Commands}, for details.@refill | |
212 | |
213 As mentioned above, Supercite provides commands to recite or uncite | |
214 regions of text in the reply buffer, and commands to perform other | |
215 beautifications on the cited original text, maintaining consistent and | |
216 informative citations throughout. Supercite tries to be as configurable | |
217 as possible to allow for a wide range of personalized citation styles, | |
218 but it is also immediately useful with the default configuration, once | |
219 it has been properly connected to your MUA. @xref{Getting Connected}, | |
220 for more details.@refill | |
221 | |
222 @node Citations, Citation Elements, What Supercite Does, Top | |
223 @cindex nested citations | |
224 @cindex citation | |
225 @chapter Citations | |
226 | |
227 A @dfn{citation} is the acknowledgement of the original author of a mail | |
228 message in the body of the reply. There are two basic citation styles | |
229 which Supercite supports. The first, called @dfn{nested citations} is | |
230 an anonymous form of citation; in other words, an indication is made | |
231 that the cited line was written by someone @emph{other} that the current | |
232 message author (i.e., other than you, the person composing the reply), | |
233 but no reference is made as to the identity of the original author. | |
234 This style should look familiar since its use on the net is widespread. | |
235 Here's an example of what a message buffer would look like using nested | |
236 citations after multiple replies: | |
237 | |
238 @example | |
239 >> John originally wrote this | |
240 >> and this as well | |
241 > Jane said that John didn't know | |
242 > what he was talking about | |
243 And that's what I think too. | |
244 @end example | |
245 | |
246 @ifinfo | |
247 @menu | |
248 * Citation Elements:: | |
249 * Recognizing Citations:: | |
250 @end menu | |
251 @end ifinfo | |
252 | |
253 Note that multiple inclusions of the original messages result in a | |
254 nesting of the @samp{@code{>}} characters. This can sometimes be quite | |
255 confusing when many levels of citations are included since it may be | |
256 difficult or impossible to figure out who actually participated in the | |
257 thread, and multiple nesting of @samp{@code{>}} characters can sometimes | |
258 make the message very difficult for the eye to scan. | |
259 | |
260 @cindex non-nested citations | |
261 In @dfn{non-nested citations}, each cited line begins with an | |
262 informative string attributing that line to the original author. Only | |
263 the first level of attribution will be shown; subsequent citations don't | |
264 nest the citation strings. The above dialog might look like this when | |
265 non-nested citations are used: | |
266 | |
267 @example | |
268 John> John originally wrote this | |
269 John> and this as well | |
270 Jane> Jane said that John didn't know | |
271 Jane> what he was talking about | |
272 And that's what I think too. | |
273 @end example | |
274 | |
275 Notice here that my inclusion of Jane's inclusion of John's original | |
276 message did not result in a line cited with @samp{Jane>John>}. | |
277 | |
278 @vindex sc-nested-citation-p | |
279 @vindex nested-citation-p (sc-) | |
280 Supercite supports both styles of citation, and the variable | |
281 @code{sc-nested-citation-p} controls which style it will use when citing | |
282 previously uncited text. When this variable is @code{nil} (the default), | |
283 non-nested citations are used. When non-@code{nil}, nested citations | |
284 are used. | |
285 | |
286 | |
287 @node Citation Elements, Recognizing Citations, Citations, Citations | |
288 @cindex citation string | |
289 @section Citation Elements | |
290 | |
291 @dfn{Citation strings} are composed of one or more elements. Non-nested | |
292 citations are composed of four elements, three of which are directly | |
293 user definable. The elements are concatenated together, in this order: | |
294 | |
295 @cindex citation leader | |
296 @vindex citation-leader (sc-) | |
297 @vindex sc-citation-leader | |
298 @enumerate | |
299 @item | |
300 The @dfn{citation leader}. The citation leader is contained in the | |
301 variable @code{sc-citation-leader}, and has the default value of a | |
302 string containing four spaces. | |
303 | |
304 @cindex attribution string | |
305 @item | |
306 The @dfn{attribution string}. This element is supplied automatically by | |
307 Supercite, based on your preferences and the original message's mail | |
308 headers, though you may be asked to confirm Supercite's choice. | |
309 @xref{Selecting an Attribution}, for more details.@refill | |
310 | |
311 @cindex citation delimiter | |
312 @vindex sc-citation-delimiter | |
313 @vindex citation-delimiter (sc-) | |
314 @item | |
315 The @dfn{citation delimiter}. This string, contained in the variable | |
316 @code{sc-citation-delimiter} visually separates the citation from the | |
317 text of the line. This variable has a default value of @code{">"} and | |
318 for best results, the string should consist of only a single character. | |
319 | |
320 @cindex citation separator | |
321 @vindex citation-separator (sc-) | |
322 @vindex sc-citation-separator | |
323 @item | |
324 The @dfn{citation separator}. The citation separator is contained in | |
325 the variable @code{sc-citation-separator}, and has the default value of | |
326 a string containing a single space. | |
327 @end enumerate | |
328 | |
329 For example, suppose you were using the default values for the above | |
330 variables, and Supercite provided the attribution string @samp{Jane}. | |
331 In this case, the composed, non-nested citation string used might be | |
332 something like | |
333 @code{@asis{" Jane> "}}. | |
334 This citation string will be inserted in front of | |
335 every line in the original message that is not already cited.@refill | |
336 | |
337 Nested citations, being simpler than non-nested citations, are composed | |
338 of the same elements, sans the attribution string. Supercite is smart | |
339 enough to not put additional spaces between citation delimiters for | |
340 multi-level nested citations. | |
341 | |
342 @node Recognizing Citations, Getting Connected, Citation Elements, Citations | |
343 @section Recognizing Citations | |
344 | |
345 Supercite also recognizes citations in the original article, and can | |
346 transform these already cited lines in a number of ways. This is how | |
347 Supercite suppresses the multiple citing of non-nested citations. | |
348 Recognition of cited lines is controlled by variables analogous to those | |
349 that make up the citation string as mentioned previously. | |
350 | |
351 @vindex sc-citation-leader-regexp | |
352 @vindex citation-leader-regexp (sc-) | |
353 @vindex sc-citation-delimiter-regexp | |
354 @vindex citation-delimiter-regexp (sc-) | |
355 @vindex sc-citation-separator-regexp | |
356 @vindex citation-separator-regexp (sc-) | |
357 @vindex sc-citation-root-regexp | |
358 @vindex citation-root-regexp (sc-) | |
359 @vindex sc-citation-nonnested-root-regexp | |
360 @vindex citation-nonnested-root-regexp (sc-) | |
361 | |
362 The variable @code{sc-citation-leader-regexp} describes how citation | |
363 leaders can look, by default it matches any number of spaces or tabs. | |
364 Note that since the lisp function @code{looking-at} is used to do the | |
365 matching, if you change this variable it need not start with a leading | |
366 @code{"^"}. | |
367 | |
368 Similarly, the variables @code{sc-citation-delimiter-regexp} and | |
369 @code{sc-citation-separator-regexp} respectively describe how citation | |
370 delimiters and separators can look. They follow the same rule as | |
371 @code{sc-citation-leader-regexp} above. | |
372 | |
373 When Supercite composes a citation string, it provides the attribution | |
374 automatically. The analogous variable which handles recognition of the | |
375 attribution part of citation strings is @code{sc-citation-root-regexp}. | |
376 This variable describes the attribution root for both nested and | |
377 non-nested citations. By default it can match zero-to-many alphanumeric | |
378 characters (also ``.'', ``-'', and ``_''). But in some situations, | |
379 Supercite has to determine whether it is looking at a nested or | |
380 non-nested citation. Thus the variable | |
381 @code{sc-citation-nonnested-root-regexp} is used to describe only | |
382 non-nested citation roots. It is important to remember that if you | |
383 change @code{sc-citation-root-regexp} you should always also change | |
384 @code{sc-citation-nonnested-root-regexp}.@refill | |
385 | |
386 @node Information Keys and the Info Alist, Reference Headers, Miscellaneous Commands, Top | |
387 @cindex information keys | |
388 @cindex Info Alist | |
389 @cindex information extracted from mail fields | |
390 @findex sc-mail-field | |
391 @findex mail-field (sc-) | |
392 @chapter Information Keys and the Info Alist | |
393 | |
394 @dfn{Mail header information keys} are nuggets of information that | |
395 Supercite extracts from the various mail headers of the original | |
396 message, placed in the reply buffer by the MUA. Information is kept in | |
397 the @dfn{Info Alist} as key-value pairs, and can be retrieved for use in | |
398 various places within Supercite, such as in header rewrite functions and | |
399 attribution selection. Other bits of data, composed and created by | |
400 Supercite, are also kept as key-value pairs in this alist. In the case | |
401 of mail fields, the key is the name of the field, omitting the trailing | |
402 colon. Info keys are always case insensitive (as are mail headers), and | |
403 the value for a corresponding key can be retrieved from the alist with | |
404 the @code{sc-mail-field} function. Thus, if the following fields were | |
405 present in the original article:@refill | |
406 | |
407 @example | |
408 Date:@: 08 April 1991, 17:32:09 EST | |
409 Subject:@: Better get out your asbestos suit | |
410 @end example | |
411 | |
412 @vindex sc-mumble | |
413 @vindex mumble (sc-) | |
414 @noindent | |
415 then, the following lisp constructs return: | |
416 | |
417 @example | |
418 (sc-mail-field "date") | |
419 ==> "08 April 1991, 17:32:09 EST" | |
420 | |
421 (sc-mail-field "subject") | |
422 ==> "Better get out your asbestos suit" | |
423 @end example | |
424 | |
425 Since the argument to @code{sc-mail-field} can be any string, it is | |
426 possible that the mail field will not be present on the info alist | |
427 (possibly because the mail header was not present in the original | |
428 message). In this case, @code{sc-mail-field} will return the value of | |
429 the variable @code{sc-mumble}. | |
430 | |
431 Supercite always places all mail fields found in the yanked original | |
432 article into the info alist. If possible, Supercite will also places | |
433 the following keys into the info alist: | |
434 | |
435 @table @code | |
436 @cindex sc-attribution info field | |
437 @cindex attribution info field (sc-) | |
438 @item "sc-attribution" | |
439 the selected attribution string. | |
440 | |
441 @cindex sc-citation info field | |
442 @cindex citation info field (sc-) | |
443 @item "sc-citation" | |
444 the non-nested citation string. | |
445 | |
446 @cindex sc-from-address info field | |
447 @cindex from-address info field (sc-) | |
448 @item "sc-from-address" | |
449 email address extracted from the @samp{From:@:} field. | |
450 | |
451 @cindex sc-reply-address info field | |
452 @cindex reply-address info field (sc-) | |
453 @item "sc-reply-address" | |
454 email address extracted from the @samp{Reply-To:@:} field. | |
455 | |
456 @cindex sc-sender-address info field | |
457 @cindex sender-address info field (sc-) | |
458 @item "sc-sender-address" | |
459 email address extracted from the @samp{Sender:@:} field. | |
460 | |
461 @cindex sc-emailname info field | |
462 @cindex emailname info field (sc-) | |
463 @item "sc-emailname" | |
464 email terminus extracted from the @samp{From:@:} field. | |
465 | |
466 @cindex sc-initials info field | |
467 @cindex initials info field (sc-) | |
468 @item "sc-initials" | |
469 the author's initials. | |
470 | |
471 @cindex sc-author info field | |
472 @cindex author info field (sc-) | |
473 @item "sc-author" | |
474 the author's full name. | |
475 | |
476 @cindex sc-firstname info field | |
477 @cindex firstname info field (sc-) | |
478 @item "sc-firstname" | |
479 the author's first name. | |
480 | |
481 @cindex sc-lastname info field | |
482 @cindex lastname info field (sc-) | |
483 @item "sc-lastname" | |
484 the author's last name. | |
485 | |
486 @cindex sc-middlename-1 info field | |
487 @cindex middlename-1 info field (sc-) | |
488 @item "sc-middlename-1" | |
489 the author's first middle name. | |
490 @end table | |
491 | |
492 If the author's name has more than one middle name, they will appear as | |
493 info keys with the appropriate index (e.g., @code{"sc-middlename-2"}, | |
494 @dots{}). @xref{Selecting an Attribution}.@refill | |
495 | |
496 @node Reference Headers, The Built-in Header Rewrite Functions, Information Keys and the Info Alist, Top | |
497 @cindex reference headers | |
498 @chapter Reference Headers | |
499 | |
500 Supercite will insert an informative @dfn{reference header} at the | |
501 beginning of the cited body of text, which display more detail about the | |
502 original article and provides the mapping between the attribution and | |
503 the original author in non-nested citations. Whereas the citation | |
504 string usually only contains a portion of the original author's name, | |
505 the reference header can contain such information as the author's full | |
506 name, email address, the original article's subject, etc. In fact any | |
507 information contained in the info alist can be inserted into a reference | |
508 header. | |
509 | |
510 @ifinfo | |
511 @menu | |
512 * The Built-in Header Rewrite Functions:: | |
513 * Electric References:: | |
514 @end menu | |
515 @end ifinfo | |
516 | |
517 @cindex header rewrite functions | |
518 @vindex sc-rewrite-header-list | |
519 @vindex rewrite-header-list (sc-) | |
520 There are a number of built-in @dfn{header rewrite functions} supplied | |
521 by Supercite, but you can write your own custom header rewrite functions | |
522 (perhaps using the built-in ones as examples). The variable | |
523 @code{sc-rewrite-header-list} contains the list of such header rewrite | |
524 functions. This list is consulted both when inserting the initial | |
525 reference header, and when displaying @dfn{electric references}. | |
526 @xref{Electric References}. | |
527 | |
528 @vindex sc-preferred-header-style | |
529 @vindex preferred-header-style (sc-) | |
530 When Supercite is initially run on a reply buffer (via | |
531 @code{sc-cite-original}), it will automatically call one of these | |
532 functions. The one it uses is defined in the variable | |
533 @code{sc-preferred-header-style}. The value of this variable is an | |
534 integer which is an index into the @code{sc-rewrite-header-list}, | |
535 beginning at zero. | |
536 | |
537 @node The Built-in Header Rewrite Functions, Electric References, Reference Headers, Reference Headers | |
538 @cindex header rewrite functions, built-in | |
539 @section The Built-in Header Rewrite Functions | |
540 | |
541 Below are examples of the various built-in header rewrite functions. | |
542 Please note the following:@: first, the text which appears in the | |
543 examples below as @var{infokey} indicates that the corresponding value | |
544 of the info key from the info alist will be inserted there. | |
545 (@pxref{Information Keys and the Info Alist}). For example, in @code{sc-header-on-said} | |
546 below, @var{date} and @var{from} correspond to the values of the | |
547 @samp{Date:@:} and @samp{From:@:} mail headers respectively.@refill | |
548 | |
549 @vindex sc-reference-tag-string | |
550 @vindex reference-tag-string (sc-) | |
551 Also, the string @code{">>>>>"} below is really the value of the | |
552 variable @code{sc-reference-tag-string}. This variable is used in all | |
553 built-in header rewrite functions, and you can customize its value to | |
554 change the tag string globally. | |
555 | |
556 Finally, the references headers actually written may omit certain parts | |
557 of the header if the info key associated with @var{infokey} is not | |
558 present in the info alist. In fact, for all built-in headers, if the | |
559 @samp{From:@:} field is not present in the mail headers, the entire | |
560 reference header will be omitted (but this usually signals a serious | |
561 problem either in your MUA or in Supercite's installation). | |
562 | |
563 @table @code | |
564 @findex sc-no-header | |
565 @findex no-header (sc-) | |
566 @item sc-no-header | |
567 This function produces no header. It should be used instead of | |
568 @code{nil} to produce a blank header. This header can possibly contain | |
569 a blank line after the @code{mail-header-separator} line. | |
570 | |
571 @item sc-no-blank-line-or-header | |
572 @findex sc-no-blank-line-or-header | |
573 @findex no-blank-line-or-header (sc-) | |
574 This function is similar to @code{sc-no-header} except that any blank | |
575 line after the @code{mail-header-separator} line will be removed. | |
576 | |
577 @item sc-header-on-said | |
578 @findex sc-header-on-said | |
579 @findex header-on-said (sc-) | |
580 @code{>>>>> On @var{date}, @var{from} said:} | |
581 | |
582 @item sc-header-inarticle-writes | |
583 @findex sc-header-inarticle-writes | |
584 @findex header-inarticle-writes (sc-) | |
585 @code{>>>>> In article @var{message-id}, @var{from} writes:} | |
586 | |
587 @item sc-header-regarding-adds | |
588 @findex sc-header-regarding-adds | |
589 @findex header-regarding-adds (sc-) | |
590 @code{>>>>> Regarding @var{subject}; @var{from} adds:} | |
591 | |
592 @item sc-header-attributed-writes | |
593 @findex sc-header-attributed-writes | |
594 @findex header-attributed-writes (sc-) | |
595 @code{>>>>> "@var{sc-attribution}" == @var{sc-author} <@var{sc-reply-address}> writes:} | |
596 | |
597 @item sc-header-author-writes | |
598 @findex sc-header-author-writes | |
599 @findex header-author-writes (sc-) | |
600 @code{>>>>> @var{sc-author} writes:} | |
601 | |
602 @item sc-header-verbose | |
603 @findex sc-header-verbose | |
604 @findex header-verbose (sc-) | |
605 @code{>>>>> On @var{date},}@* | |
606 @code{>>>>> @var{sc-author}}@* | |
607 @code{>>>>> from the organization of @var{organization}}@* | |
608 @code{>>>>> who can be reached at:@: @var{sc-reply-address}}@* | |
609 @code{>>>>> (whose comments are cited below with:@: "@var{sc-cite}")}@* | |
610 @code{>>>>> had this to say in article @var{message-id}}@* | |
611 @code{>>>>> in newsgroups @var{newsgroups}}@* | |
612 @code{>>>>> concerning the subject of @var{subject}}@* | |
613 @code{>>>>> see @var{references} for more details} | |
614 @end table | |
615 | |
616 @node Electric References, Hints to MUA Authors, The Built-in Header Rewrite Functions, Reference Headers | |
617 @cindex electric references | |
618 @section Electric References | |
619 | |
620 By default, when Supercite cites the original message for the first | |
621 time, it just goes ahead and inserts the reference header indexed by | |
622 @code{sc-preferred-header-style}. However, you may want to select | |
623 different reference headers based on the type of reply or forwarding you | |
624 are doing. You may also want to preview the reference header before | |
625 deciding whether to insert it into the reply buffer or not. Supercite | |
626 provides an optional @dfn{electric reference} mode which you can drop | |
627 into to give you this functionality. | |
628 | |
629 @vindex sc-electric-references-p | |
630 @vindex electric-references-p (sc-) | |
631 If the variable @code{sc-electric-references-p} is non-@code{nil}, | |
632 Supercite will bring up an electric reference mode buffer and place you | |
633 into a recursive edit. The electric reference buffer is read-only, so | |
634 you cannot directly modify the reference text until you exit electric | |
635 references and insert the text into the reply buffer. But you can cycle | |
636 through all the reference header rewrite functions in your | |
637 @code{sc-rewrite-header-list}. | |
638 | |
639 You can also set a new preferred header style, jump to any header, or | |
640 jump to the preferred header. The header will be shown in the electric | |
641 reference buffer and the header index and function name will appear in | |
642 the echo area. | |
643 | |
644 The following commands are available while in electric reference mode | |
645 (shown here with their default key bindings): | |
646 | |
647 @table @asis | |
648 @item @code{sc-eref-next} (@kbd{n}) | |
649 @findex sc-eref-next | |
650 @findex eref-next (sc-) | |
651 @kindex n | |
652 @vindex sc-electric-circular-p | |
653 @vindex electric-circular-p (sc-) | |
654 Displays the next reference header in the electric reference buffer. If | |
655 the variable @code{sc-electric-circular-p} is non-@code{nil}, invoking | |
656 @code{sc-eref-next} while viewing the last reference header in the list | |
657 will wrap around to the first header.@refill | |
658 | |
659 @item @code{sc-eref-prev} (@kbd{p}) | |
660 @findex sc-eref-prev | |
661 @findex eref-prev (sc-) | |
662 @kindex p | |
663 Displays the previous reference header in the electric reference buffer. | |
664 If the variable @code{sc-electric-circular-p} is non-@code{nil}, | |
665 invoking @code{sc-eref-prev} will wrap around to the last header.@refill | |
666 | |
667 @item @code{sc-eref-goto} (@kbd{g}) | |
668 @findex sc-eref-goto | |
669 @findex eref-goto (sc-) | |
670 @kindex g | |
671 Goes to a specified reference header. The index (into the | |
672 @code{sc-rewrite-header-list}) can be specified as a numeric argument to | |
673 the command. Otherwise, Supercite will query you for the index in the | |
674 minibuffer.@refill | |
675 | |
676 @item @code{sc-eref-jump} (@kbd{j}) | |
677 @findex sc-eref-jump | |
678 @findex eref-jump (sc-) | |
679 @kindex j | |
680 Display the preferred reference header, i.e., the one indexed by the current | |
681 value of @code{sc-preferred-header-style}. | |
682 | |
683 @item @code{sc-eref-setn} (@kbd{s}) | |
684 @findex sc-eref-setn | |
685 @findex eref-setn (sc-) | |
686 @kindex s | |
687 Set the preferred reference header (i.e., | |
688 @code{sc-preferred-header-style}) to the currently displayed header.@refill | |
689 | |
690 @item @code{sc-eref-exit} (@kbd{C-j}, @key{RET}, and @key{ESC C-c}) | |
691 @kindex RET | |
692 @kindex C-j | |
693 @kindex q | |
694 @findex sc-eref-exit | |
695 @findex eref-exit (sc-) | |
696 Exit from electric reference mode and insert the current header into the | |
697 reply buffer.@refill | |
698 | |
699 @item @code{sc-eref-abort} (@kbd{q}, @kbd{x}) | |
700 @findex sc-eref-abort | |
701 @findex eref-abort (sc-) | |
702 @kindex x | |
703 Exit from electric reference mode without inserting the current header. | |
704 @end table | |
705 | |
706 @vindex sc-electric-mode-hook | |
707 @vindex electric-mode-hook (sc-) | |
708 @noindent | |
709 Supercite will execute the hook @code{sc-electric-mode-hook} before | |
710 entering electric reference mode. | |
711 | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
712 @node Getting Connected, Replying and Yanking, Recognizing Citations, Top |
84313 | 713 @cindex citation interface specification |
714 @chapter Getting Connected | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
715 |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
716 |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
717 @vindex mail-citation-hook |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
718 @cindex .emacs file |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
719 In most cases, all that is necessary to begin using Supercite is to add |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
720 the following to @file{~.emacs}: |
84313 | 721 |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
722 @example |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
723 (add-hook 'mail-citation-hook 'sc-cite-original) |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
724 @end example |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
725 |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
726 @noindent For more details of the process, read on@dots{} |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
727 |
84313 | 728 Hitting @kbd{C-c C-y} in your MUA's reply buffer yanks and cites the |
729 original message into the reply buffer. In reality, the citation of the | |
730 original message is performed via a call through a configurable hook | |
731 variable. The name of this variable has been agreed to in advance as | |
732 part of the @dfn{citation interface specification}. By default this | |
733 hook variable has a @code{nil} value, which the MUA recognizes to mean, | |
734 ``use your default citation function.'' When you add Supercite's | |
735 citation function to the hook, thereby giving the variable a | |
736 non-@code{nil} value, it tells the MUA to run the hook via | |
737 @code{run-hooks} instead of using the default citation.@refill | |
738 | |
739 Early in Supercite's development, the Supercite author, a few MUA | |
740 authors, and some early Supercite users got together and agreed upon a | |
741 standard interface between MUAs and citation packages (of which | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
742 Supercite is currently the only known add-on @t{:-)}. Supercite can |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
743 probably be used with most Emacs MUAs, with a greater or lesser degree |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
744 of effort. |
84313 | 745 |
746 To learn exactly how to connect Supercite to the software systems you | |
747 are using, read the appropriate following sections. For details on the | |
748 interface specifications, or if you are writing or maintaining an MUA, | |
749 @pxref{Hints to MUA Authors}. | |
750 | |
751 @cindex autoload | |
752 @cindex .emacs file | |
753 @findex sc-cite-original | |
754 @findex cite-original (sc-) | |
755 @findex sc-submit-bug-report | |
756 @findex submit-bug-report (sc-) | |
757 The first thing that everyone should do, regardless of the MUA you are | |
758 using is to set up Emacs so it will load Supercite at the appropriate | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
759 time. This happens automatically if Supercite is distributed with your |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
760 Emacs version. If not, you can set up an @dfn{autoload} for Supercite. |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
761 |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
762 To do the latter, put the following in your @file{.emacs} file: |
84313 | 763 |
764 @example | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
765 (autoload 'sc-cite-original "supercite" nil t) |
84313 | 766 @end example |
767 | |
768 @cindex point | |
769 @cindex mark | |
770 The function @code{sc-cite-original} is the top-level Supercite function | |
771 designed to be run from the citation hook. It expects | |
772 @samp{point} and @samp{mark} to be set around the region to cite, and it | |
773 expects the original article's mail headers to be present within this | |
774 region. Note that Supercite @emph{never} touches any text outside this | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
775 region. Note further that the region need not be active |
84313 | 776 for @code{sc-cite-original} to do its job. |
777 @xref{Hints to MUA Authors}.@refill | |
778 | |
779 The other step in the getting connected process is to make sure your | |
780 MUA calls @code{sc-cite-original} at the right time. As mentioned | |
781 above, some MUAs handle this differently. Read the sections that follow | |
782 pertaining to the MUAs you are using. | |
783 | |
784 @vindex sc-load-hook | |
785 @vindex load-hook (sc-) | |
786 @vindex sc-pre-hook | |
787 @vindex pre-hook (sc-) | |
788 One final note. After Supercite is loaded into your Emacs session, it | |
789 runs the hook @code{sc-load-hook}. You can put any customizations into | |
790 this hook since it is only run once. This will not work, however, if | |
791 your Emacs maintainer has put Supercite into your dumped Emacs' image. | |
792 In that case, you can use the @code{sc-pre-hook} variable, but this will | |
793 get executed every time @code{sc-cite-original} is called. @xref{Reply | |
794 Buffer Initialization}.@refill | |
795 | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
796 @node Replying and Yanking, Reply Buffer Initialization, Getting Connected, Top |
84313 | 797 @chapter Replying and Yanking |
798 @ifinfo | |
799 | |
800 This chapter explains what happens when you reply and yank an original | |
801 message from an MUA. | |
802 | |
803 @menu | |
804 * Reply Buffer Initialization:: | |
805 * Filling Cited Text:: | |
806 @end menu | |
807 @end ifinfo | |
808 @node Reply Buffer Initialization, Filling Cited Text, Replying and Yanking, Replying and Yanking | |
809 @findex sc-cite-original | |
810 @findex cite-original (sc-) | |
811 @section Reply Buffer Initialization | |
812 | |
813 Executing @code{sc-cite-original} performs the following steps as it | |
814 initializes the reply buffer: | |
815 | |
816 @enumerate | |
817 @item | |
818 @vindex sc-pre-hook | |
819 @vindex pre-hook (sc-) | |
820 @emph{Runs @code{sc-pre-hook}.} | |
821 This hook variable is run before @code{sc-cite-original} does any other | |
822 work. You could conceivably use this hook to set certain Supercite | |
823 variables based on the reply buffer's mode or name (i.e., to do | |
824 something different based on whether you are replying or following up to | |
825 an article).@refill | |
826 | |
827 @item | |
828 @emph{Inserts Supercite's keymap.} | |
829 @vindex sc-mode-map-prefix | |
830 @vindex mode-map-prefix (sc-) | |
831 @kindex C-c C-p | |
832 @cindex keymap prefix | |
833 Supercite provides a number of commands for performing post-yank | |
834 modifications to the reply buffer. These commands are installed on | |
835 Supercite's top-level keymap. Since Supercite has to interface with a | |
836 wide variety of MUAs, it does not install all of its commands directly | |
837 into the reply buffer's keymap. Instead, it puts its commands on a | |
838 keymap prefix, then installs this prefix onto the buffer's keymap. What | |
839 this means is that you typically have to type more characters to invoke | |
840 a Supercite command, but Supercite's key bindings can be made much more | |
841 consistent across MUAs. | |
842 | |
843 You can control what key Supercite uses as its keymap prefix by changing | |
844 the variable @code{sc-mode-map-prefix}. By default, this variable is | |
845 set to @code{C-c C-p}; a finger twister perhaps, but unfortunately the | |
846 best default due to the scarcity of available key bindings in many MUAs. | |
847 | |
848 @item | |
849 @emph{Turns on Supercite minor mode.} | |
850 @cindex modeline | |
851 The modeline of the reply buffer should indicate that Supercite is | |
852 active in that buffer by displaying the string @samp{SC}. | |
853 | |
854 @item | |
855 @emph{Sets the ``Undo Boundary.''} | |
856 @cindex undo boundary | |
857 Supercite sets an undo boundary before it begins to modify the original | |
858 yanked text. This allows you to easily undo Supercite's changes to | |
859 affect alternative citing styles. | |
860 | |
861 @item | |
862 @emph{Processes the mail headers.} | |
863 @vindex sc-confirm-always-p | |
864 @vindex confirm-always-p (sc-) | |
865 @vindex sc-mail-warn-if-non-rfc822-p | |
866 @vindex mail-warn-if-non-rfc822-p (sc-) | |
867 All previously retrieved info key-value pairs are deleted from the info | |
868 alist, then the mail headers in the body of the yanked message are | |
869 scanned. Info key-value pairs are created for each header found. Also, | |
870 such useful information as the author's name and email address are | |
871 extracted. If the variable @code{sc-mail-warn-if-non-rfc822-p} is | |
872 non-@code{nil}, then Supercite will warn you if it finds a mail header | |
873 that does not conform to RFC822. This is rare and indicates a problem | |
874 either with your MUA or the original author's MUA, or some MTA (mail | |
875 transport agent) along the way. | |
876 | |
877 @vindex sc-nuke-mail-headers | |
878 @vindex sc-nuke-mail-header-list | |
879 @vindex nuke-mail-headers (sc-) | |
880 @vindex nuke-mail-header-list (sc-) | |
881 Once the info keys have been extracted from the mail headers, the | |
882 headers are nuked from the reply buffer. You can control exactly which | |
883 headers are removed or kept, but by default, all headers are removed. | |
884 | |
885 There are two variables which control mail header nuking. The variable | |
886 @code{sc-nuke-mail-headers} controls the overall behavior of the header | |
887 nuking routines. By setting this variable to @code{'all}, you | |
888 automatically nuke all mail headers. Likewise, setting this variable to | |
889 @code{'none} inhibits nuking of any mail headers. In between these | |
890 extremes, you can tell Supercite to nuke only a specified list of mail | |
891 headers by setting this variable to @code{'specified}, or to keep only a | |
892 specified list of headers by setting it to @code{'keep}. | |
893 | |
894 If @code{sc-nuke-mail-headers} is set to @code{'specified} or | |
895 @code{'keep}, then the variable @code{sc-nuke-mail-header-list} is | |
896 consulted for the list of headers to nuke or keep. This variable | |
897 contains a list of regular expressions. If the mail header line matches | |
898 a regular expression in this list, the header will be nuked or kept. | |
899 The line is matched against the regexp using @code{looking-at} rooted at | |
900 the beginning of the line. | |
901 | |
902 @vindex sc-blank-lines-after-headers | |
903 @vindex blank-lines-after-headers (sc-) | |
904 If the variable @code{sc-blank-lines-after-headers} is non-@code{nil}, | |
905 it contains the number of blank lines remaining in the buffer after mail | |
906 headers are nuked. By default, only one blank line is left in the buffer. | |
907 | |
908 @item | |
909 @emph{Selects the attribution and citation strings.} | |
910 Once the mail headers have been processed, Supercite selects a | |
911 attribution string and a citation string which it will use to cite the | |
912 original message. @xref{Selecting an Attribution}, for details. | |
913 | |
914 @item | |
915 @emph{Cites the message body.} | |
916 @vindex sc-cite-region-limit | |
917 @vindex cite-region-limit (sc-)b | |
918 After the selection of the attribution and citation strings, Supercite | |
919 cites the original message by inserting the citation string prefix in | |
920 front of every uncited line. You may not want Supercite to | |
921 automatically cite very long messages however. For example, some email | |
922 could contain a smaller header section followed by a huge uuencoded | |
923 message. It wouldn't make sense to cite the uuencoded message part when | |
924 responding to the original author's short preface. For this reason, | |
925 Supercite provides a variable which limits the automatic citation of | |
926 long messages to a certain maximum number of lines. The variable is | |
927 called @code{sc-cite-region-limit}. If this variable contains an | |
928 integer, messages with more lines that this will not be cited at all, | |
929 and a warning message will be displayed. Supercite has performed | |
930 everything necessary, though, for you to manually cite only the small | |
931 portion of the original message that you want to use. | |
932 | |
933 If @code{sc-cite-region-limit} contains a non-@code{nil} value, the | |
934 original message will always be cited, regardless of its size. If the | |
935 variable contains the value @code{nil}, the region will never be cited | |
936 automatically. Use this if you always want to be able to edit and cite | |
937 the message manually. | |
938 | |
939 @vindex sc-cite-blank-lines-p | |
940 @vindex cite-blank-lines-p (sc-) | |
941 The variable @code{sc-cite-blank-lines-p} controls whether blank lines | |
942 in the original message should be cited or not. If this variable is | |
943 non-@code{nil}, blank lines will be cited just like non-blank lines. | |
944 Otherwise, blank lines will be treated as paragraph separators. | |
945 | |
946 Citing of the original message is highly configurable. Supercite's | |
947 default setup does a pretty good job of citing many common forms of | |
948 previously cited messages. But there are as many citation styles out | |
949 there as people on the net, or just about! It would be impossible for | |
950 Supercite to anticipate every style in existence, and you probably | |
951 wouldn't encounter them all anyway. But you can configure Supercite to | |
952 recognize those styles you see often. | |
953 @xref{Configuring the Citation Engine}, for details.@refill | |
954 | |
955 @item | |
956 @emph{Runs @code{sc-post-hook}.} | |
957 @vindex sc-post-hook | |
958 @vindex post-hook (sc-) | |
959 This variable is very similar to @code{sc-pre-hook}, except that it runs | |
960 after @code{sc-cite-original} is finished. This hook is provided mostly | |
961 for completeness and backward compatibility. Perhaps it could be used to | |
962 reset certain variables set in @code{sc-pre-hook}.@refill | |
963 @end enumerate | |
964 | |
965 @node Filling Cited Text, Selecting an Attribution, Reply Buffer Initialization, Replying and Yanking | |
966 @cindex filling paragraphs | |
967 @vindex sc-auto-fill-region-p | |
968 @vindex auto-fill-region-p (sc-) | |
969 @cindex filladapt | |
970 @cindex gin-mode | |
971 @findex sc-setup-filladapt | |
972 @findex setup-filladapt (sc-) | |
973 @vindex sc-load-hook | |
974 @vindex load-hook (sc-) | |
975 @section Filling Cited Text | |
976 | |
977 Supercite will automatically fill newly cited text from the original | |
978 message unless the variable @code{sc-auto-fill-region-p} has a | |
979 @code{nil} value. Supercite will also re-fill paragraphs when you | |
980 manually cite or re-cite text. | |
981 | |
982 However, during normal editing, Supercite itself cannot be used to fill | |
983 paragraphs. This is a change from version 2. There are other add-on | |
984 lisp packages which do filling much better than Supercite ever did. The | |
985 two best known are @dfn{filladapt} and @dfn{gin-mode}. Both work well | |
986 with Supercite and both are available at the normal Emacs Lisp archive | |
987 sites. @dfn{gin-mode} works pretty well out of the box, but if you use | |
988 @dfn{filladapt}, you may want to run the function | |
989 @code{sc-setup-filladapt} from your @code{sc-load-hook}. This simply | |
990 makes @dfn{filladapt} a little more Supercite savvy than its default | |
991 setup. | |
992 | |
993 @vindex sc-fixup-whitespace-p | |
994 @vindex fixup-whitespace-p (sc-) | |
995 Also, Supercite will collapse leading whitespace between the citation | |
996 string and the text on a line when the variable | |
997 @code{sc-fixup-whitespace-p} is non-@code{nil}. The default value for | |
998 this variable is @code{nil}.@refill | |
999 | |
1000 @vindex fill-prefix | |
1001 Its important to understand that Supercite's automatic filling (during | |
1002 the initial citation of the reply) is very fragile. That is because | |
1003 figuring out the @code{fill-prefix} for a particular paragraph is a | |
1004 really hard thing to do automatically. This is especially the case when | |
1005 the original message contains code or some other text where leading | |
1006 whitespace is important to preserve. For this reason, many Supercite | |
1007 users typically run with @code{sc-auto-fill-region-p} (and possibly also | |
1008 @code{sc-fixup-whitespace-p}) set to @code{nil}. They then manually | |
1009 fill each cited paragraph in the reply buffer. | |
1010 | |
1011 I usually run with both these variables containing their default values. | |
1012 When Supercite's automatic filling breaks on a particular message, I | |
1013 will use Emacs' undo feature to undo back before the citation was | |
1014 applied to the original message. Then I'll toggle the variables and | |
1015 manually cite those paragraphs that I don't want to fill or collapse | |
1016 whitespace on. @xref{Variable Toggling Shortcuts}.@refill | |
1017 | |
1018 @kindex C-c C-p C-p | |
1019 If you find that Supercite's automatic filling is just too fragile for | |
1020 your tastes, you might consider one of these alternate approaches. | |
1021 Also, to make life easier, a shortcut function to toggle the state of | |
1022 both of these variables is provided on the key binding | |
1023 @kbd{C-c C-p C-p} (with the default value of @code{sc-mode-map-prefix}; | |
1024 @pxref{Post-yank Formatting Commands}).@refill | |
1025 | |
1026 You will noticed that the minor mode string will | |
1027 show the state of these variables as qualifier characters. When both | |
1028 variables are @code{nil}, the Supercite minor mode string will display | |
1029 @samp{SC}. When just @code{sc-auto-fill-region-p} is non-@code{nil}, the | |
1030 string will display @samp{SC:f}, and when just | |
1031 @code{sc-fixup-whitespace-p} is non-@code{nil}, the string will display | |
1032 @samp{SC:w}. When both variables are non-@code{nil}, the string will | |
1033 display @samp{SC:fw}. Note that the qualifiers chosen are mnemonics for | |
1034 the default bindings of the toggling function for each respective | |
1035 variable. | |
1036 @xref{Variable Toggling Shortcuts}.@refill | |
1037 | |
1038 Why are these variables not set to @code{nil} by default? It is because | |
1039 many users won't manually fill paragraphs that are Supercited, and there | |
1040 have been widespread complaints on the net about mail and news messages | |
1041 containing lines greater than about 72 characters. So the default is to | |
1042 fill cited text. | |
1043 | |
1044 @node Selecting an Attribution, Attribution Preferences, Filling Cited Text, Top | |
1045 @cindex attribution list | |
1046 @vindex sc-preferred-attribution-list | |
1047 @vindex preferred-attribution-list (sc-) | |
1048 @chapter Selecting an Attribution | |
1049 | |
1050 As you know, the attribution string is the part of the author's name | |
1051 that will be used to composed a non-nested citation string. Supercite | |
1052 scans the various mail headers present in the original article and uses | |
1053 a number of heuristics to extract strings which it puts into the | |
1054 @dfn{attribution association list} or @dfn{attribution alist}. This is | |
1055 analogous, but different than, the info alist previously mentioned. Each | |
1056 element in the attribution alist is a key-value pair containing such | |
1057 information as the author's first name, middle names, and last name, the | |
1058 author's initials, and the author's email terminus. | |
1059 | |
1060 @ifinfo | |
1061 @menu | |
1062 * Attribution Preferences:: | |
1063 * Anonymous Attributions:: | |
1064 * Author Names:: | |
1065 @end menu | |
1066 @end ifinfo | |
1067 | |
1068 @node Attribution Preferences, Anonymous Attributions, Selecting an Attribution, Selecting an Attribution | |
1069 @section Attribution Preferences | |
1070 | |
1071 When you cite an original message, you can tell Supercite which part of | |
1072 the author's name you would prefer it to use as the attribution. The | |
1073 variable @code{sc-preferred-attribution-list} controls this; it contains | |
1074 keys which are matched against the attribution alist in the given order. | |
1075 The first value of a key that produces a non-@code{nil}, non-empty | |
1076 string match is used as the attribution string, and if no keys match, a | |
1077 secondary mechanism is used to generate the attribution. | |
1078 @xref{Anonymous Attributions}. | |
1079 | |
1080 The following preferences are always available in the attribution alist | |
1081 (barring error): | |
1082 | |
1083 @table @code | |
1084 @item "emailname" | |
1085 the author's email terminus. | |
1086 | |
1087 @item "initials" | |
1088 the author's initials. | |
1089 | |
1090 @item "firstname" | |
1091 the author's first name. | |
1092 | |
1093 @item "lastname" | |
1094 the author's last name. | |
1095 | |
1096 @item "middlename-1" | |
1097 the author's first middle name. | |
1098 | |
1099 @item "sc-lastchoice" | |
1100 the last attribution string you have selected. This is useful when you | |
1101 recite paragraphs in the reply.@refill | |
1102 | |
1103 @item "sc-consult" | |
1104 @vindex sc-attrib-selection-list | |
1105 @vindex attrib-selection-list (sc-) | |
1106 consults the customizable list @code{sc-attrib-selection-list} which can | |
1107 be used to select special attributions based on the value of any info | |
1108 key. See below for details. | |
1109 | |
1110 @item "x-attribution" | |
1111 the original author's suggestion for attribution string choice. See below | |
1112 for details.@refill | |
1113 @end table | |
1114 | |
1115 Middle name indexes can be any positive integer greater than zero, | |
1116 though it is unlikely that many authors will have more than one middle | |
1117 name, if that many. | |
1118 | |
1119 At this point, let me digress into a discussion of etiquette. It is my | |
1120 belief that while the style of the citations is a reflection of the | |
1121 personal tastes of the replier (i.e., you), the attribution selection is | |
1122 ultimately the personal choice of the original author. In a sense it is | |
1123 his or her ``net nickname'', and therefore the author should have some | |
1124 say in the selection of attribution string. Imagine how you would feel | |
1125 if someone gave you a nickname that you didn't like? | |
1126 | |
1127 For this reason, Supercite recognizes a special mail header, | |
1128 @samp{X-Attribution:}, which if present, tells Supercite the attribution | |
1129 string preferred by the original author. It is the value of this header | |
1130 that is associated with the @code{"x-attribution"} key in the | |
1131 attribution alist. Currently, you can override the preference of this | |
1132 key by changing @code{sc-preferred-attribution-list}, but that isn't | |
1133 polite, and in the future Supercite may hard-code this. For now, it is | |
1134 suggested that if you change the order of the keys in this list, that | |
1135 @code{"x-attribution"} always be first, or possible second behind only | |
1136 @code{"sc-lastchoice"}. This latter is the default. | |
1137 | |
1138 @vindex sc-attrib-selection-list | |
1139 @vindex attrib-selection-list (sc-) | |
1140 The value @code{"sc-consult"} in @code{sc-preferred-attribution-list} | |
1141 has a special meaning during attribution selection. When Supercite | |
1142 encounters this preference, it begins processing a customizable list of | |
1143 attributions, contained in the variable @code{sc-attrib-selection-list}. | |
1144 Each element in this list contains lists of the following form: | |
1145 | |
1146 @example | |
1147 @group | |
1148 (@var{infokey} ((@var{regexp} @. @var{attribution}) | |
1149 (@var{regexp} @. @var{attribution}) | |
1150 (@dots{}))) | |
1151 @end group | |
1152 @end example | |
1153 | |
1154 @noindent | |
1155 @findex sc-mail-field | |
1156 @findex mail-field (sc-) | |
1157 where @var{infokey} is a key for @code{sc-mail-field} and @var{regexp} | |
1158 is a regular expression to match against the @var{infokey}'s value. If | |
1159 @var{regexp} matches the @var{infokey}'s value, the @var{attribution} is | |
1160 used as the attribution string. Actually, @var{attribution} can be a | |
1161 string or a list; if it is a list, it is @code{eval}uated and the return | |
1162 value (which must be a string), is used as the attribution. | |
1163 | |
1164 This can be very useful for when you are replying to net acquaintances | |
1165 who do not use the @samp{X-Attribution:@:} mail header. You may know | |
1166 what nickname they would prefer to use, and you can set up this list to | |
1167 match against a specific mail field, e.g., @samp{From:@:}, allowing you | |
1168 to cite your friend's message with the appropriate attribution. | |
1169 | |
1170 @node Anonymous Attributions, Author Names, Attribution Preferences, Selecting an Attribution | |
1171 @vindex sc-default-author-name | |
1172 @vindex default-author-name (sc-) | |
1173 @vindex sc-default-attribution | |
1174 @vindex default-attribution (sc-) | |
1175 @section Anonymous Attributions | |
1176 | |
1177 When the author's name cannot be found in the @samp{From:@:} mail | |
1178 header, a fallback author name and attribution string must be supplied. | |
1179 The fallback author name is contained in the variable | |
1180 @code{sc-default-author-name} and the fallback attribution string is | |
1181 contained in the variable @code{sc-default-attribution}. Default values | |
1182 for these variables are @code{"Anonymous"} and @code{"Anon"}, | |
1183 respectively. Note that in most circumstances, getting the default | |
1184 author name or attribution is a sign that something is set up | |
1185 incorrectly. | |
1186 | |
1187 @vindex sc-use-only-preference-p | |
1188 @vindex use-only-preference-p (sc-) | |
1189 Also, if the preferred attribution, which you specified in your | |
1190 @code{sc-preferred-attribution-list} variable cannot be found, a | |
1191 secondary method can be employed to find a valid attribution string. The | |
1192 variable @code{sc-use-only-preference-p} controls what happens in this | |
1193 case. If the variable's value is non-@code{nil}, then | |
1194 @code{sc-default-author-name} and @code{sc-default-attribution} are | |
1195 used, otherwise, the following steps are taken to find a valid | |
1196 attribution string, and the first step to return a non-@code{nil}, | |
1197 non-empty string becomes the attribution:@refill | |
1198 | |
1199 @enumerate | |
1200 @item | |
1201 Use the last selected attribution, if there is one. | |
1202 | |
1203 @item | |
1204 Use the value of the @code{"x-attribution"} key. | |
1205 | |
1206 @item | |
1207 Use the author's first name. | |
1208 | |
1209 @item | |
1210 Use the author's last name. | |
1211 | |
1212 @item | |
1213 Use the author's initials. | |
1214 | |
1215 @item | |
1216 Find the first non-@code{nil}, non-empty attribution string in the | |
1217 attribution alist. | |
1218 | |
1219 @item | |
1220 @code{sc-default-attribution} is used. | |
1221 @end enumerate | |
1222 | |
1223 @vindex sc-confirm-always-p | |
1224 @vindex confirm-always-p (sc-) | |
1225 Once the attribution string has been automatically selected, a number of | |
1226 things can happen. If the variable @code{sc-confirm-always-p} is | |
1227 non-@code{nil}, you are queried for confirmation of the chosen | |
1228 attribution string. The possible values for completion are those strings | |
1229 in the attribution alist, however you are not limited to these choices. | |
1230 You can type any arbitrary string at the confirmation prompt. The string | |
1231 you enter becomes the value associated with the @code{"sc-lastchoice"} | |
1232 key in the attribution alist. | |
1233 | |
1234 @vindex sc-downcase-p | |
1235 @vindex downcase-p (sc-) | |
1236 Once an attribution string has been selected, Supercite will force the | |
1237 string to lower case if the variable @code{sc-downcase-p} is | |
1238 non-@code{nil}. | |
1239 | |
1240 @vindex sc-attribs-preselect-hook | |
1241 @vindex attribs-preselect-hook (sc-) | |
1242 @vindex sc-attribs-postselect-hook | |
1243 @vindex attribs-postselect-hook (sc-) | |
1244 | |
1245 Two hook variables provide even greater control of the attribution | |
1246 selection process. The hook @code{sc-attribs-preselect-hook} is run | |
1247 before any attribution is selected. Likewise, the hook | |
1248 @code{sc-attribs-postselect-hook} is run after the attribution is | |
1249 selected (and the corresponding citation string is built), but before | |
1250 these values are committed for use by Supercite. During the | |
1251 post-selection hook, the local variables @code{attribution} and | |
1252 @code{citation} are bound to the appropriate strings. By changing these | |
1253 variables in your hook functions, you change the attribution and | |
1254 citation strings used by Supercite. One possible use of this would be | |
1255 to override any automatically derived attribution string when it is only | |
1256 one character long; e.g. you prefer to use @code{"initials"} but the | |
1257 author only has one name.@refill | |
1258 | |
1259 @node Author Names, Configuring the Citation Engine, Anonymous Attributions, Selecting an Attribution | |
1260 @cindex author names | |
1261 @section Author Names | |
1262 | |
1263 Supercite employs a number of heuristics to decipher the author's name | |
1264 based on value of the @samp{From:@:} mail field of the original message. | |
1265 Supercite can recognize almost all of the common @samp{From:@:} field | |
1266 formats in use. If you encounter a @samp{From:@:} field that Supercite | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1267 cannot parse, please report this bug using @kbd{M-x report-emacs-bug}. |
84313 | 1268 |
1269 @vindex sc-titlecue-regexp | |
1270 @vindex titlecue-regexp (sc-) | |
1271 There are a number of Supercite variables that control how author names | |
1272 are extracted from the @samp{From:@:} header. Some headers may contain a | |
1273 descriptive title as in: | |
1274 | |
1275 @example | |
1276 From:@: computer!speedy!doe (John Xavier-Doe -- Decent Hacker) | |
1277 @end example | |
1278 | |
1279 Supercite knows which part of the @samp{From:@:} header is email address | |
1280 and which part is author name, but in this case the string @code{"Decent | |
1281 Hacker"} is not part of the author's name. You can tell Supercite to | |
1282 ignore the title, while still recognizing hyphenated names through the | |
1283 use of a regular expression in the variable @code{sc-titlecue-regexp}. | |
1284 This variable has the default value of @code{"\\\\s +-+\\\\s +"}. Any | |
1285 text after this regexp is encountered is ignored as noise. | |
1286 | |
1287 @vindex sc-name-filter-alist | |
1288 @vindex name-filter-alist (sc-) | |
1289 Some @samp{From:@:} headers may contain extra titles in the name fields | |
1290 not separated by a title cue, but which are nonetheless not part of the | |
1291 author's name proper. Examples include the titles ``Dr.'', ``Mr.'', | |
1292 ``Ms.'', ``Jr.'', ``Sr.'', and ``III'' (e.g., Thurston Howe, the Third). | |
1293 Also, some companies prepend or append the name of the division, | |
1294 organization, or project on the author's name. All of these titles are | |
1295 noise which should be ignored. The variable @code{sc-name-filter-alist} | |
1296 is used for this purpose. As implied by its name, this variable is an | |
1297 association list, where each element is a cons cell of the form: | |
1298 | |
1299 @example | |
1300 (@var{regexp} @. @var{position}) | |
1301 @end example | |
1302 | |
1303 @noindent | |
1304 where @var{regexp} is a regular expression that is matched (using | |
1305 @code{string-match}) against each element of the @samp{From:@:} field's | |
1306 author name. @var{position} is a position indicator, starting at zero. | |
1307 Thus to strip out all titles of ``Dr.'', ``Mr.'', etc. from the name, | |
1308 @code{sc-name-filter-alist} would have an entry such as: | |
1309 | |
1310 @example | |
1311 ("^\\(Mr\\|Mrs\\|Ms\\|Dr\\)[.]?$" @. 0) | |
1312 @end example | |
1313 | |
1314 @noindent | |
1315 which only removes them if they appear as the first word in the name. | |
1316 The position indicator is an integer, or one of the two special symbols | |
1317 @code{last} or @code{any}. @code{last} always matches against the last | |
1318 word in the name field, while @code{any} matches against every word in | |
1319 the name field. | |
1320 | |
1321 @node Configuring the Citation Engine, Using Regi, Author Names, Top | |
1322 @cindex Regi | |
1323 @cindex frames (Regi) | |
1324 @cindex entries (Regi) | |
1325 @chapter Configuring the Citation Engine | |
1326 | |
1327 At the heart of Supercite is a regular expression interpreting engine | |
1328 called @dfn{Regi}. Regi operates by interpreting a data structure | |
1329 called a Regi-frame (or just @dfn{frame}), which is a list of | |
1330 Regi-entries (or just @dfn{entry}). Each entry contains a predicate, | |
1331 typically a regular expression, which is matched against a line of text | |
1332 in the current buffer. If the predicate matches true, an associated | |
1333 expression is @code{eval}uated. In this way, an entire region of text | |
1334 can be transformed in an @emph{awk}-like manner. Regi is used | |
1335 throughout Supercite, from mail header information extraction, to header | |
1336 nuking, to citing text. | |
1337 | |
1338 @ifinfo | |
1339 @menu | |
1340 * Using Regi:: | |
1341 * Frames You Can Customize:: | |
1342 @end menu | |
1343 @end ifinfo | |
1344 | |
1345 While the details of Regi are discussed below (@pxref{Using Regi}), only | |
1346 those who wish to customize certain aspects of Supercite need concern | |
1347 themselves with it. It is important to understand though, that any | |
1348 conceivable citation style that can be described by a regular expression | |
1349 can be recognized by Supercite. This leads to some interesting | |
1350 applications. For example, if you regularly receive email from a | |
1351 co-worker that uses an uncommon citation style (say one that employs a | |
1352 @samp{|} or @samp{@}} character at the front of the line), it is | |
1353 possible for Supercite to recognize this and @emph{coerce} the citation | |
1354 to your preferred style, for consistency. In theory, it is possible for | |
1355 Supercite to recognize such things as uuencoded messages or C code and | |
1356 cite or fill those differently than normal text. None of this is | |
1357 currently part of Supercite, but contributions are welcome! | |
1358 | |
1359 @node Using Regi, Frames You Can Customize, Configuring the Citation Engine, Configuring the Citation Engine | |
1360 @findex regi-interpret | |
1361 @findex eval | |
1362 @findex looking-at | |
1363 @section Using Regi | |
1364 | |
1365 Regi works by interpreting frames with the function | |
1366 @code{regi-interpret}. A frame is a list of arbitrary size where each | |
1367 element is a entry of the following form: | |
1368 | |
1369 @example | |
1370 (@var{pred} @var{func} [@var{negate-p} [@var{case-fold-search}]]) | |
1371 @end example | |
1372 | |
1373 Regi starts with the first entry in a frame, evaluating the @var{pred} | |
1374 of that entry against the beginning of the line that @samp{point} is on. | |
1375 If the @var{pred} evaluates to true (or false if the optional | |
1376 @var{negate-p} is non-@code{nil}), then the @var{func} for that entry is | |
1377 @code{eval}uated. How processing continues is determined by the return | |
1378 value for @var{func}, and is described below. If @var{pred} was false | |
1379 the next entry in the frame is checked until all entries have been | |
1380 matched against the current line. If no entry matches, @samp{point} is | |
1381 moved forward one line and the frame is reset to the first entry. | |
1382 | |
1383 @var{pred} can be a string, a variable, a list or one of the following | |
1384 symbols: @code{t}, @code{begin}, @code{end}, or @code{every}. If | |
1385 @var{pred} is a string, or a variable or list that @code{eval}uates to a | |
1386 string, it is interpreted as a regular expression. This regexp is | |
1387 matched against the current line, from the beginning, using | |
1388 @code{looking-at}. This match folds case if the optional | |
1389 @var{case-fold-search} is non-@code{nil}. If @var{pred} is not a | |
1390 string, or does not @code{eval}uate to a string, it is interpreted as a | |
1391 binary value (@code{nil} or non-@code{nil}).@refill | |
1392 | |
1393 The four special symbol values for @var{pred} are recognized: | |
1394 | |
1395 @table @code | |
1396 @item t | |
1397 Always produces a true outcome. | |
1398 @item begin | |
1399 Always executed before the frame is interpreted. This can be used to | |
1400 initialize some global variables for example. | |
1401 @item end | |
1402 Always executed after frame interpreting is completed. This can be used | |
1403 to perform any necessary post-processing. | |
1404 @item every | |
1405 Executes whenever the frame is reset, usually after the entire frame has | |
1406 been matched against the current line. | |
1407 @end table | |
1408 | |
1409 Note that @var{negate-p} and @var{case-fold-search} are ignored if | |
1410 @var{pred} is one of these special symbols. Only the first occurrence of | |
1411 each symbol in a frame is used; any duplicates are ignored. Also | |
1412 note that for performance reasons, the entries associated with these | |
1413 symbols are removed from the frame during the main interpreting loop. | |
1414 | |
1415 Your @var{func} can return certain values which control continued Regi | |
1416 processing. By default, if your @var{func} returns @code{nil} (as it | |
1417 should be careful to do explicitly), Regi will reset the frame to the | |
1418 first entry, and advance @samp{point} to the beginning of the next line. | |
1419 If a list is returned from your function, it can contain any combination | |
1420 of the following elements:@refill | |
1421 | |
1422 @table @asis | |
1423 @item the symbol @code{continue} | |
1424 This tells Regi to continue processing entries after a match, instead of | |
1425 resetting the frame and moving @samp{point}. In this way, lines of text | |
1426 can have multiple matches, but you have to be careful to avoid entering | |
1427 infinite loops. | |
1428 | |
1429 @item the symbol @code{abort} | |
1430 This tells Regi to terminate frame processing. However, any @code{end} | |
1431 entry is still processed. | |
1432 | |
1433 @item the list @code{(frame . @var{newframe})} | |
1434 This tells Regi to substitute @var{newframe} as the frame it is | |
1435 interpreting. In other words, your @var{func} can modify the Regi frame | |
1436 on the fly. @var{newframe} can be a variable containing a frame, or it | |
1437 can be the frame in-lined.@refill | |
1438 | |
1439 @item the list @code{(step . @var{step})} | |
1440 Tells Regi to move @var{step} number of lines forward as it continues | |
1441 processing. By default, Regi moves forward one line. @var{step} can be | |
1442 zero or negative of course, but watch out for infinite loops.@refill | |
1443 @end table | |
1444 | |
1445 During execution of your @var{func}, the following variables will be | |
1446 temporarily bound to some useful information:@refill | |
1447 | |
1448 @table @code | |
1449 @item curline | |
1450 The current line in the buffer that Regi is @code{looking-at}, as a string. | |
1451 @item curframe | |
1452 The current frame being interpreted. | |
1453 @item curentry | |
1454 The current frame entry being interpreted. | |
1455 @end table | |
1456 | |
1457 @node Frames You Can Customize, Post-yank Formatting Commands, Using Regi, Configuring the Citation Engine | |
1458 @vindex sc-nuke-mail-header | |
1459 @section Frames You Can Customize | |
1460 | |
1461 As mentioned earlier, Supercite uses various frames to perform | |
1462 certain jobs such as mail header information extraction and mail header | |
1463 nuking. However, these frames are not available for you to customize, | |
1464 except through abstract interfaces such as @code{sc-nuke-mail-header}, | |
1465 et al. | |
1466 | |
1467 @vindex sc-default-cite-frame | |
1468 However, the citation frames Supercite uses provide a lot of customizing | |
1469 power and are thus available to you to change to suit your needs. The | |
1470 workhorse of citation is the frame contained in the variable | |
1471 @code{sc-default-cite-frame}. This frame recognizes many situations, | |
1472 such as blank lines, which it interprets as paragraph separators. It | |
1473 also recognizes previously cited nested and non-nested citations in the | |
1474 original message. By default it will coerce non-nested citations into | |
1475 your preferred citation style, and it will add a level of citation to | |
1476 nested citations. It will also simply cite uncited lines in your | |
1477 preferred style. | |
1478 | |
1479 @cindex unciting | |
1480 @cindex reciting | |
1481 @vindex sc-default-uncite-frame | |
1482 @vindex sc-default-recite-frame | |
1483 In a similar vein, there are default frames for @dfn{unciting} and | |
1484 @dfn{reciting}, contained in the variables | |
1485 @code{sc-default-uncite-frame} and @code{sc-default-recite-frame} | |
1486 respectively.@refill | |
1487 | |
1488 As mentioned earlier (@pxref{Recognizing Citations}), citations are | |
1489 recognized through the values of the regular expressions | |
1490 @code{sc-citation-root-regexp}, et al. To recognize odd styles, you | |
1491 could modify these variables, or you could modify the default citing | |
1492 frame. Alternatively, you could set up association lists of frames for | |
1493 recognizing specific alternative forms. | |
1494 | |
1495 @vindex sc-cite-frame-alist | |
1496 @vindex sc-uncite-frame-alist | |
1497 @vindex sc-recite-frame-alist | |
1498 For each of the actions -- citing, unciting, and reciting -- an alist is | |
1499 consulted to find the frame to use (@code{sc-cite-frame-alist}, | |
1500 @code{sc-uncite-frame-alist}, and @code{sc-recite-frame-alist} | |
1501 respectively). These frames can contain alists of the form: | |
1502 | |
1503 @example | |
1504 ((@var{infokey} (@var{regexp} @. @var{frame}) (@var{regexp} @. @var{frame}) @dots{}) | |
1505 (@var{infokey} (@var{regexp} @. @var{frame}) (@var{regexp} @. @var{frame}) @dots{}) | |
1506 (@dots{})) | |
1507 @end example | |
1508 | |
1509 @vindex sc-mail-field | |
1510 @findex string-match | |
1511 Where @var{infokey} is a key suitable for @code{sc-mail-field}, | |
1512 @var{regexp} is a regular expression which is @code{string-match}'d | |
1513 against the value of the @code{sc-mail-field} key, and @var{frame} is | |
1514 the frame to use if a match occurred. @var{frame} can be a variable | |
1515 containing a frame or a frame in-lined.@refill | |
1516 | |
1517 When Supercite is about to cite, uncite, or recite a region, it consults | |
1518 the appropriate alist and attempts to find a frame to use. If one | |
1519 is not found from the alist, then the appropriate default frame is used. | |
1520 | |
1521 @node Post-yank Formatting Commands, Citing Commands, Frames You Can Customize, Top | |
1522 @vindex sc-mode-map-prefix | |
1523 @vindex mode-map-prefix (sc-) | |
1524 @kindex C-c C-p | |
1525 @chapter Post-yank Formatting Commands | |
1526 | |
1527 Once the original message has been yanked into the reply buffer, and | |
1528 @code{sc-cite-original} has had a chance to do its thing, a number of | |
1529 useful Supercite commands will be available to you. Since there is wide | |
1530 variety in the keymaps that MUAs set up in their reply buffers, it is | |
1531 next to impossible for Supercite to properly sprinkle its commands into | |
1532 the existing keymap. For this reason Supercite places its commands on a | |
1533 separate keymap, putting this keymap onto a prefix key in the reply | |
1534 buffer. You can customize the prefix key Supercite uses by changing the | |
1535 variable @code{sc-mode-map-prefix}. By default, the | |
1536 @code{sc-mode-map-prefix} is @kbd{C-c C-p}; granted, not a great choice, | |
1537 but unfortunately the best general solution so far. In the rest of this | |
1538 chapter, we'll assume you've installed Supercite's keymap on the default | |
1539 prefix.@refill | |
1540 | |
1541 @ifinfo | |
1542 @menu | |
1543 * Citing Commands:: | |
1544 * Insertion Commands:: | |
1545 * Variable Toggling Shortcuts:: | |
1546 * Mail Field Commands:: | |
1547 * Miscellaneous Commands:: | |
1548 @end menu | |
1549 @end ifinfo | |
1550 | |
1551 @node Citing Commands, Insertion Commands, Post-yank Formatting Commands, Post-yank Formatting Commands | |
1552 @vindex sc-cite-region-limit | |
1553 @section Commands to Manually Cite, Recite, and Uncite | |
1554 | |
1555 Probably the three most common post-yank formatting operations that you | |
1556 will perform will be the manual citing, reciting, and unciting of | |
1557 regions of text in the reply buffer. Often you may want to recite a | |
1558 paragraph to use a nickname, or manually cite a message when setting | |
1559 @code{sc-cite-region-limit} to @code{nil}. The following commands | |
1560 perform these functions on the region of text between @samp{point} and | |
1561 @samp{mark}. Each of them sets the @dfn{undo boundary} before modifying | |
1562 the region so that the command can be undone in the standard Emacs | |
1563 way.@refill | |
1564 | |
1565 Here is the list of Supercite citing commands: | |
1566 | |
1567 @table @asis | |
1568 @findex sc-cite-region | |
1569 @findex cite-region (sc-) | |
1570 @kindex C-c C-p c | |
1571 @vindex sc-pre-cite-hook | |
1572 @vindex pre-cite-hook (sc-) | |
1573 @vindex sc-confirm-always-p | |
1574 @vindex confirm-always-p | |
1575 @kindex C-u | |
1576 @item @code{sc-cite-region} (@kbd{C-c C-p c}) | |
1577 This command cites each line in the region of text by interpreting the | |
1578 selected frame from @code{sc-cite-frame-alist}, or the default citing | |
1579 frame @code{sc-default-cite-frame}. It runs the hook | |
1580 @code{sc-pre-cite-hook} before interpreting the frame. With an optional | |
1581 universal argument (@kbd{C-u}), it temporarily sets | |
1582 @code{sc-confirm-always-p} to @code{t} so you can confirm the | |
1583 attribution string for a single manual citing. | |
1584 @xref{Configuring the Citation Engine}.@refill | |
1585 | |
1586 @findex sc-uncite-region | |
1587 @findex uncite-region (sc-) | |
1588 @kindex C-c C-p u | |
1589 @item @code{sc-uncite-region} (@kbd{C-c C-p u}) | |
1590 This command removes any citation strings from the beginning of each | |
1591 cited line in the region by interpreting the selected frame from | |
1592 @code{sc-uncite-frame-alist}, or the default unciting frame | |
1593 @code{sc-default-uncite-frame}. It runs the hook | |
1594 @code{sc-pre-uncite-hook} before interpreting the frame. | |
1595 @xref{Configuring the Citation Engine}.@refill | |
1596 | |
1597 @findex sc-recite-region | |
1598 @findex recite-region (sc-) | |
1599 @kindex C-c C-p r | |
1600 @item @code{sc-recite-region} (@kbd{C-c C-p r}) | |
1601 This command recites each line the region by interpreting the selected | |
1602 frame from @code{sc-recite-frame-alist}, or the default reciting frame | |
1603 @code{sc-default-recite-frame}. It runs the hook | |
1604 @code{sc-pre-recite-hook} before interpreting the frame. | |
1605 @xref{Configuring the Citation Engine}.@refill | |
1606 | |
1607 @vindex sc-confirm-always-p | |
1608 @vindex confirm-always-p (sc-) | |
1609 Supercite will always ask you to confirm the attribution when reciting a | |
1610 region, regardless of the value of @code{sc-confirm-always-p}. | |
1611 @end table | |
1612 | |
1613 @node Insertion Commands, Variable Toggling Shortcuts, Citing Commands, Post-yank Formatting Commands | |
1614 @section Insertion Commands | |
1615 | |
1616 These two functions insert various strings into the reply buffer. | |
1617 | |
1618 @table @asis | |
1619 @findex sc-insert-reference | |
1620 @findex insert-reference (sc-) | |
1621 @kindex C-c C-p w | |
1622 @item @code{sc-insert-reference} (@kbd{C-c C-p w}) | |
1623 @vindex sc-preferred-header-style | |
1624 @vindex preferred-header-style (sc-) | |
1625 Inserts a reference header into the reply buffer at @samp{point}. With | |
1626 no arguments, the header indexed by @code{sc-preferred-header-style} is | |
1627 inserted. An optional numeric argument is the index into | |
1628 @code{sc-rewrite-header-list} indicating which reference header to | |
1629 write.@refill | |
1630 | |
1631 With just the universal argument (@kbd{C-u}), electric reference mode is | |
1632 entered, regardless of the value of @code{sc-electric-references-p}. | |
1633 | |
1634 @findex sc-insert-citation | |
1635 @findex insert-citation (sc-) | |
1636 @kindex C-c C-p i | |
1637 @item @code{sc-insert-citation} (@kbd{C-c C-p i}) | |
1638 Inserts the current citation string at the beginning of the line that | |
1639 @samp{point} is on. If the line is already cited, Supercite will issue | |
1640 an error and will not cite the line. | |
1641 @end table | |
1642 | |
1643 @node Variable Toggling Shortcuts, Mail Field Commands, Insertion Commands, Post-yank Formatting Commands | |
1644 @cindex toggling variables | |
1645 @section Variable Toggling Shortcuts | |
1646 | |
1647 Supercite defines a number of commands that make it easier for you to | |
1648 toggle and set various Supercite variables as you are editing the reply | |
1649 buffer. For example, you may want to turn off filling or whitespace | |
1650 cleanup, but only temporarily. These toggling shortcut commands make | |
1651 this easy to do. | |
1652 | |
1653 @kindex C-c C-p C-t | |
1654 Like Supercite commands in general, the toggling commands are placed on | |
1655 a keymap prefix within the greater Supercite keymap. For the default | |
1656 value of @code{sc-mode-map-prefix}, this will be | |
1657 @kbd{C-c C-p C-t}.@refill | |
1658 | |
1659 The following commands toggle the value of certain Supercite variables | |
1660 which take only a binary value: | |
1661 | |
1662 @table @kbd | |
1663 @item C-c C-p C-t b | |
1664 Toggles the variable @code{sc-mail-nuke-blank-lines-p}. | |
1665 | |
1666 @item C-c C-p C-t c | |
1667 Toggles the variable @code{sc-confirm-always-p}. | |
1668 | |
1669 @item C-c C-p C-t d | |
1670 Toggles the variable @code{sc-downcase-p}. | |
1671 | |
1672 @item C-c C-p C-t e | |
1673 Toggles the variable @code{sc-electric-references-p}. | |
1674 | |
1675 @item C-c C-p C-t f | |
1676 Toggles the variable @code{sc-auto-fill-region-p}. | |
1677 | |
1678 @item C-c C-p C-t o | |
1679 Toggles the variable @code{sc-electric-circular-p}. | |
1680 | |
1681 @item C-c C-p C-t s | |
1682 Toggles the variable @code{sc-nested-citation-p}. | |
1683 | |
1684 @item C-c C-p C-t u | |
1685 Toggles the variable @code{sc-use-only-preferences-p}. | |
1686 | |
1687 @item C-c C-p C-t w | |
1688 Toggles the variable @code{sc-fixup-whitespace-p}. | |
1689 @end table | |
1690 | |
1691 @findex set-variable | |
1692 The following commands let you set the value of multi-value variables, | |
1693 in the same way that Emacs' @code{set-variable} does: | |
1694 | |
1695 @table @kbd | |
1696 @item C-c C-p C-t a | |
1697 Sets the value of the variable @code{sc-preferred-attribution-list}. | |
1698 | |
1699 @item C-c C-p C-t l | |
1700 Sets the value of the variable @code{sc-cite-region-limit}. | |
1701 | |
1702 @item C-c C-p C-t n | |
1703 Sets the value of the variable @code{sc-mail-nuke-mail-headers}. | |
1704 | |
1705 @item C-c C-p C-t N | |
1706 Sets the value of the variable @code{sc-mail-header-nuke-list}. | |
1707 | |
1708 @item C-c C-p C-t p | |
1709 Sets the value of the variable @code{sc-preferred-header-style}. | |
1710 @end table | |
1711 | |
1712 @kindex C-c C-p C-p | |
1713 One special command is provided to toggle both | |
1714 @code{sc-auto-fill-region-p} and @code{sc-fixup-whitespace-p} together. | |
1715 This is because you typically want to run Supercite with either variable | |
1716 as @code{nil} or non-@code{nil}. The command to toggle these variables | |
1717 together is bound on @kbd{C-c C-p C-p}.@refill | |
1718 | |
1719 Finally, the command @kbd{C-c C-p C-t h} (also @kbd{C-c C-p C-t ?}) | |
1720 brings up a Help message on the toggling keymap. | |
1721 | |
1722 | |
1723 @node Mail Field Commands, Miscellaneous Commands, Variable Toggling Shortcuts, Post-yank Formatting Commands | |
1724 @section Mail Field Commands | |
1725 | |
1726 These commands allow you to view, modify, add, and delete various bits | |
1727 of information from the info alist. | |
1728 @xref{Information Keys and the Info Alist}.@refill | |
1729 | |
1730 @table @asis | |
1731 @kindex C-c C-p f | |
1732 @findex sc-mail-field-query | |
1733 @findex mail-field-query (sc-) | |
1734 @kindex C-c C-p f | |
1735 @item @code{sc-mail-field-query} (@kbd{C-c C-p f}) | |
1736 Allows you to interactively view, modify, add, and delete info alist | |
1737 key-value pairs. With no argument, you are prompted (with completion) | |
1738 for a info key. The value associated with that key is displayed in the | |
1739 minibuffer. With an argument, this command will first ask if you want | |
1740 to view, modify, add, or delete an info key. Viewing is identical to | |
1741 running the command with no arguments. | |
1742 | |
1743 If you want to modify the value of a key, Supercite will first prompt | |
1744 you (with completion) for the key of the value you want to change. It | |
1745 will then put you in the minibuffer with the key's current value so you | |
1746 can edit the value as you wish. When you hit @key{RET}, the key's value | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1747 is changed. Minibuffer history is kept for the values. |
84313 | 1748 |
1749 If you choose to delete a key-value pair, Supercite will prompt you (with | |
1750 completion) for the key to delete. | |
1751 | |
1752 If you choose to add a new key-value pair, Supercite firsts prompts you | |
1753 for the key to add. Note that completion is turned on for this prompt, | |
1754 but you can type any key name here, even one that does not yet exist. | |
1755 After entering the key, Supercite prompts you for the key's value. It | |
1756 is not an error to enter a key that already exists, but the new value | |
1757 will override any old value. It will not replace it though; if you | |
1758 subsequently delete the key-value pair, the old value will reappear. | |
1759 | |
1760 @findex sc-mail-process-headers | |
1761 @findex mail-process-headers (sc-) | |
1762 @kindex C-c C-p g | |
1763 @item @code{sc-mail-process-headers} (@kbd{C-c C-p g}) | |
1764 This command lets you re-initialize Supercite's info alist from any set | |
1765 of mail headers in the region between @samp{point} and @samp{mark}. | |
1766 This function is especially useful for replying to digest messages where | |
1767 Supercite will initially set up its information for the digest | |
1768 originator, but you want to cite each component article with the real | |
1769 message author. Note that unless an error during processing occurs, any | |
1770 old information is lost.@refill | |
1771 @end table | |
1772 | |
1773 @node Miscellaneous Commands, Information Keys and the Info Alist, Mail Field Commands, Post-yank Formatting Commands | |
1774 @section Miscellaneous Commands | |
1775 | |
1776 @table @asis | |
1777 @findex sc-open-line | |
1778 @findex open-line (sc-) | |
1779 @findex open-line | |
1780 @kindex C-c C-p o | |
1781 @item @code{sc-open-line} (@kbd{C-c C-p o}) | |
1782 Similar to Emacs' standard @code{open-line} commands, but inserts the | |
1783 citation string in front of the new line. As with @code{open-line}, | |
1784 an optional numeric argument inserts that many new lines.@refill | |
1785 @end table | |
1786 | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1787 @node Hints to MUA Authors, Thanks and History, Electric References, Top |
84313 | 1788 @chapter Hints to MUA Authors |
1789 | |
1790 In June of 1989, some discussion was held between the various MUA | |
1791 authors, the Supercite author, and other Supercite users. These | |
1792 discussions centered around the need for a standard interface between | |
1793 MUAs and Supercite (or any future Supercite-like packages). This | |
1794 interface was formally proposed by Martin Neitzel on Fri, 23 Jun 89, in | |
1795 a mail message to the Supercite mailing list: | |
1796 | |
1797 @example | |
1798 Martin> Each news/mail-reader should provide a form of | |
1799 Martin> mail-yank-original that | |
1800 | |
1801 Martin> 1: inserts the original message incl. header into the | |
1802 Martin> reply buffer; no indentation/prefixing is done, the header | |
1803 Martin> tends to be a "full blown" version rather than to be | |
1804 Martin> stripped down. | |
1805 | |
1806 Martin> 2: `point' is at the start of the header, `mark' at the | |
1807 Martin> end of the message body. | |
1808 | |
1809 Martin> 3: (run-hooks 'mail-yank-hooks) | |
1810 | |
1811 Martin> [Supercite] should be run as such a hook and merely | |
1812 Martin> rewrite the message. This way it isn't anymore | |
1813 Martin> [Supercite]'s job to gather the original from obscure | |
1814 Martin> sources. [@dots{}] | |
1815 @end example | |
1816 | |
1817 @vindex mail-citation-hook | |
1818 @vindex mail-yank-hooks | |
1819 @cindex sendmail.el | |
1820 @findex mail-yank-original | |
1821 @findex defvar | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1822 This specification was adopted, but underwent a slight modification with |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1823 the release of Emacs 19. Instead of the variable |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1824 @code{mail-yank-hooks}, the hook variable that the MUA should provide is |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1825 @code{mail-citation-hook}. Richard Stallman suggests that the MUAs |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1826 should @code{defvar} @code{mail-citation-hook} to @code{nil} and perform |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1827 some default citing when that is the case.@refill |
84313 | 1828 |
1829 If you are writing a new MUA package, or maintaining an existing MUA | |
1830 package, you should make it conform to this interface so that your users | |
1831 will be able to link Supercite easily and seamlessly. To do this, when | |
1832 setting up a reply or forward buffer, your MUA should follow these | |
1833 steps: | |
1834 | |
1835 @enumerate | |
1836 @item | |
1837 Insert the original message, including the mail headers into the reply | |
105934
26b37c3219d1
(Hints to MUA Authors): MUA should do any decoding.
Glenn Morris <rgm@gnu.org>
parents:
102059
diff
changeset
|
1838 buffer. At this point you should not modify the raw text in any way |
26b37c3219d1
(Hints to MUA Authors): MUA should do any decoding.
Glenn Morris <rgm@gnu.org>
parents:
102059
diff
changeset
|
1839 (except for any necessary decoding, e.g. of quoted-printable text), and |
84313 | 1840 you should place all the original headers into the body of the reply. |
1841 This means that many of the mail headers will be duplicated, one copy | |
105934
26b37c3219d1
(Hints to MUA Authors): MUA should do any decoding.
Glenn Morris <rgm@gnu.org>
parents:
102059
diff
changeset
|
1842 above the @code{mail-header-separator} line and one copy below, however |
26b37c3219d1
(Hints to MUA Authors): MUA should do any decoding.
Glenn Morris <rgm@gnu.org>
parents:
102059
diff
changeset
|
1843 there will probably be more headers below this line.@refill |
84313 | 1844 |
1845 @item | |
1846 Set @samp{point} to the beginning of the line containing the first mail | |
1847 header in the body of the reply. Set @samp{mark} at the end of the | |
1848 message text. It is very important that the region be set around the | |
1849 text Supercite is to modify and that the mail headers are within this | |
1850 region. Supercite will not venture outside the region for any reason, | |
1851 and anything within the region is fair game, so don't put anything that | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1852 @strong{must} remain unchanged inside the region.@refill |
84313 | 1853 |
1854 @item | |
1855 Run the hook @code{mail-citation-hook}. You will probably want to | |
1856 provide some kind of default citation functions in cases where the user | |
1857 does not have Supercite installed. By default, your MUA should | |
1858 @code{defvar} @code{mail-citation-hook} to @code{nil}, and in your | |
1859 yanking function, check its value. If it finds | |
1860 @code{mail-citation-hook} to be @code{nil}, it should perform some | |
1861 default citing behavior. User who want to connect to Supercite then | |
1862 need only add @code{sc-cite-original} to this list of hooks using | |
1863 @code{add-hook}.@refill | |
1864 @end enumerate | |
1865 | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1866 If you do all this your MUA will join the ranks of those that conform to |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1867 this interface ``out of the box.'' |
84313 | 1868 |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1869 @node Thanks and History, GNU Free Documentation License, Hints to MUA Authors, Top |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1870 @chapter Thanks and History |
84313 | 1871 |
1872 The Supercite package was derived from its predecessor Superyank 1.11 | |
1873 which was inspired by various bits of code and ideas from Martin Neitzel | |
1874 and Ashwin Ram. They were the folks who came up with the idea of | |
1875 non-nested citations and implemented some rough code to provide this | |
1876 style. Superyank and Supercite version 2 evolved to the point where much | |
1877 of the attribution selection mechanism was automatic, and features have | |
1878 been continuously added through the comments and suggestions of the | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1879 Supercite mailing list participants. |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1880 |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1881 With version 3, Supercite underwent an almost complete rewrite, |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1882 benefitting in a number of ways, including vast improvements in the |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1883 speed of performance, a big reduction in size of the code and in the use |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1884 of Emacs resources, and a much cleaner and flexible internal |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1885 architecture. Most of this work was internal and not of very great |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1886 importance to the casual user. There were some changes at the |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1887 user-visible level, but for the most part, the Supercite configuration |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1888 variables from version 2 should still be relevant to version 3. |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1889 Hopefully Supercite version 3 is faster, smaller, and much more flexible |
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1890 than its predecessors. |
84313 | 1891 |
1892 In the version 2 manual I thanked some specific people for their help in | |
1893 developing Supercite 2. You folks know who you are and your continued | |
1894 support is greatly appreciated. I wish to thank everyone on the | |
1895 Supercite mailing list, especially the brave alpha testers, who helped | |
1896 considerably in testing out the concepts and implementation of Supercite | |
1897 version 3. Special thanks go out to the MUA and Emacs authors Kyle | |
1898 Jones, Stephen Gildea, Richard Stallman, and Jamie Zawinski for coming | |
1899 to a quick agreement on the new @code{mail-citation-hook} interface, and | |
1900 for adding the magic lisp to their code to support this. | |
1901 | |
1902 All who have helped and contributed have been greatly appreciated. | |
1903 | |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1904 Supercite was written by Barry Warsaw. |
84313 | 1905 |
92246
6184e70102de
Remove a lot of old and obsolete info.
Glenn Morris <rgm@gnu.org>
parents:
87903
diff
changeset
|
1906 @node GNU Free Documentation License, Concept Index, Thanks and History, Top |
84313 | 1907 @appendix GNU Free Documentation License |
1908 @include doclicense.texi | |
1909 | |
1910 @node Concept Index, Command Index, GNU Free Documentation License, Top | |
1911 @unnumbered Concept Index | |
1912 @printindex cp | |
1913 | |
1914 @node Command Index, Key Index, Concept Index, Top | |
1915 @unnumbered Command Index | |
1916 @ifinfo | |
1917 | |
1918 @end ifinfo | |
1919 Since all supercite commands are prepended with the string | |
1920 ``@code{sc-}'', each appears under its @code{sc-}@var{command} name and | |
1921 its @var{command} name. | |
1922 @iftex | |
1923 @sp 2 | |
1924 @end iftex | |
1925 @printindex fn | |
1926 | |
1927 @node Key Index, Variable Index, Command Index, Top | |
1928 @unnumbered Key Index | |
1929 @printindex ky | |
1930 | |
1931 @node Variable Index, , Key Index, Top | |
1932 @unnumbered Variable Index | |
1933 @ifinfo | |
1934 | |
1935 @end ifinfo | |
1936 Since all supercite variables are prepended with the string | |
1937 ``@code{sc-}'', each appears under its @code{sc-}@var{variable} name and | |
1938 its @var{variable} name. | |
1939 @iftex | |
1940 @sp 2 | |
1941 @end iftex | |
1942 @printindex vr | |
1943 @bye | |
1944 | |
1945 @ignore | |
1946 arch-tag: 0521847a-4680-44b6-ae6e-13ce20e18436 | |
1947 @end ignore |