Important Concepts

Fundamental af Commands

Other Ways to Deal With Messages

Commands for Mail Folder Management

How to Customise Af

Glossary and Indexes

Distribution

Af is free software; this means that everyone is free to use it and free to redistribute it on certain conditions. Af is not in the public domain; it is copyrighted and there are restrictions on its distribution, but these restrictions are designed to permit everything that a good cooperating citizen would want to do. What is not allowed is to try to prevent others from further sharing any version of af that they might get from you. The precise conditions are found in the GNU General Public License that comes with af and also appears following this section.

The simplest way to get a copy of af is from someone else who has it. You need not ask for permission to do so, or tell anyone you have done so; just copy it. If you have access to the Internet, you can get the latest version, or a patch to upgrade to the latest version, from the Af Home Page on the World Wide Web `http://www.thing.demon.co.uk/af', or by anonymous FTP from `ftp://ftp.csv.warwick.ac.uk/pub/mail/af'.

GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

Copyright © 1989, 1991 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA

Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software-- to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

1. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

   Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

2. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

   You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

3. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
   1. You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
   2. You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
   3. If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

   These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

   Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

   In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

4. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
   1. Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
   2. Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
   3. Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

   The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

   If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

5. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
6. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
7. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
8. If, as a consequence of a court judgement or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

   If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

   It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

   This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

9. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
10. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

    Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

11. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
12. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
13. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.

one line to give the program's name and an idea of what it does.
Copyright (C) 19yy  name of author

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
type `show w'.  This is free software, and you are welcome
to redistribute it under certain conditions; type `show c' 
for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright
interest in the program `Gnomovision'
(which makes passes at compilers) written 
by James Hacker.

signature of Ty Coon, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.

Introduction

You are reading about af, an advanced, self-documenting, customisable, real-time display-oriented mail reader and composer. If you think that sounds rather like the Emacs editor, you're correct; af is designed to follow the Emacs paradigm as closely as possible.

We say that af is display-oriented because normally the messages being read are visible on the screen and are updated automatically as you type your commands. See section Display.

We call it a real-time mail reader because the display is updated very frequently, usually after each character or pair of characters you type. This minimises the amount of information you must keep in your head as you process your mail. See section Basic af Commands.

We call af advanced because it provides facilities that go beyond simple reading of messages: viewing multiple mail folders at once, searching and sorting mailboxes, and dealing with groups of messages in one operation.

Similarly, we have tried to take care that af complies with any relevant standards: it conforms closely to RFC822, the Internet Standard for Mail Messages, and will work with such standard Mail Transfer Agents as UUCP, sendmail, and MMDF; and supports the POP3 protocol for reading mail from a remote server. Af also has good support for reading MIME mail, and limited support for composingl MIME mail, although this is still being improved. (1).

Self-documenting means that help about af is available from within af itself. You can find out what any command does, or find all the commands that are relevant to a topic. See section Help.

Customisable means that you can change the definitions of af commands in little ways. For example, if you prefer to include the text of the original message into the text of a reply to that message, then you can tell af to do so. Another sort of customisation is rearrangement of the command set. For example, if you prefer the four basic cursor motion commands (up, down, left and right) on keys in a diamond pattern on the keyboard, you can rebind the keys that way. See section Customisation.

Acknowledgements

Several people have contributed to af's development. Here's my chance to thank them for their efforts, and for an attempt at a moment of glory.

• Malc Arnold (malc@thing.demon.co.uk) conceived af, did the initial design work, wrote almost all of the code, and argued passionately in defence of the interface.
• Kay Dekker (kay@vide.coventry.ac.uk) did a vast amount of design work, discussing and arguing about features I should support and how the interface should work. More af features than I can readily recall were originally Kay's idea. He also wrote the manual pages and the first draft of the user manual, and showed great patience when struggling with some of the less stable versions of af.
• Ian "Vato" Dickinson (idickins@fore.com) actually suggested turning af into a full-featured mailer, and had a wealth of suggestions for features, some of which I've actually implemented. He also wrote the first draught of the POP3 and SMTP support code.
• Andrew "Vic" Fry (vic@pootug.demon.co.uk) has contributed insights about the af interface, as well as enough encouragement and coffee to keep me going. He has also ported and tested several versions of af.
• Justin Murdock (justin@vide.coventry.ac.uk), Dave Berry (daveb@harlequin.co.uk), Iain Bowen (alaric@harlech.demon.co.uk), and Onno van der Linden (onno@simplex.nl) have reported many bugs and suggestions for improving af.
• Emma Kemm (emma@thing.demon.co.uk) and Iain Bowen (alaric@harlech.demon.co.uk) proofread the manuals and supplied more much-needed moral support.
• Richard Stallman (rms@gnu.mit.edu) wrote the eleventh edition of the GNU Emacs manual, from which many parts of this manual have been derived. Thanks to the Free Software Foundation for permission to distribute this manual as a "derived work".

  Note that this does not imply any endorsement of af by the Free Software Foundation.

Bugs

Sometimes you will run into a bug in af. Although I can't promise that I can or will fix the bug, and I may not even agree that it is a bug, I want to hear about problems you encounter. Often I will agree that they are bugs and want to fix them.

If af should ever crash (ie fall over with an operating system error message), or exit back to the shell without warning, then it is certainly a bug. Commands doing the "wrong thing" are also bugs, but you should check the manual and help entry for the command carefully to be sure that the command isn't doing what it is supposed to.

If you think that you've found a bug, it is important to report it, and to provide enough information with the report to be useful. The most useful kind of bug report (except the fix for it) is an exact description of what commands you type, from entering af until the bug manifests. It may also help if you could include a small folder which triggers the bug, since many af bugs can be related to the data in the current folders. It is also important to tell me which version of af you are using, and what machine it is running on. You can find out which version of af you are using by typing M-x af-version RET.

At present, I am also interested in any feedback on af. If you have comments, praise, criticisms or complaints, then I'd like to hear it.

The best way to send bug reports or comments is to mail them electronically to the af maintainer at `af-bug@csv.warwick.ac.uk'. I don't promise to fix the problem; but if I agree that its a bug then I'll most likely want to fix it. And remember that the clearer your bug report is, the more likely it is that the bug will get fixed quickly, or indeed at all.

Future Developments

Af has now been released, but this doesn't mean that it is complete. There are several major enhancements that af could benefit from, some of which are loosely planned to be done at some time in the future.

• Internal support for composing non-textual MIME mail.
• Commands to allow you to use PGP conveniently with af. PGP stands for Pretty Good Privacy; it is a public-key encryption package written by Phil Zimmerman.
• Support for internationalising af, so that messages are displayed in the user's native language. I would need volunteers to actually do the translations.
• Major enhancements to the Afl language, allowing people to write their own extensions to af.
• An X interface with pull-down menus, scroll bars and mouse support.
• An additional major mode for reading news, similar to the mail mode but carefully tailored for convenient news-reading.
• Ports to other operating systems, such as MS-DOS or windows.

If you have any strong preferences about the direction af should take in the future, or suggestions of other enhancements you think I might like to consider, then please mail them to me at `af-bug@csv.warwick.ac.uk'.

1. An Introduction to Electronic Mail

Electronic mail (often known as e-mail, or simply mail), is the exchange of messages between people using computer networks. In this manual, when we say mail, we mean electronic mail. A mail message is a message which has been or will be sent via electronic mail. Again, when we say message in this manual, we are referring to a mail message.

When a mail message is sent, it is transmitted from one computer to another until it reaches the correct one. A message can be addressed to more than one person, in which case a separate copy of the message is sent to each person. Once a message has reached the machine to which it was addressed, then it is usually stored in the incoming mailbox of the person it is addressed to.

An incoming mailbox, or mailbox is simply a file containing mail messages, with a special sequence of characters separating each message from the others. Each user of a system will normally have their own mailbox. Users can also store messages in files of their own, which are called folders. In this manual, the term folder will refer to any file which contains mail messages.

To read your mail, you will usually use a mail reader, a program which can understand the format of a folder and present the contents to you in a convenient form. Af is an example of a mail reader. Similarly, you would normally send mail by using a mail composer, a program which knows how to construct and send a mail message, and gives the user a convenient environment in which to compose and send their message. Most mail readers, including af, are also mail composers.

To allow a mail message to be sent to the correct person, it needs an envelope. To supply this, a mail message is divided up into two parts, the headers and the body. The headers supply the information required to send the message to the right people, while the body is the actual message you wanted to send.

1.1 Mail Headers

The headers of a mail message are held at the beginning of the message, and are separated from the message body by a blank line. Here's an example of message headers:

From malc@thing.demon.co.uk Tue Jan 23 16:20:39 1996
Date: Tue, 23 Jan 1996 16:20:36 GMT
Message-Id: <4780.199201201539@thing.demon.co.uk>
From: Malc Arnold <malc@thing.demon.co.uk>
Organization: Team Limpid
Sender: The Management <root@thing.demon.co.uk>
To: Kay Dekker <kay@thing.demon.co.uk>,
    Andrew Fry <vic@pootug.demon.co.uk>
Subject: Af manual in progress
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Note that apart from the first line, each header consists of a header name, followed by a colon and then the header text. The first line is not really a header at all; it is the marker that most Unix systems insert to mark the start of each new message. You can also see that unlike the envelope for a postal letter, the envelope information contained in the header can also be of interest to the recipient. There are actually several other headers contained in most mail messages, but by default af will filter them out when it displays a message for you to read (see section Reading Messages).

Another interesting feature is the `To:' header, which has been extended over two lines by starting the second line with a tab. You can also continue headers in the same way by starting the following line with a space. Probably it's best to try to keep headers to a single line though; if a long header line needs to be folded like this, then af will normally do so for you.

