Mercurial > emacs
comparison doc/misc/gnus.texi @ 96024:be43dd7afc91
Merge from gnus--devo--0
Revision: emacs@sv.gnu.org/emacs--devo--0--patch-1244
author | Miles Bader <miles@gnu.org> |
---|---|
date | Tue, 17 Jun 2008 02:32:59 +0000 |
parents | 6f0fce2c3559 |
children | 3a9a5b883ec1 |
comparison
equal
deleted
inserted
replaced
96023:936483adbab6 | 96024:be43dd7afc91 |
---|---|
4396 * Propagating marks:: How to propagate marks from nnmairix groups | 4396 * Propagating marks:: How to propagate marks from nnmairix groups |
4397 * nnmairix tips and tricks:: Some tips, tricks and examples | 4397 * nnmairix tips and tricks:: Some tips, tricks and examples |
4398 * nnmairix caveats:: Some more stuff you might want to know | 4398 * nnmairix caveats:: Some more stuff you might want to know |
4399 @end menu | 4399 @end menu |
4400 | 4400 |
4401 @c FIXME: The markup in this section needs improvement. E.g. add | 4401 @c FIXME: The markup in this section might need improvement. |
4402 @c @sample{...}, maybe remove some @strong{...}, convert ` - ' to `---`, | 4402 @c E.g. adding @samp, @var, @file, @command, etc. |
4403 @c ... | 4403 @c Cf. (info "(texinfo)Indicating") |
4404 | 4404 |
4405 @node About mairix | 4405 @node About mairix |
4406 @subsubsection About mairix | 4406 @subsubsection About mairix |
4407 | 4407 |
4408 Mairix is a tool for indexing and searching words in locally stored | 4408 Mairix is a tool for indexing and searching words in locally stored |
4434 but much faster. | 4434 but much faster. |
4435 | 4435 |
4436 @node nnmairix requirements | 4436 @node nnmairix requirements |
4437 @subsubsection nnmairix requirements | 4437 @subsubsection nnmairix requirements |
4438 | 4438 |
4439 Mairix searches local mail - that means, mairix absolutely must have | 4439 Mairix searches local mail---that means, mairix absolutely must have |
4440 direct access to your mail folders. If your mail resides on another | 4440 direct access to your mail folders. If your mail resides on another |
4441 server (e.g. an @acronym{IMAP} server) and you happen to have shell | 4441 server (e.g. an @acronym{IMAP} server) and you happen to have shell |
4442 access, @code{nnmairix} supports running mairix remotely, e.g. via ssh. | 4442 access, @code{nnmairix} supports running mairix remotely, e.g. via ssh. |
4443 | 4443 |
4444 Additionally, @code{nnmairix} only supports the following Gnus back | 4444 Additionally, @code{nnmairix} only supports the following Gnus back |
4445 ends: @code{nnml}, @code{nnmaildir}, and @code{nnimap}. You | 4445 ends: @code{nnml}, @code{nnmaildir}, and @code{nnimap}. You must use |
4446 @strong{must} use one of these back ends for using | 4446 one of these back ends for using @code{nnmairix}. Other back ends, like |
4447 @code{nnmairix}. Other back ends, like @code{nnmbox}, @code{nnfolder} or | 4447 @code{nnmbox}, @code{nnfolder} or @code{nnmh}, won't work. |
4448 @code{nnmh}, won't work. | |
4449 | 4448 |
4450 If you absolutely must use mbox and still want to use @code{nnmairix}, | 4449 If you absolutely must use mbox and still want to use @code{nnmairix}, |
4451 you can set up a local @acronym{IMAP} server, which you then access via | 4450 you can set up a local @acronym{IMAP} server, which you then access via |
4452 @code{nnimap}. This is a rather massive setup for accessing some mbox | 4451 @code{nnimap}. This is a rather massive setup for accessing some mbox |
4453 files, so just change to MH or Maildir already... | 4452 files, so just change to MH or Maildir already... |
4471 automatically update themselves by calling mairix. | 4470 automatically update themselves by calling mairix. |
4472 | 4471 |
4473 You might ask why you need @code{nnmairix} at all, since mairix already | 4472 You might ask why you need @code{nnmairix} at all, since mairix already |
4474 creates the group, populates it with links to the mails so that you can | 4473 creates the group, populates it with links to the mails so that you can |
4475 then access it with Gnus, right? Well, this @emph{might} work, but often | 4474 then access it with Gnus, right? Well, this @emph{might} work, but often |
4476 does not - at least not without problems. Most probably you will get | 4475 does not---at least not without problems. Most probably you will get |
4477 strange article counts, and sometimes you might see mails which Gnus | 4476 strange article counts, and sometimes you might see mails which Gnus |
4478 claims have already been canceled and are inaccessible. This is due to | 4477 claims have already been canceled and are inaccessible. This is due to |
4479 the fact that Gnus isn't really amused when things are happening behind | 4478 the fact that Gnus isn't really amused when things are happening behind |
4480 its back. Another problem can be the mail back end itself, e.g. if you | 4479 its back. Another problem can be the mail back end itself, e.g. if you |
4481 use mairix with an @acronym{IMAP} server (I had Dovecot complaining | 4480 use mairix with an @acronym{IMAP} server (I had Dovecot complaining |
4482 about corrupt index files when mairix changed the contents of the search | 4481 about corrupt index files when mairix changed the contents of the search |
4483 group). Using @code{nnmairix} should circumvent these problems. | 4482 group). Using @code{nnmairix} should circumvent these problems. |
4484 | 4483 |
4485 @code{nnmairix} is not really a mail back end - it's actually more like a | 4484 @code{nnmairix} is not really a mail back end---it's actually more like a |
4486 wrapper, sitting between a ``real'' mail back end where mairix stores the | 4485 wrapper, sitting between a ``real'' mail back end where mairix stores the |
4487 searches and the Gnus front end. You can choose between three different | 4486 searches and the Gnus front end. You can choose between three different |
4488 mail back ends for the mairix folders: @code{nnml}, @code{nnmaildir} or | 4487 mail back ends for the mairix folders: @code{nnml}, @code{nnmaildir} or |
4489 @code{nnimap}. @code{nnmairix} will call the mairix binary so that the | 4488 @code{nnimap}. @code{nnmairix} will call the mairix binary so that the |
4490 search results are stored in folders named | 4489 search results are stored in folders named |
4493 can use an existing mail back end where you already store your mail, but | 4492 can use an existing mail back end where you already store your mail, but |
4494 if you're uncomfortable with @code{nnmairix} creating new mail groups | 4493 if you're uncomfortable with @code{nnmairix} creating new mail groups |
4495 alongside your other mail, you can also create e.g. a new | 4494 alongside your other mail, you can also create e.g. a new |
4496 @code{nnmaildir} server exclusively for mairix. However, a special case | 4495 @code{nnmaildir} server exclusively for mairix. However, a special case |
4497 exists if you want to use mairix remotely on an IMAP server with | 4496 exists if you want to use mairix remotely on an IMAP server with |
4498 @code{nnimap} - here the mairix folders and your other mail must be on | 4497 @code{nnimap}---here the mairix folders and your other mail must be on |
4499 the same @code{nnimap} back end. | 4498 the same @code{nnimap} back end. |
4500 | 4499 |
4501 @node Setting up mairix | 4500 @node Setting up mairix |
4502 @subsubsection Setting up mairix | 4501 @subsubsection Setting up mairix |
4503 | 4502 |
4509 @example | 4508 @example |
4510 # Your Maildir/MH base folder | 4509 # Your Maildir/MH base folder |
4511 base=~/Maildir | 4510 base=~/Maildir |
4512 @end example | 4511 @end example |
4513 | 4512 |
4514 This is the base folder for your mails. All the following paths are | 4513 This is the base folder for your mails. All the following directories |
4515 relative to this base folder. If you want to use @code{nnmairix} with | 4514 are relative to this base folder. If you want to use @code{nnmairix} |
4516 @code{nnimap}, this base path has to point to the mail path where the | 4515 with @code{nnimap}, this base directory has to point to the mail |
4517 @acronym{IMAP} server stores the mail folders! | 4516 directory where the @acronym{IMAP} server stores the mail folders! |
4518 | 4517 |
4519 @c FIXME: Add typical examples? | |
4520 @example | 4518 @example |
4521 maildir= ... your maildir folders which should be indexed ... | 4519 maildir= ... your maildir folders which should be indexed ... |
4522 mh= ... your nnml/mh folders which should be indexed ... | 4520 mh= ... your nnml/mh folders which should be indexed ... |
4523 mbox = ... your mbox files which should be indexed ... | 4521 mbox = ... your mbox files which should be indexed ... |
4524 @end example | 4522 @end example |
4525 | 4523 |
4526 Specify all your maildir/nnml folders and mbox files (relative to the | 4524 Specify all your maildir/nnml folders and mbox files (relative to the |
4527 base path!) you want to index with mairix. See the man-page for | 4525 base directory!) you want to index with mairix. See the man-page for |
4528 mairixrc for details. | 4526 mairixrc for details. |
4529 | 4527 |
4530 @example | 4528 @example |
4531 omit=zz_mairix-* | 4529 omit=zz_mairix-* |
4532 @end example | 4530 @end example |
4534 @vindex nnmairix-group-prefix | 4532 @vindex nnmairix-group-prefix |
4535 This should make sure that you don't accidentally index the mairix | 4533 This should make sure that you don't accidentally index the mairix |
4536 search results. You can change the prefix of these folders with the | 4534 search results. You can change the prefix of these folders with the |
4537 variable @code{nnmairix-group-prefix}. | 4535 variable @code{nnmairix-group-prefix}. |
4538 | 4536 |
4539 @c FIXME: Add typical examples? | |
4540 @example | 4537 @example |
4541 mformat= ... 'maildir' or 'mh' ... | 4538 mformat= ... 'maildir' or 'mh' ... |
4542 database= ... location of database file ... | 4539 database= ... location of database file ... |
4543 @end example | 4540 @end example |
4544 | 4541 |
4545 The @code{format} setting specifies the output format for the mairix | 4542 The @code{format} setting specifies the output format for the mairix |
4546 search folder. Set this to @code{mh} if you want to access search results | 4543 search folder. Set this to @code{mh} if you want to access search results |
4547 with @code{nnml}. Otherwise choose @code{maildir}. | 4544 with @code{nnml}. Otherwise choose @code{maildir}. |
4548 | 4545 |
4549 See the man pages for mairix and mairixrc for further options. Now | 4546 To summarize, here is my shortened @file{.mairixrc} file as an example: |
4550 simply call @code{mairix} to create the index for the first time. | 4547 |
4548 @example | |
4549 base=~/Maildir | |
4550 maildir=.personal:.work:.logcheck:.sent | |
4551 mh=../Mail/nnml/*... | |
4552 mbox=../mboxmail/mailarchive_year* | |
4553 mformat=maildir | |
4554 omit=zz_mairix-* | |
4555 database=~/.mairixdatabase | |
4556 @end example | |
4557 | |
4558 In this case, the base directory is @file{~/Maildir}, where all my Maildir | |
4559 folders are stored. As you can see, the folders are separated by | |
4560 colons. If you wonder why every folder begins with a dot: this is | |
4561 because I use Dovecot as @acronym{IMAP} server, which again uses | |
4562 @code{Maildir++} folders. For testing nnmairix, I also have some | |
4563 @code{nnml} mail, which is saved in @file{~/Mail/nnml}. Since this has | |
4564 to be specified relative to the @code{base} directory, the @code{../Mail} | |
4565 notation is needed. Note that the line ends in @code{*...}, which means | |
4566 to recursively scan all files under this directory. Without the three | |
4567 dots, the wildcard @code{*} will not work recursively. I also have some | |
4568 old mbox files with archived mail lying around in @file{~/mboxmail}. | |
4569 The other lines should be obvious. | |
4570 | |
4571 See the man page for @code{mairixrc} for details and further options, | |
4572 especially regarding wildcard usage, which may be a little different | |
4573 than you are used to. | |
4574 | |
4575 Now simply call @code{mairix} to create the index for the first time. | |
4576 Note that this may take a few minutes, but every following index will do | |
4577 the updates incrementally and hence is very fast. | |
4551 | 4578 |
4552 @node Configuring nnmairix | 4579 @node Configuring nnmairix |
4553 @subsubsection Configuring nnmairix | 4580 @subsubsection Configuring nnmairix |
4554 | 4581 |
4555 In group mode, type @kbd{G b c} | 4582 In group mode, type @kbd{G b c} |
4558 server. You will have to specify the following: | 4585 server. You will have to specify the following: |
4559 | 4586 |
4560 @itemize @bullet | 4587 @itemize @bullet |
4561 | 4588 |
4562 @item | 4589 @item |
4563 The @strong{name} of the @code{nnmairix} server - choose whatever you | 4590 The @strong{name} of the @code{nnmairix} server---choose whatever you |
4564 want. | 4591 want. |
4565 | 4592 |
4566 @item | 4593 @item |
4567 The @strong{mail back end} where mairix should stores its | 4594 The @strong{mail back end} where mairix should stores its |
4568 searches. Currently @code{nnmaildir}, @code{nnimap} and @code{nnml} are | 4595 searches. Currently @code{nnmaildir}, @code{nnimap} and @code{nnml} are |
4741 (Only in @code{nnmairix} groups!) Tries determine the group this article | 4768 (Only in @code{nnmairix} groups!) Tries determine the group this article |
4742 originally came from and displays the article in this group, so that | 4769 originally came from and displays the article in this group, so that |
4743 e.g. replying to this article the correct posting styles/group | 4770 e.g. replying to this article the correct posting styles/group |
4744 parameters are applied (@code{nnmairix-goto-original-article}). This | 4771 parameters are applied (@code{nnmairix-goto-original-article}). This |
4745 function will use the registry if available, but can also parse the | 4772 function will use the registry if available, but can also parse the |
4746 article file path as a fallback method. | 4773 article file name as a fallback method. |
4747 | 4774 |
4748 @item $ u | 4775 @item $ u |
4749 @kindex $ u (Summary) | 4776 @kindex $ u (Summary) |
4750 @findex nnmairix-remove-tick-mark-original-article | 4777 @findex nnmairix-remove-tick-mark-original-article |
4751 Remove possibly existing tick mark from original article | 4778 Remove possibly existing tick mark from original article |
4779 can dynamically change your folders any time you want to. This also | 4806 can dynamically change your folders any time you want to. This also |
4780 implies that you will usually read your mails in the @code{nnmairix} | 4807 implies that you will usually read your mails in the @code{nnmairix} |
4781 groups instead of your ``real'' mail groups. | 4808 groups instead of your ``real'' mail groups. |
4782 | 4809 |
4783 There is one problem, though: say you got a new mail from | 4810 There is one problem, though: say you got a new mail from |
4784 @samp{david@@foobar.com} - it will now show up in two groups, the | 4811 @samp{david@@foobar.com}; it will now show up in two groups, the |
4785 ``real'' group (your INBOX, for example) and in the @code{nnmairix} | 4812 ``real'' group (your INBOX, for example) and in the @code{nnmairix} |
4786 search group (provided you have updated the mairix database). Now you | 4813 search group (provided you have updated the mairix database). Now you |
4787 enter the @code{nnmairix} group and read the mail. The mail will be | 4814 enter the @code{nnmairix} group and read the mail. The mail will be |
4788 marked as read, but only in the @code{nnmairix} group - in the ``real'' | 4815 marked as read, but only in the @code{nnmairix} group---in the ``real'' |
4789 mail group it will be still shown as unread. | 4816 mail group it will be still shown as unread. |
4790 | 4817 |
4791 You could now catch up the mail group (@pxref{Group Data}), but this is | 4818 You could now catch up the mail group (@pxref{Group Data}), but this is |
4792 tedious and error prone, since you may overlook mails you don't have | 4819 tedious and error prone, since you may overlook mails you don't have |
4793 created @code{nnmairix} groups for. Of course, you could first use | 4820 created @code{nnmairix} groups for. Of course, you could first use |
4830 set @code{gnus-registry-max-entries} to a large enough value; to be on | 4857 set @code{gnus-registry-max-entries} to a large enough value; to be on |
4831 the safe side, choose roughly the amount of mails you index with mairix. | 4858 the safe side, choose roughly the amount of mails you index with mairix. |
4832 | 4859 |
4833 @vindex nnmairix-only-use-registry | 4860 @vindex nnmairix-only-use-registry |
4834 If you don't want to use the registry or the registry hasn't seen the | 4861 If you don't want to use the registry or the registry hasn't seen the |
4835 original article yet, @code{nnmairix} will use an additional mairix search | 4862 original article yet, @code{nnmairix} will use an additional mairix |
4836 for determining the file path of the article. This, of course, is way | 4863 search for determining the file name of the article. This, of course, is |
4837 slower than the registry - if you set hundreds or even thousands of | 4864 way slower than the registry---if you set hundreds or even thousands of |
4838 marks this way, it might take some time. You can avoid this situation | 4865 marks this way, it might take some time. You can avoid this situation by |
4839 by setting @code{nnmairix-only-use-registry} to t. | 4866 setting @code{nnmairix-only-use-registry} to t. |
4840 | 4867 |
4841 Maybe you also want to propagate marks the other way round, i.e. if you | 4868 Maybe you also want to propagate marks the other way round, i.e. if you |
4842 tick an article in a "real" mail group, you'd like to have the same | 4869 tick an article in a "real" mail group, you'd like to have the same |
4843 article in a @code{nnmairix} group ticked, too. For several good | 4870 article in a @code{nnmairix} group ticked, too. For several good |
4844 reasons, this can only be done efficiently if you use maildir. To | 4871 reasons, this can only be done efficiently if you use maildir. To |
4896 @samp{F:f} as query and do not include threads. | 4923 @samp{F:f} as query and do not include threads. |
4897 | 4924 |
4898 Now activate marks propagation for this group by using @kbd{G b p}. Then | 4925 Now activate marks propagation for this group by using @kbd{G b p}. Then |
4899 activate the always-unread feature by using @kbd{G b r} twice. | 4926 activate the always-unread feature by using @kbd{G b r} twice. |
4900 | 4927 |
4901 So far so good - but how do you remove the tick marks in the @code{nnmairix} | 4928 So far so good---but how do you remove the tick marks in the @code{nnmairix} |
4902 group? There are two options: You may simply use | 4929 group? There are two options: You may simply use |
4903 @code{nnmairix-remove-tick-mark-original-article} (bound to @kbd{$ u}) to remove | 4930 @code{nnmairix-remove-tick-mark-original-article} (bound to @kbd{$ u}) to remove |
4904 tick marks from the original article. The other possibility is to set | 4931 tick marks from the original article. The other possibility is to set |
4905 @code{nnmairix-propagate-marks-to-nnmairix-groups} to @code{t}, but see the above | 4932 @code{nnmairix-propagate-marks-to-nnmairix-groups} to @code{t}, but see the above |
4906 comments about this option. If it works for you, the tick marks should | 4933 comments about this option. If it works for you, the tick marks should |
4918 | 4945 |
4919 As described before, all @code{nnmairix} groups are in fact stored on | 4946 As described before, all @code{nnmairix} groups are in fact stored on |
4920 the mail back end in the form @samp{zz_mairix-<NAME>-<NUMBER>}. You can | 4947 the mail back end in the form @samp{zz_mairix-<NAME>-<NUMBER>}. You can |
4921 see them when you enter the back end server in the server buffer. You | 4948 see them when you enter the back end server in the server buffer. You |
4922 should not subscribe these groups! Unfortunately, these groups will | 4949 should not subscribe these groups! Unfortunately, these groups will |
4923 usually get @strong{auto-subscribed} when you use @code{nnmaildir} or | 4950 usually get @emph{auto-subscribed} when you use @code{nnmaildir} or |
4924 @code{nnml}, i.e. you will suddenly see groups of the form | 4951 @code{nnml}, i.e. you will suddenly see groups of the form |
4925 @samp{zz_mairix*} pop up in your group buffer. If this happens to you, | 4952 @samp{zz_mairix*} pop up in your group buffer. If this happens to you, |
4926 simply kill these groups with C-k. For avoiding this, turn off | 4953 simply kill these groups with C-k. For avoiding this, turn off |
4927 auto-subscription completely by setting the variable | 4954 auto-subscription completely by setting the variable |
4928 @code{gnus-auto-subscribed-groups} to @code{nil} (@pxref{Filtering New | 4955 @code{gnus-auto-subscribed-groups} to @code{nil} (@pxref{Filtering New |
4945 @code{nnmairix} groups (though I have no idea what happens if you do). | 4972 @code{nnmairix} groups (though I have no idea what happens if you do). |
4946 | 4973 |
4947 @item | 4974 @item |
4948 If you use the Gnus registry: don't use the registry with | 4975 If you use the Gnus registry: don't use the registry with |
4949 @code{nnmairix} groups (put them in | 4976 @code{nnmairix} groups (put them in |
4950 @code{gnus-registry-unfollowed-groups}). Be @strong{extra careful} if | 4977 @code{gnus-registry-unfollowed-groups}). Be @emph{extra careful} if |
4951 you use @code{gnus-registry-split-fancy-with-parent} - mails which are | 4978 you use @code{gnus-registry-split-fancy-with-parent}; mails which are |
4952 split into @code{nnmairix} groups are usually gone for good as soon as | 4979 split into @code{nnmairix} groups are usually gone for good as soon as |
4953 you check the group for new mail (yes, it has happened to me...). | 4980 you check the group for new mail (yes, it has happened to me...). |
4954 | 4981 |
4955 @item | 4982 @item |
4956 Therefore: @strong{Never ever} put ``real'' mails into @code{nnmairix} | 4983 Therefore: @emph{Never ever} put ``real'' mails into @code{nnmairix} |
4957 groups (you shouldn't be able to, anyway). | 4984 groups (you shouldn't be able to, anyway). |
4958 | 4985 |
4959 @item | 4986 @item |
4960 mairix does only support us-ascii characters. | 4987 mairix does only support us-ascii characters. |
4961 | 4988 |
4962 @item | 4989 @item |
4963 @code{nnmairix} uses a rather brute force method to force Gnus to | 4990 @code{nnmairix} uses a rather brute force method to force Gnus to |
4964 completely reread the group on the mail back end after mairix was | 4991 completely reread the group on the mail back end after mairix was |
4965 called - it simply deletes and re-creates the group on the mail | 4992 called---it simply deletes and re-creates the group on the mail |
4966 back end. So far, this has worked for me without any problems, and I | 4993 back end. So far, this has worked for me without any problems, and I |
4967 don't see how @code{nnmairix} could delete other mail groups than its | 4994 don't see how @code{nnmairix} could delete other mail groups than its |
4968 own, but anyway: you really should have a backup of your mail | 4995 own, but anyway: you really should have a backup of your mail |
4969 folders. | 4996 folders. |
4970 | 4997 |
4984 @code{zz_mairix-<NAME>-<NUMBER>}. You can change the prefix of | 5011 @code{zz_mairix-<NAME>-<NUMBER>}. You can change the prefix of |
4985 @code{nnmairix} groups by changing the variable | 5012 @code{nnmairix} groups by changing the variable |
4986 @code{nnmairix-group-prefix}. | 5013 @code{nnmairix-group-prefix}. |
4987 | 5014 |
4988 @item | 5015 @item |
4989 The following only applies if you @strong{don't} use the mentioned patch | 5016 The following only applies if you @emph{don't} use the mentioned patch |
4990 for mairix (@pxref{Propagating marks}): | 5017 for mairix (@pxref{Propagating marks}): |
4991 | 5018 |
4992 A problem can occur when using @code{nnmairix} with maildir folders and | 5019 A problem can occur when using @code{nnmairix} with maildir folders and |
4993 comes with the fact that maildir stores mail flags like @samp{Seen} or | 5020 comes with the fact that maildir stores mail flags like @samp{Seen} or |
4994 @samp{Replied} by appending chars @samp{S} and @samp{R} to the message | 5021 @samp{Replied} by appending chars @samp{S} and @samp{R} to the message |
15380 @code{t}, delete the files immediately, if @code{nil}, never delete any | 15407 @code{t}, delete the files immediately, if @code{nil}, never delete any |
15381 files. If a positive number, delete files older than number of days | 15408 files. If a positive number, delete files older than number of days |
15382 (the deletion will only happen when receiving new mail). You may also | 15409 (the deletion will only happen when receiving new mail). You may also |
15383 set @code{mail-source-delete-incoming} to @code{nil} and call | 15410 set @code{mail-source-delete-incoming} to @code{nil} and call |
15384 @code{mail-source-delete-old-incoming} from a hook or interactively. | 15411 @code{mail-source-delete-old-incoming} from a hook or interactively. |
15385 @code{mail-source-delete-incoming} defaults to @code{2} in alpha Gnusae | 15412 @code{mail-source-delete-incoming} defaults to @code{10} in alpha Gnusae |
15386 and @code{10} in released Gnusae. @xref{Gnus Development}. | 15413 and @code{2} in released Gnusae. @xref{Gnus Development}. |
15387 | 15414 |
15388 @item mail-source-delete-old-incoming-confirm | 15415 @item mail-source-delete-old-incoming-confirm |
15389 @vindex mail-source-delete-old-incoming-confirm | 15416 @vindex mail-source-delete-old-incoming-confirm |
15390 If non-@code{nil}, ask for confirmation before deleting old incoming | 15417 If non-@code{nil}, ask for confirmation before deleting old incoming |
15391 files. This variable only applies when | 15418 files. This variable only applies when |
28602 controls this. | 28629 controls this. |
28603 | 28630 |
28604 @item You can now drag and drop attachments to the Message buffer. | 28631 @item You can now drag and drop attachments to the Message buffer. |
28605 See @code{mml-dnd-protocol-alist} and @code{mml-dnd-attach-options}. | 28632 See @code{mml-dnd-protocol-alist} and @code{mml-dnd-attach-options}. |
28606 @xref{MIME, ,MIME, message, Message Manual}. | 28633 @xref{MIME, ,MIME, message, Message Manual}. |
28607 @c New in 5.10.9 / 5.11 (Emacs 21.1) | 28634 @c New in 5.10.9 / 5.11 (Emacs 22.1) |
28608 | 28635 |
28609 @item @code{auto-fill-mode} is enabled by default in Message mode. | 28636 @item @code{auto-fill-mode} is enabled by default in Message mode. |
28610 See @code{message-fill-column}. @xref{Various Message Variables, , | 28637 See @code{message-fill-column}. @xref{Various Message Variables, , |
28611 Message Headers, message, Message Manual}. | 28638 Message Headers, message, Message Manual}. |
28612 @c New in Gnus 5.10.12 / 5.11 (Emacs 22.3) | 28639 @c New in Gnus 5.10.12 / 5.11 (Emacs 22.3) |