Here is a brief summary of some of the headers you are likely to see in a mail message.

`From:'

The e-mail address of the person who the mail is from. Replies to the message will be sent to this address (see section Composing and Sending Mail). It is possible for a message to be from more than one person.

`Organization:'

The organisation the sender belongs to.

`Subject:'

A brief description of what the message is about.

`To:'

The e-mail addresses of the message's primary recipients.

`Cc:'

A "carbon copy" of the message was sent to the addresses listed. People listed in the `Cc:' header should regard the mail as being a copy for informational purposes.

`MIME-Version:'

Indicates that the message is a MIME message. See section The Message Body.

`Content-Type:'

What type of data the message contains. See section Content Type.

`Content-Transfer-Encoding:'

How the data has been encoded for transport via mail. See section Transfer Encoding.

1.2 Mail Addresses

Mail addresses usually take the form `user@full.domain.name'. They may also be written as `Full Name <user@full.domain.name>', or `user@full.domain.name (Full Name)'. In all of these cases, the address of the user is the same; the addition of the full name is simply a convenience to allow mail readers to display the person's full name rather then their e-mail address.

Usually, the part of the address to the left of the "@" character (`user') identifies the user to which the mail is to be sent, while the part to the right (`full.domain.name') identifies the specific computer or organisation where that user can be found. Note that while mail addresses must be unique, a user name may be duplicated many times by different organisations; each with a different full domain name.

Lists of addresses (such as in a `To:' header) should be separated either by spaces or commas.

We shall not go into the intimate details of mail address syntax here; af will check any addresses you give it, and either correct minor problems or report any serious errors in an address.

1.3 The Message Body

Normally, the body of a mail message is just text, which is not handled in any special way. Recently, electronic mail has been extended to allow for a message body which is something other than text. These extensions are called MIME (Multipurpose Internet Mail Enhancements), and mail which makes use of them is called MIME mail.

A MIME message uses the `Content-Type:' header to define the type of data the message contains. The `Content-Transfer-Encoding:' header describes how the data was encoded in order to be sent via mail. The `Content-Disposition:' header describes how a message should be handled when read. Finally the `Content-Description:' header can be used to describe the contents of a message.

1.3.1 Body Parts

A MIME message body may consist of more than one part. Each of these body parts is like a miniature MIME message in its own right, and has its own headers specifying the MIME details.

For example, a message might contain two body parts. The first is a description of the work you've been doing; the second is an image displaying the results of that work. You can see that the two parts of the message are related, but they must go into different body parts since they contain a different type of data.

Since we can think of a normal message as having one body part, when describing MIME mail it is conventional to talk about body parts rather than the message body. We will follow this convention in this manual.

1.3.2 Content Type

The body of a MIME mail message may be textual, or it may be an image or some other non-textual material. The type of the message body is specified by the `Content-Type:' header.

The form of a `Content-Type:' header is something like:

Content-Type: type/subtype [; parameter=value ... ]

The main type is separated from a subtype by a slash. The content type may be further refined by parameters, which are separated from the type and subtype, and from each other, by semicolons.

The content types you are likely to see in mail messages are:

`multipart'

The message body consists of a set of body parts. The `mixed' subtype indicates that the body parts may contain any content type. The `digest' subtype indicates that each body part is an entire mail message, which may itself be in MIME format. The `alternative' subtype indicates that each body part contains a different form of the same data, and only the "best" should be displayed. The `parallel' subtype indicates that the body parts should be displayed simultaneously if possible. Af can handle multipart messages internally.

`message'

The body part is itself a MIME message. The `rfc822' subtype indicates that the body part is an entire MIME message. Af is capable of handling such encapsulated messages internally.

The `partial' subtype indicates that the original message has been split into a number of smaller messages, presumably to avoid limits on the size of mail messages. Af can rebuild the original message from such partial messages, if all the parts of the original message have arrived intact.

`text'

The body part is textual. Although it may contain formatting information, it should be readable as it stands. The `plain' subtype means there is no formatting information; the text should be displayed as it stands.

The `charset' parameter indicates the character set the text is written in. Common values are `us-ascii' for plain ASCII text, and `iso-8859-1', which is suitable for Western European languages. See section Character Sets.

`image'

The body part is an image, in a format specified by the subtype, such as `image/gif' or `image/jpeg'. Af will call an external program to display `image' body parts.

`audio'

The body part is audio data, in a format specified by the subtype. Af will call an external program to display `audio' body parts.

`video'

The body part is video data, in a format specified by the subtype. Af will call an external program to display `video' body parts.

`application'

The body part is raw data for some application, often specified by the subtype. One common value is `application/octet-stream', which indicates that the body part contains raw data with no meaning attached. Hopefully the context will make it clear what you are to do with the data. Af will call an external program to display `application' body parts.

1.3.3 Character Sets

One of the commonest uses of MIME (in Europe at least) is to send mail which contains international characters (such as accents, or Cyrillic characters) which aren't in the us-ascii character set.

To allow these characters in a message, textual MIME messages can specify which character set they are written in with a `charset' parameter. The character set may be either `us-ascii' (the default), or one of the `iso-8859' character sets.

If your display is capable of displaying these character sets properly, Af can be set up so that it display's such messages properly by setting the variable viewable-charsets (see section Variables).

The person who installed af at your site may have already configured it to handle messages in the available character sets. In this case you don't need to do anything to make af handle internationalised messages correctly.

Sadly, none of these character sets is capable of displaying all the characters used in all the world's languages. So you may sometimes receive textual messages which you cannot read. The ISO-8859-1 character set, which is suitable for most Western European languages, is by far the most common character set used in MIME mail.

1.3.4 Transfer Encoding

Traditionally, the body of a mail message had to contain only plain text consisting of only ASCII characters, and much of the infrastructure which supports mail is only capable of transmitting such messages. For this reason, it may have been necessary to encode the contents of the message before they were send via mail. This encoding is specified by the `Content-Transfer-Encoding:' header.

The encodings that you may encounter in a MIME body part are:

`7bit'

The body part contains only short lines of 7 bit ASCII characters. No encoding has been applied.

`8bit'

The body part contains only short lines of 8 bit characters, not including the null character ASCII NUL. No encoding has been applied.

`binary'

The body part contains binary data, but has not been encoded. The electronic mail infrastructure is such that this encoding is unlikely to work.

`quoted-printable'

The body part has been encoded with the `quoted-printable' encoding. This encoding leaves ASCII characters untouched, but replaces international characters with sequences beginning with `='. It is intended for encoding text, since many characters will still be readable without decoding the message.

`base64'

The body part has been encoded with the `base64' encoding. This renders the body part completely unreadable, but is more compact than `quoted-printable' if the message contains a high proportion of non-ASCII characters. It is suitable for encoding binary data, such as images.

`x-uuencode'

`x-uue'

These encodings are not part of MIME at all. They represent the Unix `uuencode' encoding, which predates MIME. Some people send messages marked in this format, and af is able to handle them. These encodings are similar to `base64', but is not as robust. It is a bad idea to send messages encoded in this way except by prior arrangement with the recipient.

1.3.5 Content Disposition

Sometimes a body part isn't primarily intended to be read. It might be a program source file, or a configuration file. The `Content-Disposition:' header specifies whether a body part should be displayed inline when the message is read, or that it is an attachment, which requires confirmation before it is displayed.

You can also specify a file name in the `Content-Disposition:' header. Again, this is a hint to the recipient's mail reader that the body part should be stored in the named file if it is saved.

The form of a `Content-Disposition:' header is something like:

Content-Disposition: disposition [; filename=file ... ]

1.3.6 Content Description

Sometimes it can be useful to the recipient to have a textual description of a body part, especially if the body part contains something other than text. The `Content-Description:' header contains just that; a free text description of the contents of a body part.

1.4 Signatures

It is common for people to want to include a small amount of text at the end of each message, to give information such as their telephone number, paper-mail ("snail-mail") address, other e-mail addresses. and so on.

To aid people in doing this, af supports a feature known as signature files. These files contain text which will automagically be included at the end of each mail message you send. By default, af's uses the file .signature in your home directory as your signature file.

Some people also like to include lengthy quotations, large ASCII graphics or other amusements in signature files. This annoys many people on the net, since it costs money to transfer large signatures, and conveys no useful information. Because of this, the version of af which you use may be configured to truncate signature files that are larger than a certain size; typically 4 lines of 79 columns each. You have been warned.

2. The Organization of the Screen

Normally, the af display occupies the whole screen. When you start af, the entire screen except for the last line is devoted to the folder you are reading. This area is called the window. The last line is a special echo area or minibuffer window where prompts appear and where you can enter responses. You can subdivide the window into different windows, each of which can be used to display a different folder (see section Multiple Windows). In this manual, the word "window" always refers to the subdivisions of the screen within af.

The window that the arrow cursor is in is the selected window, in which most operations take place. Most af commands implicitly apply to the messages in the selected window. The other windows display messages for reference only, unless/until you select them.

Most windows display the details of folders, showing a header line for each message in the folder. Each header line shows a brief summary of the message's details, and is treated as a pointer to the message it describes.

Each window's last line is a mode line which describes what is going on in that window. It contains text that starts like `==== Af: something'. Its purpose is to indicate what buffer is being displayed above it in the window above it, how many messages are in the buffer, whether the buffer contains unsaved changes, and so on.

2.1 Point

Within a buffer displaying a folder, an arrow pointer shows the location at which commands will take effect. This location is called point. Many af commands move point through the buffer, so that you can execute commands at different places in it.

While the arrow appears to point at a message, you should think of point as between two messages; it lies before the message that it is pointing at. Sometimes people speak of "the cursor" when they mean "point", or speak of commands that move point as "cursor motion" commands.

If you are reading several folders in af, each in its own buffer, each buffer has its own point location. A buffer that is not currently displayed remembers where point is in case you display it again later.

When there are multiple windows on the screen, each window has its own point location. The arrow shows the location of point in the selected window. This also is how you can tell which window is selected. If the same buffer appears in more than one window, each window has its own position for point in that buffer.

It is possible to move point past the last message in a buffer. This is deliberate, to allow several other commands to work properly in an "Emacs-like" way. While it may seem strange at first if you are used to other mail readers, it soon becomes familiar; and it allows you to use many af features much more easily. Most commands that deal with messages will report an error if you have moved point past the last message in the buffer, just as they would if there were no messages at all.

2.2 The Echo Area

The line at the bottom of the screen (below the mode line) is the echo area. It is used to display small amounts of text for several purposes.

Echoing means displaying the characters that you type. Outside af, the operating system normally echoes all your input. Inside af things work a little differently.

Single-character commands do not echo in af, and multi-character commands echo only if you pause while typing them. As soon as you pause for more than a second in the middle of a command, af echoes all the characters of the command so far. This is to prompt you for the rest of the command. Once echoing has started, the rest of the command echoes immediately as you type it. This behaviour is designed to give confident users fast response, while giving hesitant users maximum feedback. You can change this behaviour by setting the variable echo-keystrokes (see section Variables).

If a command cannot be executed, it may print an error message in the echo area. Error messages are accompanied by a beep.

Some commands print informative messages in the echo area. These messages look much like error messages, but they are not announced with a beep. Sometimes the message tells you what the command has done, when this is not obvious from looking at the screen. Sometimes the sole purpose of a command is to print a message giving you specific information--for example, C-x = prints a message describing the position of point in the buffer. Commands that take a long time often display messages ending in `...' while they are working, and add `done' at the end when they are finished.

The echo area is also used to display the minibuffer, a window that is used for reading arguments to commands, such as the name of a file to be read. When the minibuffer is in use, the echo area begins with a prompt string that usually ends with a colon; also, the cursor appears in that line because it is the selected window. You can always get out of the minibuffer by typing C-g (see section The Minibuffer).

2.3 The Header Lines

Most of the lines in a window which displays a folder will be header lines, which present a one-line summary of a mail message. By default a header line will look something like this:

ptr tags  originator                  subject

ptr is the pointer which indicates the position of point in the window; the ptr will be represented as `=>' only on the line that point lies before, and as blank on all other lines. The line on which the pointer is present is sometimes referred to as the current line, and the message it represents as the current message, or the message at point.

tags are the tags of the message. Normally, this will only show system tags which af sets to show information about a message's status (see section Tags).

originator is the sender of the message. If the sender's real name is available in the message headers then it will be shown here, otherwise their e-mail address will be displayed.

subject is the subject of the message.

It is possible to change the layout of the header lines by setting the variable header-line-format (see section Variables). Also, the arrow pointer can be changed by setting the variable header-line-arrow.

2.4 The Mode Line

Each window's last line is a mode line which describes what is going on in that window. When there is only one window, the mode line appears right above the echo area. The mode line starts and ends with dashes, and it contains text like `Af: something'.

Normally, the mode line looks like this:

=ch= Af: buf == count == (modes) == pos =

This gives information about the buffer being displayed in the window: the buffer's name, what modes are in use, whether the buffer has been changed, and how far down the buffer you are currently looking.

ch contains two stars `**' if the buffer has been changed (the buffer is "modified"), two plus signs `++' if the buffer contains messages whose status has changed, or `==' if the buffer has not been changed. For a read-only buffer, it is `%*' if the buffer is modified, and `%%' otherwise.

buf is the name of the window's buffer. In most cases this is the same as the name of a folder you are processing. (see section Using Multiple Buffers)

count is the number of messages in the window's buffer.

The buffer displayed in the selected window (the window that the arrow cursor is in) is also af's selected buffer, the one that most commands operate on. When we speak of what some command does to "the buffer", we are talking about the currently selected buffer.

pos tells you whether there are more messages above the top of the window, or below the bottom. If your buffer is small and it is all visible in the window, pos is `All'. Otherwise, it is `Top' if you are looking at the beginning of the buffer, `Bot' if you are looking at the end of the buffer, or `nn%', where nn is the percentage of the buffer above the top of the window.

modes lists the major mode and any minor modes which are in effect in the buffer. At any time, each buffer is in one and only one of the possible major modes. The major modes available include Mail mode (for reading folders), Typeout mode (for displaying information) and Minibuffer mode (for asking the user for input). Each major mode may be supplemented by one or more minor modes, which change the mode's behaviour in some small way. (see section Major Modes).

It is possible to change the layout of the mode line by setting the variable mode-line-format (see section Variables).

3. Characters, Keys and Commands

ASCII consists of 128 character codes. Some of these codes are assigned graphic symbols such as `a' and `='; the rest are control characters, such as Control-a (usually written C-a for short). C-a gets its name from the fact that you type it by holding down the CTRL key while pressing a.

Some control characters have special names, and special keys you can type them with: for example, RET, TAB, LFD, DEL and ESC. The space character is usually referred to below as SPC, even though strictly speaking it is a graphic character whose graphic happens to be blank.

On ASCII terminals, there are only 32 possible control characters. These are the control variants of letters and `@[]\^_'. In addition, the shift key is meaningless with control characters: C-a and C-A are the same character, and af cannot distinguish them.

One af character set extension is that characters have an additional modifier, called Meta. Every character has a Meta variant; examples include Meta-a (normally written M-a, for short), M-A (not the same character as M-a, but those two characters normally have the same meaning in af), M-RET, and M-C-a. For reasons of tradition, we usually write C-M-a rather than M-C-a; logically speaking, the order in which the modifier keys CTRL and META are mentioned does not matter.

Some terminals have a META key, and allow you to type Meta characters by holding this key down. Thus, Meta-a is typed by holding down META and pressing a. The META key works much like the SHIFT key. Such a key is not always labelled META, however, as this function is often a special option for a key with some other primary purpose.

If there is no META key, you can still type Meta characters using two-character sequences starting with ESC. Thus, to enter M-a, you could type ESC a. To enter C-M-a, you would type ESC C-a. ESC is allowed on terminals with META keys, too, in case you have formed a habit of using it.

ASCII terminals represent function keys as a special sequence of ASCII characters. Because of this, it is possible, although not simple, to configure af to handle function and arrow keys. (see section Customisation)

3.1 Keys

A key sequence (key, for short) is a sequence of characters that are meaningful as a unit--as "a single command." Some af command sequences are just one character; for example, just C-n is enough to move down one line. But af also has commands that take two or more characters to invoke.

If a sequence of events is enough to invoke a command, it is a complete key. Examples of complete keys include C-n, RET, C-x C-f and C-x 4 C-f. If it isn't long enough to be complete, we call it a prefix key. The above examples show that C-x and C-x 4 are prefix keys. Every key sequence is either a complete key or a prefix key.

Many single characters constitute complete keys in the standard af command bindings. A few of them are prefix keys. A prefix key combines with the following character to make a longer key sequence, which may itself be complete or a prefix. For example, C-x is a prefix key, so C-x and the next character combine to make a two-character key sequence. Most of these key sequences are complete keys, including C-x C-f and C-x b. A few, such as C-x 4 and C-x r, are themselves prefix keys that lead to three-character key sequences. There's no limit to the length of a key sequence, but in practice people rarely use sequences longer than four characters.

By contrast, you can't add more characters onto a complete key. For example, the two-character sequence C-n C-k is not a key, because the C-n is a complete key in itself. It's impossible to give C-n C-k an independent meaning as a command. C-n C-k is two key sequences, not one.

All told, the prefix keys in af are C-h, C-t, C-x C-x 4, and ESC. But this is not cast in concrete; it is just a matter of af standard key bindings. If you customise af, you can make new prefix keys, or eliminate these (see section Customising Key Bindings).

If you do make or eliminate prefix keys, that changes the set of possible key sequences. For example, if you redefine C-n as a prefix, C-n C-k automatically becomes a key (complete, unless you define it too as a prefix). Conversely, if you remove the prefix definition of C-x 4, then C-x 4 f (or C-x 4 anything) is no longer a key.

3.2 Keys and Commands

This manual is full of passages that tell you what particular keys do. But af does not assign meanings to keys directly. Instead, af assigns meanings to named commands, and then gives keys their meanings by binding them to commands.

Every command has a name chosen by a programmer. The name is usually made of a few English words separated by dashes; for example, next-line or open-message. The bindings between keys and commands are recorded in various tables called keymaps (see section Customising Key Bindings).

When we say that "C-n moves down vertically one line" we are glossing over a distinction that is irrelevant in ordinary use but is vital in understanding how to customise af. It is the command next-line that is programmed to move down vertically. C-n has this effect because it is bound to that command. If you rebind C-n to the command end-of-buffer then C-n will move to the end of the buffer instead. Rebinding keys is a common method of customisation.

In the rest of this manual, we usually ignore this subtlety to keep things simple. To give the information needed for customisation, we state the name of the command which really does the work in parentheses after mentioning the key that runs it. For example, we will say that "The command C-n (next-line) moves point vertically down," meaning that next-line is a command that moves vertically down and C-n is a key that is standardly bound to it.

While we are on the subject of information for customisation only, it's a good time to tell you about variables. Often the description of a command will say, "To change this, set the variable foobar." A variable is a name used to remember a value. Most of the variables documented in this manual exist just to facilitate customisation: some command or other part of af examines the variable and behaves differently according to the value that you set. Until you are interested in customising, you can ignore the information about variables. When you are ready to be interested, read the basic information on variables, and then the information on individual variables will make sense (see section Variables).

3.3 Major Modes

Af has several modes of operation; known as major modes. A major mode is in effect a subset of af, where a command may have a different effect, and different commands may be available (This is probably the most pronounced difference between af and Emacs; Emacs major modes just alter its behaviour in minor ways, such as changing key bindings; while af major modes may have a completely different set of commands and behaviour).

There are three major modes currently available in af. Mail mode is the mode used for buffers displaying mail messages; most af buffers use mail mode. Minibuffer mode is used to support the minibuffer; it has no commands to handle mail messages, but many extra commands to allow editing of text. Typeout mode is the mode used for displaying text to the screen. Again, it has no commands to handle mail messages, it simply allows you to browse text displayed on the screen.

Each major mode allows you to bind keys independently of the other major modes (just like in Emacs), so keys may be bound in only one mode, or even be bound to different things in different modes (just as they can in Emacs). For example, in mail mode SPC just clears the echo area, in minibuffer mode it inserts a space into the text you are editing, and in typeout mode it scrolls the text up to display the next page.

Each af command may be available in all modes, or just in some of them. For example the command open-message is only available in mail mode, since in the other modes you are not dealing with mail messages and the command wouldn't make sense. So you can't run the command open-message in typeout mode even by typing M-x open-message.

A command may also have slightly different behaviour in different modes. For example the command search-forward in mail mode searches through the text of each mail message, looking for some text. In typeout mode it searches through the text you are viewing instead.

This distinction is only really important when customising af; when you are using af it is (hopefully) quite obvious what commands are likely to work. The important thing to remember is that keys may do very different things depending on whether you are browsing a list of messages, entering an argument in the minibuffer, or viewing text.

3.4 Minor Modes

A minor mode is a particular feature which can be turned on or off. For example, Read Only mode selects whether you are allowed to modify the contents of a buffer. Unlike the major modes, the minor modes are independent of each other, although they may only be valid in some major modes.

Minor modes are usually specific to a buffer, so they may be turned on in some buffers and off in others. Normally, minor modes are turned on or off automatically in response to some situation. There may also be a command to turn the minor mode off if it is on, or on if it is off; this will be formed from the prefix `toggle-' followed by the name of the mode. So the command to turn Read Only mode on or off is toggle-read-only.

4. Entering Af

The usual way to invoke af is with the shell command `af'. Af clears the screen and then displays an initial help message and copyright notice while it processes any startup files (see section The Startup File, `~/.afrc'), and then reads your incoming mailbox. (If your mailbox is small, you may not see the initial help message and copyright; it would be very inconvenient for experienced users if af were to pause long enough to let you read the message.) When af has finished reading the mailbox, it displays a final count of how many messages it read, and displays the buffer containing the messages.

Some operating systems discard all type-ahead when af starts up; they give af no way to prevent this. Therefore, it is advisable to wait until af clears the screen before typing your first command.

It is possible to specify folders to be visited, or details of a message you want to send, by giving af arguments in the shell command line (see section Command Line Arguments). But you can do these things from within af too; whether you run af once and suspend it, or separately each time you want to read or send mail is simply a matter of taste.

Arguments starting with `-' are options. Other arguments specify addresses to send mail to. If you specify addresses (or use any of the `-c', `-b', or `-E' options), then af doesn't read any folders; it simply allows you to send a single mail message to the addresses you supplied, and then exits.

You can use options to specify various other things, such as which folders to read, the subject for mail you're sending, and so on. A few options support advanced usage, such as running afl functions in batch mode. The sections of this chapter describe the available options, arranged according to their purpose.

Most options specify how to initialise af, or set parameters for the af session. We call them initial options. A few options specify things to do: for example, read folders or load afl programs (see section Afl). These are called action options. These and file names together are called action arguments. Af processes all the action arguments in the order they are written.

4.1 Command Line Arguments

Here is a table of the arguments and options that af accepts:

`address'

Send mail to address. See section Composing and Sending Mail. If addresses are supplied, then many of the other arguments are disabled, since af will not be visiting any folders. If the standard input is not a terminal, then af will silently send the message as requested, rather than expecting you to edit the text of the message.

`-E'

This option has two effects. Firstly, it makes af start up to send a single mail message even if no addresses were given as arguments. Secondly, it forces af to allow you to edit the text of the message you send, even if the text is being obtained from the standard input. This doesn't really seem very useful, but occasionally it can be very handy in allowing you to write flexible scripts which send mail using af.

`-H'

Force af to present the user with the headers of an outgoing message when editing it, or to force translation of headers in mail sent from the standard input. In effect, it causes af's edit-initial-headers variable to be set to true regardless of the contents of the user's `.afrc' file (see section Variables).

`-c cc'

Specifies one or more addresses to send a carbon copy of a message to. If the addresses contain spaces then you should enclose them in double quotes.

`-b bcc'

Specifies one or more addresses to send a blind carbon copy of a message to. If the addresses contain spaces then you should enclose them in double quotes.

`-s subject'

Specifies the Subject: for an outgoing message. Only one `-s' option may be given, and it only takes effect if addresses (or the `-c', `-c', or `-E' option) were given on the command line. If the subject contains spaces then you should enclose it in double quotes.

`-C content-type'

Specifies the MIME Content-Type: for an outgoing message. Only one `-C' option may be given, and it only takes effect if addresses (or the `-E' option) were given on the command line.

`-f folder'

Read folder in place of your incoming mailbox. Multiple `-f' options may be given, in which case each folder is read into its own buffer. This option is ignored if addresses or the `-E' option were given.

`-u user'

Read user's incoming mailbox in place of your own. You must have permissions to read user's mailbox. Multiple `-u' options may be given, and they may be mixed with `-f' options. This option is ignored if addresses or the `-E' option were given.

`-F'

Interpret any arguments other than options as folders to be read in, rather than addresses to send mail to. This can be very useful if you want to read in a set of folders with `af -F *'.

`-w'

Create enough windows to display all the folders given with the `-f', `-u' or `-F' options, subject to the maximum number of windows that will fit on the screen (usually about four on a 24-line display). This option is ignored if addresses or the `-E' option were given.

`-e'

Check whether there is mail in your default mailbox (or, if `-f' or `-u' are given, any specified mailboxes) and then exit. The exit status is zero if there is mail in any of the mailboxes; one if not. This option is ignored if addresses or the `-E' option were given.

`-z'

Makes af terminate immediately with an exit status of 1 if your incoming mailbox (or, if `-f' or `-u' are given, any specified folders) is empty. Otherwise, af will start up normally. This option is ignored if addresses or the `-E' option were given.

`-n'

Ignore the file `.afrc' in the user's home directory. See section The Startup File, `~/.afrc'.

`-v'

Prints the version of af and then exit. Ignores the effect of any other options.

`-l loadfile'

Specifies a file which should be read and executed on startup before any buffers are created. Used with the `-n' option, this allows the user to specify an alternate startup file, rather than the default of `.afrc' in their home directory.

`-S file'

Names a file of commands in af's internal language afl. The commands in the file are read and executed exactly as if af had been started up interactively and then the af command load-file had been executed. When all the commands in file have been executed, or if an error is encountered in the file, then af terminates. If the `-S' option is given, then af will not display the screen; only messages will be printed to the standard output. Only one `-S' option may be given, it is ignored if destinations or the `-E' option were specified.

4.2 Command Line Examples

Here are a few examples of af command line usage, with brief explanations.

Read two folders `foo' and `bar' into separate windows:

af -f foo -f bar -w

Check if there is any mail in folders foo and bar:

af -e -f foo -f bar

Send mail to `fred' on the local system with subject `Hi':

af -s Hi fred

Take a current directory listing, and use it as a base for some mail to user `fred@foobar.co.uk':

ls -l | af -E fred@foobar.co.uk

Run the afl script in file `script.afl' with folder `foobar' as the default buffer:

af -S script.afl -f foobar

4.3 Environment Variables

Af uses several environment variables. An environment variable is a string passed from the operating system to af, and the collection of environment variables is known as the environment. Environment variable names are case sensitive and it is conventional to use upper case letters only.

Because environment variables come from the operating system there is no general way to set them; it depends on the operating system and especially the shell that you are using. For example, here's how to set the environment variable ORGANIZATION to `Utter Chaos' using bash:

export ORGANIZATION="Utter Chaos"

and here's how to do it in csh or tcsh:

setenv ORGANIZATION "Utter Chaos"

It should be noted that the environment variables are used to customise af, not to configure it. None of these variables are required; and af should work correctly without them. They simply serve to tailor af to your taste.

Here is a list of the environment variables af uses, with a brief description of what they are used for.

MAIL

The full path to your incoming mailbox.

HOME

Your home directory.

FOLDER

The directory where your mail folders are stored. Defaults to `~/Mail'.

SAVEDIR

The directory where your news folders are stored. Defaults to `~/News'.

TMPDIR

The directory where temporary files should be created.

VISUAL, EDITOR

The editor to use for editing outgoing mail (or messages if you choose to edit them). VISUAL overrides EDITOR if they are set to different values.

PAGER

The program to use when you ask af to display a message via an external pager.

NAME

Your real name. Used for generating the headers on the messages you send.

ORGANIZATION

your organisational affiliation. If set, af will generate an Organization: header on the messages you send.

4.4 Exiting af

There are two commands for exiting af because there are two kinds of exiting: suspending af and killing af.

Suspending means stopping af temporarily and returning control to its parent process (usually a shell), allowing you to resume reading mail later in the same af job, with the same buffers, same kill ring, and so on.

Killing af means destroying the af job. You can run af again later, but you will get a fresh af; there is no way to resume the same mail reading session after it has been killed.

C-z

Suspend af (suspend-af)

C-x C-c

Kill af (save-buffers-kill-af).

M-z

Kill af, automatically saving any changed buffers (save-all-kill-af).

To suspend af, type C-z (suspend-af). This takes you back to the shell from which you invoked af. You can resume af with the shell command `%af' in most common shells.

On systems that do not support suspending programs, C-z starts an inferior shell that communicates directly with the terminal (shell). Af waits until you exit the inferior shell. (The way to do that is probably with C-d or `exit', but it depends on which shell you use). The only way on these systems to get back to the shell from which af was run (to log out, for example) is to kill af.

To kill af, type C-x C-c (save-buffers-kill-af). A two-character key is used for this to make it harder to type. This command first offers to save any modified file-visiting buffers. If you do not save them all, it asks for confirmation with yes before killing af, since any changes not saved will be lost forever.

To kill af, saving all modified file-visiting buffers, type M-z (save-all-kill-af). We don't recommend using this, since you might accidentally save changes you didn't mean to, but you can use M-z to exit if you prefer.

The operating system usually listens for certain special characters whose meaning is to kill or suspend the program you are running. This operating system feature is turned off while you are in af. The meanings of C-z and C-x C-c as keys in af were inspired by the use of C-z and C-c on several operating systems as the characters for stopping or killing a program, but that is their only relationship with the operating system. You can customise these keys to run any commands of your choice (see section Customising Key Bindings).

5. Basic af Commands

We now give the basics of how to read, save, and delete messages, send mail to people and save your changes back to your mailbox.

5.1 Reading Messages

The most basic operation in af is to open the current message; to display it's contents via typeout (see section Typeout), or some other pager.

RET or C-o

Open the current message, using the pager named in the pager variable, usually `typeout' (open-message).

M-RET or C-M-o

Open the current message, using the pager named in the PAGER environment variable (page-message).

C-x C-o

Open the current message, displaying all the headers and the message body using the pager named in the pager variable. The body is not decoded, and multipart or partial messages are not processed in any way. (open-raw-message).

Normally, only mail headers not listed in the headers-not-displayed variable will be displayed when you open a message. A positive numeric argument makes af display all the message's headers. A negative argument makes af skip all headers, and only display the body of the message. See section Numeric Arguments, for more information on numeric arguments.

When you open a multipart message, the headers and each textual body part will be displayed to a separate section of typeout. Non-textual body parts will be displayed using an external program if possible, otherwise you will be asked whether to view the text of the body part, save it to a file, pipe it into a command, or skip it. If any body part is an attachment, then af will offer you the choice of viewing, saving or skipping that body part.

Normally, af will ask for confirmation before it displays image, audio, video or application body parts, even if it knows how to. The confirm-viewing variable controls this, listing the content types which af will ask for confirmation before displaying.

When you open a partial message, af will try to rebuild and display the entire original message. If af can't rebuild the message then it will warn you about the problem, and offer you the choice of viewing or skipping that part of the message.

If your external pager doesn't need af to pause after displaying the message; then you can make reading messages more convenient by setting the variable pause-after-paging-message to true.

5.2 Changing the Location of Point

To do anything useful with af, you have to know how to move point (see section Point). There are several keys which move point within a buffer.

C-n or n

Move down one line, vertically (next-line).

C-p or p

Move up one line, vertically (previous-line).

M-.

Move point to the vertical centre of the window. (move-to-window-line). Text does not move on the screen.

A numeric argument says which screen line to place point on. It counts screen lines down from the top of the window (zero for the top line). A negative argument counts lines from the bottom (-1 for the bottom line).

M-< or <

Move to the top of the buffer (beginning-of-buffer). With numeric argument n, move to n/10 of the way from the top. See section Numeric Arguments, for more information on numeric arguments.

M-> or >

Move to the end of the buffer (end-of-buffer).

M-g

Read a number n and move point to line number n (goto-line). Line 1 is the beginning of the buffer.

5.3 Scrolling

Since only part of a large buffer fits in the window, af tries to show the part that is likely to be interesting. The display control commands allow you to specify which part of the buffer you want to see.

C-l

Clear screen and redisplay, scrolling the selected window to center point vertically within it (recenter). A numeric argument n says to move point to screen line n.

C-v

Scroll forward (a windowful or a specified number of lines) (scroll-up).

M-v

Scroll backward (scroll-down).

The names of all scroll commands are based on the direction that the messages move in the window. Thus, the command to scroll forward is called scroll-up, since the messages move up.

When scrolling a windowful at a time, af leaves two lines that were visible before you scrolled still visible afterwards, so that you can retain the context you were in before you scrolled. The number of lines of overlap across a C-v or M-v is controlled by the variable next-screen-context-lines; by default, it is two.

5.4 Deleting Messages

C-k or k

Kill the current message, removing it from the folder (kill-line). See section Killing and Yanking.

M-x delete-message

Mark the current message as deleted. This doesn't actually delete the message until you save the buffer. At that point any messages marked as deleted will be killed, and not written to the folder.

M-x undelete-message

Remove the deleted marker from the current message; so that it will not be killed when you save the buffer.

5.5 Message and Position information

Here are commands to get information about messages, and your position in the buffer.

M-=

Print line number of point in the buffer (what-cursor-position).

C-x =

Print a short summary of some of the message's details in the echo area (message-info).

C-t ?

Print the message's tags in the echo area (message-tags). See section Tags.

5.6 Quitting

At any time in af except when a command is running, you can type C-g (keyboard-quit) to quit from what you are doing. If you have typed part of a command, or a numeric argument, then C-g will get rid of it. If there isn't a partial command to get rid of, but you are in the minibuffer or typeout then typing C-g will exit back to the mail buffer, aborting the command you were running.

This means, that you can always get back to the top level of af by typing C-g C-g. This is useful for aborting commands, or if you are unsure where you are in af.

5.7 Help

If you forget what a key does, you can find out with the Help character, which is C-h. Type C-h k followed by the key you want to know about; for example, C-h k C-n tells you all about what C-n does. C-h is a prefix key; C-h k is just one of its subcommands (the command describe-key). The other subcommands of C-h provide different kinds of help. Type C-h three times to get a description of all the help facilities. (see section Help).

5.8 Numeric Arguments

Any af command can be given a numeric argument (also called a prefix argument), although it may be ignored. Some commands interpret the argument as a repetition count. For example, C-n with an argument of ten moves down ten lines instead of one. With these commands, no argument is equivalent to an argument of one. Negative arguments tell most such commands to move or act in the opposite direction.

If your terminal keyboard has a META key, the easiest way to specify a numeric argument is to type digits and/or a minus sign while holding down the META key. For example,

M-5 C-n

would move down five lines. The characters Meta-1, Meta-2, and so on, as well as Meta--, do this because they are keys bound to commands (digit-argument and negative-argument) that are defined to contribute to an argument for the next command.

Another way of specifying an argument is to use the C-u (universal-argument) command followed by the digits of the argument. With C-u, you can type the argument digits without holding down modifier keys; C-u works on all terminals. To type a negative argument, type a minus sign after C-u. Just a minus sign without digits normally means -1.

C-u followed by a character which is neither a digit nor a minus sign has the special meaning of "multiply by four". It multiplies the argument for the next command by four. C-u twice multiplies it by sixteen. Thus, C-u C-u C-n moves down sixteen lines. This is a good way to move down "fast", since it moves about 2/3 of a screen in the usual size screen. C-u is also a handy way of providing an argument when you don't care about the value.

Many commands care only about whether there is an argument, and not about its value. Other commands care only about the sign of the argument. For example, the command RET (open-message) with no argument shows only some of the message's headers; with a positive argument, it shows all the headers, and with a negative argument it shows no headers at all. This may seem strange, but it is a convenient way of modifying the behaviour of a command.

We use the term "prefix argument" as well as "numeric argument" to emphasise that you type the argument before the command, and to distinguish these arguments from minibuffer arguments that come after the command.

6. Typeout

Typeout is the mode af uses to display large amounts of text such as mail messages or help information. When af uses typeout, the typeout window appears, covering the entire screen apart from the echo area. Once you exit typeout, the window disappears, "uncovering" the original windows.

If possible, each line of the text is displayed as a single line on the screen. If a line is too long to fit on a single screen line, then it will be displayed on several screen lines, with a `\' at the extreme right margin of all but the last of them. The `\' says that the following screen line is not really a distinct line in the text, but just the continuation of a line too long to fit the screen. This is called line wrapping, and the lines after the first are often referred to as continuation lines.

When you are viewing typeout, the position indicator in the mode line will often say `MOR'. This is because typeout does not wait to read the entire input before displaying the first page, and since af doesn't know how many lines there are in the text yet, it will give the position as `MOR' to indicate this.

Most of the time, typeout consists of a single section. But when typeout is displaying related outputs, such as the body parts of a multipart message, typeout will consist of several sections. Each section of typeout will be displayed separately.

Sometimes, the typeout window will appear, but you will still be able to carry on with some other operation (such as displaying the help options via C-h C-h C-h). In these cases the typeout window will disappear when the operation is completed.

Within typeout, only the cursor motion commands, the scrolling commands and the text searching commands can be used. To exit typeout, simply type C-g. The other af commands are irrelevant when you are just viewing text. Here is a brief summary of the commands available in typeout:

SPC

Scroll the text up to show the next page of text. If you are already at the end of the text, then exit typeout (typeout-scroll). This is a convenient way of paging through short amounts of text.

C-v

Scroll forward (a windowful, or a specified number of lines) (scroll-up).

M-v

Scroll backward (a windowful, or a specified number of lines) (scroll-down).

C-n or n

Scroll forward one line (next-line).

C-p or p

Scroll backward one line (previous-line).

C-] or ]

Move to the next typeout section (next-section).

C-[ or [

Move to the previous typeout section (previous-section).

C-l

Redraw the display (recenter).

C-s regex RET

Search forward through the text for a line matching regex (search-forward). See section Searching Mail Folders.

C-r regex RET

Search backward through the text for a line matching regex (search-forward). See section Searching Mail Folders.

7. The Minibuffer

The minibuffer is the facility used by af commands to read arguments more complicated than a single number. Minibuffer arguments can be file names, buffer names, af command names, address lists, and many other things, depending on the command reading the argument. You can use many editing commands in the minibuffer to edit the argument.

When the minibuffer is in use, it appears in the echo area, and the terminal's cursor moves there. The beginning of the minibuffer line displays a prompt which says what kind of input you should supply and how it will be used. Often this prompt is derived from the name of the command that the argument is for. The prompt normally ends with a colon.

Sometimes a default argument appears in parentheses after the colon; it too is part of the prompt. The default will be used as the argument value if you enter an empty argument (e.g., just type RET). For example, commands that read buffer names always show a default, which is the name of the buffer that will be used if you type just RET.

The simplest way to enter a minibuffer argument is to type the text you want, terminated by RET which exits the minibuffer. You can cancel the command that wants the argument, and get out of the minibuffer, by typing C-g.

Sometimes, a default response will already be in the minibuffer when you enter it. If it is completely wrong, then you can type C-a C-k to remove it. These default responses appear for convenience when you are prompted for a long value that you are likely to want to edit, rather then retype from scratch.

Most commands which use typeout allow you to redirect the output into a file, instead of viewing it. The major exception to this is RET (open-message), since there are several ways to save a message to a file. To redirect typeout to a file simply give the command a prefix argument of any value; you will be prompted for the file name using the minibuffer.

7.1 Echo Area Conflicts

Since the minibuffer uses the screen space of the echo area, it can conflict with other ways af customarily uses the echo area. Here is how af handles such conflicts:

• If a command gets an error while you are in the minibuffer, this does not cancel the minibuffer. However, the echo area is needed for the error message and therefore the minibuffer itself is hidden for a while. It comes back after a few seconds, or as soon as you type anything.
• If in the minibuffer you use a command whose purpose is to print a message in the echo area, such as C-x =, the message is printed normally, and the minibuffer is hidden for a while. It comes back after a few seconds, or as soon as you type anything.
• Echoing of keystrokes does not take place while the minibuffer is in use.

7.2 Inserting Text

To insert printing characters into the minibuffer, just type them. This inserts the characters you type into the buffer at the cursor (that is, at point; which has a different appearance in the minibuffer, but the same meaning). The cursor moves forward, and any text after the cursor moves forward too. If the text in the buffer is `foobar', with the cursor before the `b', then if you type xx, you get `fooxxbar', with the cursor still before the `b'. This all works because in the minibuffer all the printing characters run the command self-insert-command.

Direct insertion works for printing characters and SPC, but other characters act as editing commands and do not insert themselves. If you need to insert a control character or a character whose code is above 200 octal, you must quote it by typing the character C-q (quoted-insert) first. There are two ways to use C-q:

• C-q followed by any non-graphic character (even C-g) inserts that character.
• C-q followed by three octal digits inserts the character with the specified character code.

A numeric argument to C-q specifies how many copies of the quoted character should be inserted (see section Numeric Arguments).

When you have finished entering the text, simply type RET (newline) to accept the argument and exit the minibuffer.

7.3 Deleting Text

To delete a character you have inserted, use DEL (delete-backward-char). DEL deletes the character before the cursor (not the one that the cursor is on top of or under; that is the character after the cursor). The cursor and all characters after it move backwards. Therefore, if you type a printing character and then type DEL, they cancel out.

To delete the character that the cursor is under, use C-d (delete-char). This deletes the character, moving all the characters after the cursor backwards. The cursor is left in place. Therefore C-d is equivalent to C-f DEL.

To delete the text from the cursor to the end of the line, use C-k (kill-line). This kills the characters from the one the cursor is under to the end of the line, leaving the cursor at the end of the line (see section Killing and Yanking in the Minibuffer).

7.4 Editing the Text

To edit the text in the minibuffer, you need to be able to move around in the text. There are several commands available to do this:

C-a

Move to the beginning of the line (beginning-of-line).

C-e

Move to the end of the line (end-of-line).

C-f

Move forward one character (forward-char).

C-b

Move backward one character (backward-char).

C-t

Transpose the two characters on either side of point, moving point forward one character (transpose-chars).

7.5 Dealing with Words

The minibuffer includes several commands for dealing with words rather than characters. Often these take the usual command for moving point, but use a Meta key rather then a control key:

M-f

Move forward one word (forward-word).

M-b

Move backward one word (backward-word).

M-DEL

Delete the next word (backward-kill-word).

M-d

Delete the previous word (kill-word).

M-l

Convert the next word to lower case (downcase-word).

M-u

Convert the next word to upper case (upcase-word).

M-c

Capitalise the next word (capitalize-word).

7.6 Completion

For certain kinds of arguments, you can use completion to enter the argument value. Completion means that you type part of the argument, then af visibly fills in the rest, or as much as can be determined from the part you have typed.

When completion is available, certain keys--TAB, RET, and SPC--are rebound to complete the text present in the minibuffer into a longer string that it stands for, by matching it against a set of completion alternatives provided by the command reading the argument. ? is defined to display a list of possible completions of what you have inserted.

For example, when M-x uses the minibuffer to read the name of a command, it provides a list of all available af command names to complete against. The completion keys match the text in the minibuffer against all the command names, find any additional name characters implied by the ones already present in the minibuffer, and add those characters to the ones you have given. This is what makes it possible to type M-x del SPC m RET instead of M-x delete-message RET (for example).

Case is often significant in completion, because it is significant in many of the names that you can complete (buffer names and file names). Thus, `fo' often does not complete to `Foo'. Completion does ignore case distinctions for certain arguments in which case does not matter (such as af command or configuration variable names).

7.6.1 Completion Example

A concrete example may help here. If you type M-x co TAB, the TAB looks for alternatives (in this case, command names) that start with `co'. There are only two: copy-region-as-kill and copy-tagset-as-kill. These are the same as far as copy-, so the `co' in the minibuffer changes to `copy-'.

If you type TAB again immediately, there are multiple possibilities for the very next character--it could be `r' or `t'--so no more characters are added; instead, TAB just produces a beep. If you now type ?, af will produce a list of all possible completions to typeout; when you exit typeout, the minibuffer is still waiting for the next character.

If you go on to type r TAB, this TAB sees `copy-r'. The only command name starting this way is copy-region-as-kill, so completion fills in the rest of that. You now have `copy-region-as-kill' in the minibuffer after typing just co TAB r TAB. Note that TAB has this effect because in the minibuffer it is bound to the command minibuffer-complete when completion is available.

7.6.2 Completion Commands

Here is a list of the completion commands defined in the minibuffer when completion is available.

TAB

Complete the text in the minibuffer as much as possible (minibuffer-complete).

SPC

Complete the minibuffer text, but don't go beyond one word (minibuffer-complete-word).

RET

Submit the text in the minibuffer as the argument, possibly completing first as described below (minibuffer-complete-and-exit).

?

Print a list of all possible completions of the text in the minibuffer (minibuffer-list-completions).

SPC completes much like TAB, but never goes beyond the next hyphen or space. If you have `copy-r' in the minibuffer and type SPC, it finds that the completion is `copy-region-as-kill', but it stops completing after `region-'. This gives `copy-region-'. Another SPC at this point completes to `copy-region-as-'.

7.6.3 Strict Completion

There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

• Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
• Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

  Cautious completion is used for reading file names for files that must already exist.

• Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

  7.6.3 Strict Completion

  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

    Cautious completion is used for reading file names for files that must already exist.

  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

    7.6.3 Strict Completion

    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

      Cautious completion is used for reading file names for files that must already exist.

    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

      7.6.3 Strict Completion

      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

        Cautious completion is used for reading file names for files that must already exist.

      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

        7.6.3 Strict Completion

        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

          Cautious completion is used for reading file names for files that must already exist.

        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

          7.6.3 Strict Completion

          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

            Cautious completion is used for reading file names for files that must already exist.

          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

            7.6.3 Strict Completion

            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

              Cautious completion is used for reading file names for files that must already exist.

            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

              7.6.3 Strict Completion

              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                Cautious completion is used for reading file names for files that must already exist.

              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                7.6.3 Strict Completion

                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                  Cautious completion is used for reading file names for files that must already exist.

                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                  7.6.3 Strict Completion

                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                    Cautious completion is used for reading file names for files that must already exist.

                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                    7.6.3 Strict Completion

                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                      Cautious completion is used for reading file names for files that must already exist.

                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                      7.6.3 Strict Completion

                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                        Cautious completion is used for reading file names for files that must already exist.

                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                        7.6.3 Strict Completion

                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                          Cautious completion is used for reading file names for files that must already exist.

                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                          7.6.3 Strict Completion

                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                            Cautious completion is used for reading file names for files that must already exist.

                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                            7.6.3 Strict Completion

                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                              Cautious completion is used for reading file names for files that must already exist.

                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                              7.6.3 Strict Completion

                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                Cautious completion is used for reading file names for files that must already exist.

                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                7.6.3 Strict Completion

                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                  Cautious completion is used for reading file names for files that must already exist.

                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                  7.6.3 Strict Completion

                                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                    Cautious completion is used for reading file names for files that must already exist.

                                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                    7.6.3 Strict Completion

                                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                      Cautious completion is used for reading file names for files that must already exist.

                                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                      7.6.3 Strict Completion

                                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                        Cautious completion is used for reading file names for files that must already exist.

                                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                        7.6.3 Strict Completion

                                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                          Cautious completion is used for reading file names for files that must already exist.

                                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                          7.6.3 Strict Completion

                                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                            Cautious completion is used for reading file names for files that must already exist.

                                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                            7.6.3 Strict Completion

                                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                              Cautious completion is used for reading file names for files that must already exist.

                                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                              7.6.3 Strict Completion

                                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                Cautious completion is used for reading file names for files that must already exist.

                                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                7.6.3 Strict Completion

                                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                  Cautious completion is used for reading file names for files that must already exist.

                                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                  7.6.3 Strict Completion

                                                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                    Cautious completion is used for reading file names for files that must already exist.

                                                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                    7.6.3 Strict Completion

                                                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                      Cautious completion is used for reading file names for files that must already exist.

                                                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                      7.6.3 Strict Completion

                                                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                        Cautious completion is used for reading file names for files that must already exist.

                                                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                        7.6.3 Strict Completion

                                                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                          Cautious completion is used for reading file names for files that must already exist.

                                                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                          7.6.3 Strict Completion

                                                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                            Cautious completion is used for reading file names for files that must already exist.

                                                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                            7.6.3 Strict Completion

                                                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                              Cautious completion is used for reading file names for files that must already exist.

                                                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                              7.6.3 Strict Completion

                                                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                Cautious completion is used for reading file names for files that must already exist.

                                                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                7.6.3 Strict Completion

                                                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                  Cautious completion is used for reading file names for files that must already exist.

                                                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                  7.6.3 Strict Completion

                                                                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                    Cautious completion is used for reading file names for files that must already exist.

                                                                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                    7.6.3 Strict Completion

                                                                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                      Cautious completion is used for reading file names for files that must already exist.

                                                                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                      7.6.3 Strict Completion

                                                                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                        Cautious completion is used for reading file names for files that must already exist.

                                                                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                        7.6.3 Strict Completion

                                                                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                          Cautious completion is used for reading file names for files that must already exist.

                                                                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                          7.6.3 Strict Completion

                                                                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                            Cautious completion is used for reading file names for files that must already exist.

                                                                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                            7.6.3 Strict Completion

                                                                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                              Cautious completion is used for reading file names for files that must already exist.

                                                                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                              7.6.3 Strict Completion

                                                                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                Cautious completion is used for reading file names for files that must already exist.

                                                                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                7.6.3 Strict Completion

                                                                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                  Cautious completion is used for reading file names for files that must already exist.

                                                                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                  7.6.3 Strict Completion

                                                                                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                    Cautious completion is used for reading file names for files that must already exist.

                                                                                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                    7.6.3 Strict Completion

                                                                                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                      Cautious completion is used for reading file names for files that must already exist.

                                                                                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                      7.6.3 Strict Completion

                                                                                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                        Cautious completion is used for reading file names for files that must already exist.

                                                                                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                        7.6.3 Strict Completion

                                                                                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                          Cautious completion is used for reading file names for files that must already exist.

                                                                                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                          7.6.3 Strict Completion

                                                                                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                            Cautious completion is used for reading file names for files that must already exist.

                                                                                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                            7.6.3 Strict Completion

                                                                                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                              Cautious completion is used for reading file names for files that must already exist.

                                                                                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                              7.6.3 Strict Completion

                                                                                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                Cautious completion is used for reading file names for files that must already exist.

                                                                                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                7.6.3 Strict Completion

                                                                                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                  Cautious completion is used for reading file names for files that must already exist.

                                                                                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                  7.6.3 Strict Completion

                                                                                                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                    Cautious completion is used for reading file names for files that must already exist.

                                                                                                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                    7.6.3 Strict Completion

                                                                                                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                      Cautious completion is used for reading file names for files that must already exist.

                                                                                                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                      7.6.3 Strict Completion

                                                                                                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                        Cautious completion is used for reading file names for files that must already exist.

                                                                                                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                        7.6.3 Strict Completion

                                                                                                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                          Cautious completion is used for reading file names for files that must already exist.

                                                                                                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                          7.6.3 Strict Completion

                                                                                                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                            Cautious completion is used for reading file names for files that must already exist.

                                                                                                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                            7.6.3 Strict Completion

                                                                                                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                              Cautious completion is used for reading file names for files that must already exist.

                                                                                                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                              7.6.3 Strict Completion

                                                                                                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                Cautious completion is used for reading file names for files that must already exist.

                                                                                                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                7.6.3 Strict Completion

                                                                                                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                  Cautious completion is used for reading file names for files that must already exist.

                                                                                                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                  7.6.3 Strict Completion

                                                                                                                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                    Cautious completion is used for reading file names for files that must already exist.

                                                                                                                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                    7.6.3 Strict Completion

                                                                                                                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                      Cautious completion is used for reading file names for files that must already exist.

                                                                                                                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                      7.6.3 Strict Completion

                                                                                                                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                        Cautious completion is used for reading file names for files that must already exist.

                                                                                                                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                        7.6.3 Strict Completion

                                                                                                                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                          Cautious completion is used for reading file names for files that must already exist.

                                                                                                                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                          7.6.3 Strict Completion

                                                                                                                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                            Cautious completion is used for reading file names for files that must already exist.

                                                                                                                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                            7.6.3 Strict Completion

                                                                                                                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                              Cautious completion is used for reading file names for files that must already exist.

                                                                                                                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                              7.6.3 Strict Completion

                                                                                                                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                Cautious completion is used for reading file names for files that must already exist.

                                                                                                                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                7.6.3 Strict Completion

                                                                                                                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                  Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                  7.6.3 Strict Completion

                                                                                                                                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                    Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                    7.6.3 Strict Completion

                                                                                                                                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                      Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                      7.6.3 Strict Completion

                                                                                                                                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                        Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                        7.6.3 Strict Completion

                                                                                                                                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                          Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                          7.6.3 Strict Completion

                                                                                                                                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                            Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                            7.6.3 Strict Completion

                                                                                                                                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                              Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                              7.6.3 Strict Completion

                                                                                                                                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                7.6.3 Strict Completion

                                                                                                                                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                  Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                  7.6.3 Strict Completion

                                                                                                                                                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                    Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                    7.6.3 Strict Completion

                                                                                                                                                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                      Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                      7.6.3 Strict Completion

                                                                                                                                                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                        Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                        7.6.3 Strict Completion

                                                                                                                                                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                          Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                          7.6.3 Strict Completion

                                                                                                                                                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                            Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                            7.6.3 Strict Completion

                                                                                                                                                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                              Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                              7.6.3 Strict Completion

                                                                                                                                                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                7.6.3 Strict Completion

                                                                                                                                                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                  Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                  7.6.3 Strict Completion

                                                                                                                                                                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                    Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                    7.6.3 Strict Completion

                                                                                                                                                                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                      Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                      7.6.3 Strict Completion

                                                                                                                                                                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                        Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                        7.6.3 Strict Completion

                                                                                                                                                                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                          Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                          7.6.3 Strict Completion

                                                                                                                                                                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                            Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                            7.6.3 Strict Completion

                                                                                                                                                                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                              Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                              7.6.3 Strict Completion

                                                                                                                                                                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                                Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                                7.6.3 Strict Completion

                                                                                                                                                                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                                  Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                                  7.6.3 Strict Completion

                                                                                                                                                                                  There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                                  • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                                  • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                                    Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                                  • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                                    7.6.3 Strict Completion

                                                                                                                                                                                    There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                                    • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                                    • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                                      Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                                    • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                                      7.6.3 Strict Completion

                                                                                                                                                                                      There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                                      • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                                      • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                                        Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                                      • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                                        7.6.3 Strict Completion

                                                                                                                                                                                        There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                                        • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                                        • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                                          Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                                        • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                                          7.6.3 Strict Completion

                                                                                                                                                                                          There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                                          • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                                          • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                                            Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                                          • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                                            7.6.3 Strict Completion

                                                                                                                                                                                            There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                                            • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                                            • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                                              Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                                            • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                                              7.6.3 Strict Completion

                                                                                                                                                                                              There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                                              • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                                              • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                                                Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                                              • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

                                                                                                                                                                                                7.6.3 Strict Completion

                                                                                                                                                                                                There are three different ways that RET can work in completing the minibuffer, depending on how the argument will be used.

                                                                                                                                                                                                • Strict completion is used when it is meaningless to give any argument except one of the known alternatives. For example, when M-x reads the name of a command to run, it is meaningless to give anything but the name of an existing command or macro. In strict completion, RET refuses to exit if the text in the minibuffer does not complete to an exact match.
                                                                                                                                                                                                • Cautious completion is similar to strict completion, except that RET exits only if the text was an exact match already, not needing completion. If the text is not an exact match, RET does not exit, but it does complete the text. If it completes to an exact match, a second RET will exit.

                                                                                                                                                                                                  Cautious completion is used for reading file names for files that must already exist.

                                                                                                                                                                                                • Permissive completion is used when ese reading order"> > ]   [ << ] [ Up ] [