1 @c This is part of the Emacs manual.
2 @c Copyright (C) 1985-1987, 1993-1995, 1997, 2000-2015 Free Software
4 @c See file emacs.texi for copying conditions.
6 @chapter Using Multiple Buffers
9 The text you are editing in Emacs resides in an object called a
10 @dfn{buffer}. Each time you visit a file, a buffer is used to hold
11 the file's text. Each time you invoke Dired, a buffer is used to hold
12 the directory listing. If you send a message with @kbd{C-x m}, a
13 buffer is used to hold the text of the message. When you ask for a
14 command's documentation, that appears in a buffer named @file{*Help*}.
16 Each buffer has a unique name, which can be of any length. When a
17 buffer is displayed in a window, its name is shown in the mode line
18 (@pxref{Mode Line}). The distinction between upper and lower case
19 matters in buffer names. Most buffers are made by visiting files, and
20 their names are derived from the files' names; however, you can also
21 create an empty buffer with any name you want. A newly started Emacs
22 has several buffers, including one named @file{*scratch*}, which can
23 be used for evaluating Lisp expressions and is not associated with any
24 file (@pxref{Lisp Interaction}).
26 @cindex selected buffer
27 @cindex current buffer
28 At any time, one and only one buffer is @dfn{selected}; we call it
29 the @dfn{current buffer}. We sometimes say that a command operates on
30 ``the buffer''; this really means that it operates on the current
31 buffer. When there is only one Emacs window, the buffer displayed in
32 that window is current. When there are multiple windows, the buffer
33 displayed in the @dfn{selected window} is current. @xref{Windows}.
35 Aside from its textual contents, each buffer records several pieces
36 of information, such as what file it is visiting (if any), whether it
37 is modified, and what major mode and minor modes are in effect
38 (@pxref{Modes}). These are stored in @dfn{buffer-local
39 variables}---variables that can have a different value in each buffer.
42 @cindex buffer size, maximum
43 A buffer's size cannot be larger than some maximum, which is defined
44 by the largest buffer position representable by @dfn{Emacs integers}.
45 This is because Emacs tracks buffer positions using that data type.
46 For typical 64-bit machines, this maximum buffer size is @math{2^{61} - 2}
47 bytes, or about 2 EiB@. For typical 32-bit machines, the maximum is
48 usually @math{2^{29} - 2} bytes, or about 512 MiB@. Buffer sizes are
49 also limited by the amount of memory in the system.
52 * Select Buffer:: Creating a new buffer or reselecting an old one.
53 * List Buffers:: Getting a list of buffers that exist.
54 * Misc Buffer:: Renaming; changing read-only status; copying text.
55 * Kill Buffer:: Killing buffers you no longer need.
56 * Several Buffers:: How to go through the list of all buffers
57 and operate variously on several of them.
58 * Indirect Buffers:: An indirect buffer shares the text of another buffer.
59 * Buffer Convenience:: Convenience and customization features for
64 @section Creating and Selecting Buffers
65 @cindex change buffers
66 @cindex switch buffers
69 @item C-x b @var{buffer} @key{RET}
70 Select or create a buffer named @var{buffer} (@code{switch-to-buffer}).
71 @item C-x 4 b @var{buffer} @key{RET}
72 Similar, but select @var{buffer} in another window
73 (@code{switch-to-buffer-other-window}).
74 @item C-x 5 b @var{buffer} @key{RET}
75 Similar, but select @var{buffer} in a separate frame
76 (@code{switch-to-buffer-other-frame}).
78 Select the previous buffer in the buffer list (@code{previous-buffer}).
80 Select the next buffer in the buffer list (@code{next-buffer}).
83 Read a number @var{n} and move to line @var{n} in the most recently
84 selected buffer other than the current buffer.
88 @findex switch-to-buffer
89 The @kbd{C-x b} (@code{switch-to-buffer}) command reads a buffer
90 name using the minibuffer. Then it makes that buffer current, and
91 displays it in the currently-selected window. An empty input
92 specifies the buffer that was current most recently among those not
93 now displayed in any window.
95 While entering the buffer name, you can use the usual completion and
96 history commands (@pxref{Minibuffer}). Note that @kbd{C-x b}, and
97 related commands, use ``permissive completion with confirmation'' for
98 minibuffer completion: if you type @key{RET} immediately after
99 completing up to a nonexistent buffer name, Emacs prints
100 @samp{[Confirm]} and you must type a second @key{RET} to submit that
101 buffer name. @xref{Completion Exit}, for details.
103 If you specify a buffer that does not exist, @kbd{C-x b} creates a
104 new, empty buffer that is not visiting any file, and selects it for
105 editing. The default value of the variable @code{major-mode}
106 determines the new buffer's major mode; the default value is
107 Fundamental mode. @xref{Major Modes}. One reason to create a new
108 buffer is to use it for making temporary notes. If you try to save
109 it, Emacs asks for the file name to use, and the buffer's major mode
110 is re-established taking that file name into account (@pxref{Choosing
113 @kindex C-x @key{LEFT}
114 @kindex C-x @key{RIGHT}
116 @findex previous-buffer
117 For conveniently switching between a few buffers, use the commands
118 @kbd{C-x @key{LEFT}} and @kbd{C-x @key{RIGHT}}. @kbd{C-x @key{LEFT}}
119 (@code{previous-buffer}) selects the previous buffer (following the
120 order of most recent selection in the current frame), while @kbd{C-x
121 @key{RIGHT}} (@code{next-buffer}) moves through buffers in the reverse
125 @findex switch-to-buffer-other-window
126 To select a buffer in a window other than the current one, type
127 @kbd{C-x 4 b} (@code{switch-to-buffer-other-window}). This prompts
128 for a buffer name using the minibuffer, displays that buffer in
129 another window, and selects that window.
132 @findex switch-to-buffer-other-frame
133 Similarly, @kbd{C-x 5 b} (@code{switch-to-buffer-other-frame})
134 prompts for a buffer name, displays that buffer in another frame, and
135 selects that frame. If the buffer is already being shown in a window
136 on another frame, Emacs selects that window and frame instead of
137 creating a new frame.
139 @xref{Displaying Buffers}, for how the @kbd{C-x 4 b} and @kbd{C-x 5
140 b} commands get the window and/or frame to display in.
142 In addition, @kbd{C-x C-f}, and any other command for visiting a
143 file, can also be used to switch to an existing file-visiting buffer.
147 @kbd{C-u M-g M-g}, that is @code{goto-line} with a plain prefix
148 argument, reads a number @var{n} using the minibuffer, selects the
149 most recently selected buffer other than the current buffer in another
150 window, and then moves point to the beginning of line number @var{n}
151 in that buffer. This is mainly useful in a buffer that refers to line
152 numbers in another buffer: if point is on or just after a number,
153 @code{goto-line} uses that number as the default for @var{n}. Note
154 that prefix arguments other than just @kbd{C-u} behave differently.
155 @kbd{C-u 4 M-g M-g} goes to line 4 in the @emph{current} buffer,
156 without reading a number from the minibuffer. (Remember that @kbd{M-g
157 M-g} without prefix argument reads a number @var{n} and then moves to
158 line number @var{n} in the current buffer. @xref{Moving Point}.)
160 Emacs uses buffer names that start with a space for internal purposes.
161 It treats these buffers specially in minor ways---for example, by
162 default they do not record undo information. It is best to avoid using
163 such buffer names yourself.
166 @section Listing Existing Buffers
170 List the existing buffers (@code{list-buffers}).
173 @cindex listing current buffers
176 To display a list of existing buffers, type @kbd{C-x C-b}. Each
177 line in the list shows one buffer's name, size, major mode and visited file.
178 The buffers are listed in the order that they were current; the
179 buffers that were current most recently come first.
181 @samp{.} in the first field of a line indicates that the buffer is
182 current. @samp{%} indicates a read-only buffer. @samp{*} indicates
183 that the buffer is ``modified''. If several buffers are modified, it
184 may be time to save some with @kbd{C-x s} (@pxref{Save Commands}).
185 Here is an example of a buffer list:
188 CRM Buffer Size Mode File
189 . * .emacs 3294 Emacs-Lisp ~/.emacs
191 search.c 86055 C ~/cvs/emacs/src/search.c
192 % src 20959 Dired by name ~/cvs/emacs/src/
194 % HELLO 1607 Fundamental ~/cvs/emacs/etc/HELLO
195 % NEWS 481184 Outline ~/cvs/emacs/etc/NEWS
196 *scratch* 191 Lisp Interaction
197 * *Messages* 1554 Messages
201 The buffer @file{*Help*} was made by a help request (@pxref{Help}); it
202 is not visiting any file. The buffer @code{src} was made by Dired on
203 the directory @file{~/cvs/emacs/src/}. You can list only buffers that
204 are visiting files by giving the command a prefix argument, as in
207 @code{list-buffers} omits buffers whose names begin with a space,
208 unless they visit files: such buffers are used internally by Emacs.
211 @section Miscellaneous Buffer Operations
215 Toggle read-only status of buffer (@code{read-only-mode}).
216 @item M-x rename-buffer @key{RET} @var{name} @key{RET}
217 Change the name of the current buffer.
218 @item M-x rename-uniquely
219 Rename the current buffer by adding @samp{<@var{number}>} to the end.
220 @item M-x view-buffer @key{RET} @var{buffer} @key{RET}
221 Scroll through buffer @var{buffer}. @xref{View Mode}.
225 @vindex buffer-read-only
226 @cindex read-only buffer
227 A buffer can be @dfn{read-only}, which means that commands to change
228 its contents are not allowed. The mode line indicates read-only
229 buffers with @samp{%%} or @samp{%*} near the left margin. @xref{Mode
230 Line}. Read-only buffers are usually made by subsystems such as Dired
231 and Rmail that have special commands to operate on the text; also by
232 visiting a file whose access control says you cannot write it.
234 @findex read-only-mode
235 @vindex view-read-only
236 The command @kbd{C-x C-q} (@code{read-only-mode}) makes a read-only
237 buffer writable, and makes a writable buffer read-only. This works by
238 setting the variable @code{buffer-read-only}, which has a local value
239 in each buffer and makes the buffer read-only if its value is
240 non-@code{nil}. If you change the option @code{view-read-only} to a
241 non-@code{nil} value, making the buffer read-only with @kbd{C-x C-q}
242 also enables View mode in the buffer (@pxref{View Mode}).
244 @findex rename-buffer
245 @kbd{M-x rename-buffer} changes the name of the current buffer. You
246 specify the new name as a minibuffer argument; there is no default.
247 If you specify a name that is in use for some other buffer, an error
248 happens and no renaming is done.
250 @findex rename-uniquely
251 @kbd{M-x rename-uniquely} renames the current buffer to a similar
252 name with a numeric suffix added to make it both different and unique.
253 This command does not need an argument. It is useful for creating
254 multiple shell buffers: if you rename the @file{*shell*} buffer, then
255 do @kbd{M-x shell} again, it makes a new shell buffer named
256 @file{*shell*}; meanwhile, the old shell buffer continues to exist
257 under its new name. This method is also good for mail buffers,
258 compilation buffers, and most Emacs features that create special
259 buffers with particular names. (With some of these features, such as
260 @kbd{M-x compile}, @kbd{M-x grep}, you need to switch to some other
261 buffer before using the command again, otherwise it will reuse the
262 current buffer despite the name change.)
264 The commands @kbd{M-x append-to-buffer} and @kbd{M-x insert-buffer}
265 can also be used to copy text from one buffer to another.
266 @xref{Accumulating Text}.
269 @section Killing Buffers
271 @cindex killing buffers
274 If you continue an Emacs session for a while, you may accumulate a
275 large number of buffers. You may then find it convenient to @dfn{kill}
276 the buffers you no longer need. (Some other editors call this
277 operation @dfn{close}, and talk about ``closing the buffer'' or
278 ``closing the file'' visited in the buffer.) On most operating
279 systems, killing a buffer releases its space back to the operating
280 system so that other programs can use it. Here are some commands for
284 @item C-x k @var{bufname} @key{RET}
285 Kill buffer @var{bufname} (@code{kill-buffer}).
286 @item M-x kill-some-buffers
287 Offer to kill each buffer, one by one.
288 @item M-x kill-matching-buffers
289 Offer to kill all buffers matching a regular expression.
294 @kbd{C-x k} (@code{kill-buffer}) kills one buffer, whose name you
295 specify in the minibuffer. The default, used if you type just
296 @key{RET} in the minibuffer, is to kill the current buffer. If you
297 kill the current buffer, another buffer becomes current: one that was
298 current in the recent past but is not displayed in any window now. If
299 you ask to kill a file-visiting buffer that is modified, then you must
300 confirm with @kbd{yes} before the buffer is killed.
302 @findex kill-some-buffers
303 The command @kbd{M-x kill-some-buffers} asks about each buffer, one
304 by one. An answer of @kbd{y} means to kill the buffer, just like
305 @code{kill-buffer}. This command ignores buffers whose names begin
306 with a space, which are used internally by Emacs.
308 @findex kill-matching-buffers
309 The command @kbd{M-x kill-matching-buffers} prompts for a regular
310 expression and kills all buffers whose names match that expression.
311 @xref{Regexps}. Like @code{kill-some-buffers}, it asks for
312 confirmation before each kill. This command normally ignores buffers
313 whose names begin with a space, which are used internally by Emacs.
314 To kill internal buffers as well, call @code{kill-matching-buffers}
315 with a prefix argument.
317 The Buffer Menu feature is also convenient for killing various
318 buffers. @xref{Several Buffers}.
320 @vindex kill-buffer-hook
321 If you want to do something special every time a buffer is killed, you
322 can add hook functions to the hook @code{kill-buffer-hook} (@pxref{Hooks}).
324 @findex clean-buffer-list
325 If you run one Emacs session for a period of days, as many people do,
326 it can fill up with buffers that you used several days ago. The command
327 @kbd{M-x clean-buffer-list} is a convenient way to purge them; it kills
328 all the unmodified buffers that you have not used for a long time. An
329 ordinary buffer is killed if it has not been displayed for three days;
330 however, you can specify certain buffers that should never be killed
331 automatically, and others that should be killed if they have been unused
334 @cindex Midnight mode
335 @vindex midnight-mode
336 @vindex midnight-hook
337 You can also have this buffer purging done for you, once a day,
338 by enabling Midnight mode. Midnight mode operates each day
339 at midnight; at that time, it runs @code{clean-buffer-list}, or
340 whichever functions you have placed in the normal hook
341 @code{midnight-hook} (@pxref{Hooks}). To enable Midnight mode, use
342 the Customization buffer to set the variable @code{midnight-mode} to
343 @code{t}. @xref{Easy Customization}.
345 @node Several Buffers
346 @section Operating on Several Buffers
350 @item M-x buffer-menu
351 Begin editing a buffer listing all Emacs buffers.
352 @item M-x buffer-menu-other-window
353 Similar, but do it in another window.
356 The @dfn{Buffer Menu} opened by @kbd{C-x C-b} (@pxref{List Buffers})
357 does not merely list buffers. It also allows you to perform various
358 operations on buffers, through an interface similar to Dired
359 (@pxref{Dired}). You can save buffers, kill them (here called
360 @dfn{deleting} them, for consistency with Dired), or display them.
363 @findex buffer-menu-other-window
364 To use the Buffer Menu, type @kbd{C-x C-b} and switch to the window
365 displaying the @file{*Buffer List*} buffer. You can also type
366 @kbd{M-x buffer-menu} to open the Buffer Menu in the selected window.
367 Alternatively, the command @kbd{M-x buffer-menu-other-window} opens
368 the Buffer Menu in another window, and selects that window.
370 The Buffer Menu is a read-only buffer, and can be changed only
371 through the special commands described in this section. The usual
372 cursor motion commands can be used in this buffer. The following
373 commands apply to the buffer described on the current line:
377 @findex Buffer-menu-delete
378 @kindex d @r{(Buffer Menu)}
379 Flag the buffer for deletion (killing), then move point to the next
380 line (@code{Buffer-menu-delete}). The deletion flag is indicated by
381 the character @samp{D} on the line, before the buffer name. The
382 deletion occurs only when you type the @kbd{x} command (see below).
385 @findex Buffer-menu-delete-backwards
386 @kindex C-d @r{(Buffer Menu)}
387 Like @kbd{d}, but move point up instead of down
388 (@code{Buffer-menu-delete-backwards}).
391 @findex Buffer-menu-save
392 @kindex s @r{(Buffer Menu)}
393 Flag the buffer for saving (@code{Buffer-menu-save}). The save flag
394 is indicated by the character @samp{S} on the line, before the buffer
395 name. The saving occurs only when you type @kbd{x}. You may request
396 both saving and deletion for the same buffer.
399 @findex Buffer-menu-execute
400 @kindex x @r{(Buffer Menu)}
401 Perform all flagged deletions and saves (@code{Buffer-menu-execute}).
404 @findex Buffer-menu-unmark
405 @kindex u @r{(Buffer Menu)}
406 Remove all flags from the current line, and move down
407 (@code{Buffer-menu-unmark}).
410 @findex Buffer-menu-backup-unmark
411 @kindex DEL @r{(Buffer Menu)}
412 Move to the previous line and remove all flags on that line
413 (@code{Buffer-menu-backup-unmark}).
417 The commands for adding or removing flags, @kbd{d}, @kbd{C-d}, @kbd{s}
418 and @kbd{u}, all accept a numeric argument as a repeat count.
420 The following commands operate immediately on the buffer listed on
421 the current line. They also accept a numeric argument as a repeat
426 @findex Buffer-menu-not-modified
427 @kindex ~ @r{(Buffer Menu)}
428 Mark the buffer as unmodified (@code{Buffer-menu-not-modified}).
429 @xref{Save Commands}.
432 @findex Buffer-menu-toggle-read-only
433 @kindex % @r{(Buffer Menu)}
434 Toggle the buffer's read-only status
435 (@code{Buffer-menu-toggle-read-only}). @xref{Misc Buffer}.
438 @findex Buffer-menu-visit-tags-table
439 @kindex % @r{(Buffer Menu)}
440 Visit the buffer as a tags table
441 (@code{Buffer-menu-visit-tags-table}). @xref{Select Tags Table}.
444 The following commands are used to select another buffer or buffers:
449 @kindex q @r{(Buffer Menu)}
450 Quit the Buffer Menu (@code{quit-window}). The most recent formerly
451 visible buffer is displayed in its place.
455 @findex Buffer-menu-this-window
456 @kindex f @r{(Buffer Menu)}
457 @kindex RET @r{(Buffer Menu)}
458 Select this line's buffer, replacing the @file{*Buffer List*} buffer
459 in its window (@code{Buffer-menu-this-window}).
462 @findex Buffer-menu-other-window
463 @kindex o @r{(Buffer Menu)}
464 Select this line's buffer in another window, as if by @kbd{C-x 4 b},
465 leaving @file{*Buffer List*} visible
466 (@code{Buffer-menu-other-window}).
469 @findex Buffer-menu-switch-other-window
470 @kindex C-o @r{(Buffer Menu)}
471 Display this line's buffer in another window, without selecting it
472 (@code{Buffer-menu-switch-other-window}).
475 @findex Buffer-menu-1-window
476 @kindex 1 @r{(Buffer Menu)}
477 Select this line's buffer in a full-frame window
478 (@code{Buffer-menu-1-window}).
481 @findex Buffer-menu-2-window
482 @kindex 2 @r{(Buffer Menu)}
483 Set up two windows on the current frame, with this line's buffer
484 selected in one, and a previously current buffer (aside from
485 @file{*Buffer List*}) in the other (@code{Buffer-menu-2-window}).
488 @findex Buffer-menu-bury
489 @kindex b @r{(Buffer Menu)}
490 Bury this line's buffer (@code{Buffer-menu-bury}).
493 @findex Buffer-menu-mark
494 @kindex m @r{(Buffer Menu)}
495 Mark this line's buffer to be displayed in another window if you exit
496 with the @kbd{v} command (@code{Buffer-menu-mark}). The display flag
497 is indicated by the character @samp{>} at the beginning of the line.
498 (A single buffer may not have both deletion and display flags.)
501 @findex Buffer-menu-select
502 @kindex v @r{(Buffer Menu)}
503 Select this line's buffer, and also display in other windows any
504 buffers flagged with the @kbd{m} command (@code{Buffer-menu-select}).
505 If you have not flagged any buffers, this command is equivalent to
509 The following commands affect the entire buffer list:
513 @findex tabulated-list-sort
514 @kindex S @r{(Buffer Menu)}
515 Sort the Buffer Menu entries according to their values in the column
516 at point. With a numeric prefix argument @var{n}, sort according to
517 the @var{n}-th column (@code{tabulated-list-sort}).
520 @findex Buffer-menu-toggle-files-only
521 @kindex T @r{(Buffer Menu)}
522 Delete, or reinsert, lines for non-file buffers
523 (@code{Buffer-menu-toggle-files-only}). This command toggles the
524 inclusion of such buffers in the buffer list.
527 Normally, the buffer @file{*Buffer List*} is not updated
528 automatically when buffers are created and killed; its contents are
529 just text. If you have created, deleted or renamed buffers, the way
530 to update @file{*Buffer List*} to show what you have done is to type
531 @kbd{g} (@code{revert-buffer}). You can make this happen regularly
532 every @code{auto-revert-interval} seconds if you enable Auto Revert
533 mode in this buffer, as long as it is not marked modified. Global
534 Auto Revert mode applies to the @file{*Buffer List*} buffer only if
535 @code{global-auto-revert-non-file-buffers} is non-@code{nil}.
537 @inforef{Autorevert,, emacs-xtra}, for details.
540 @xref{Autorevert, global-auto-revert-non-file-buffers}, for details.
543 @node Indirect Buffers
544 @section Indirect Buffers
545 @cindex indirect buffer
548 An @dfn{indirect buffer} shares the text of some other buffer, which
549 is called the @dfn{base buffer} of the indirect buffer. In some ways it
550 is a buffer analogue of a symbolic link between files.
553 @findex make-indirect-buffer
554 @item M-x make-indirect-buffer @key{RET} @var{base-buffer} @key{RET} @var{indirect-name} @key{RET}
555 Create an indirect buffer named @var{indirect-name} with base buffer
557 @findex clone-indirect-buffer
558 @item M-x clone-indirect-buffer @key{RET}
559 Create an indirect buffer that is a twin copy of the current buffer.
562 @findex clone-indirect-buffer-other-window
563 Create an indirect buffer that is a twin copy of the current buffer, and
564 select it in another window (@code{clone-indirect-buffer-other-window}).
567 The text of the indirect buffer is always identical to the text of its
568 base buffer; changes made by editing either one are visible immediately
569 in the other. But in all other respects, the indirect buffer and its
570 base buffer are completely separate. They can have different names,
571 different values of point, different narrowing, different markers,
572 different major modes, and different local variables.
574 An indirect buffer cannot visit a file, but its base buffer can. If
575 you try to save the indirect buffer, that actually works by saving the
576 base buffer. Killing the base buffer effectively kills the indirect
577 buffer, but killing an indirect buffer has no effect on its base buffer.
579 One way to use indirect buffers is to display multiple views of an
580 outline. @xref{Outline Views}.
582 @vindex clone-indirect-buffer-hook
583 A quick and handy way to make an indirect buffer is with the command
584 @kbd{M-x clone-indirect-buffer}. It creates and selects an indirect
585 buffer whose base buffer is the current buffer. With a numeric
586 argument, it prompts for the name of the indirect buffer; otherwise it
587 uses the name of the current buffer, with a @samp{<@var{n}>} suffix
588 added. @kbd{C-x 4 c} (@code{clone-indirect-buffer-other-window})
589 works like @kbd{M-x clone-indirect-buffer}, but it selects the new
590 buffer in another window. These functions run the hook
591 @code{clone-indirect-buffer-hook} after creating the indirect buffer.
593 The more general way to make an indirect buffer is with the command
594 @kbd{M-x make-indirect-buffer}. It creates an indirect buffer
595 named @var{indirect-name} from a buffer @var{base-buffer}, prompting for
596 both using the minibuffer.
598 @node Buffer Convenience
599 @section Convenience Features and Customization of Buffer Handling
601 This section describes several modes and features that make it more
602 convenient to switch between buffers.
605 * Uniquify:: Making buffer names unique with directory parts.
606 * Icomplete:: Fast minibuffer selection.
607 * Buffer Menus:: Configurable buffer menu.
611 @subsection Making Buffer Names Unique
613 @cindex unique buffer names
614 @cindex directories in buffer names
615 When several buffers visit identically-named files, Emacs must give
616 the buffers distinct names. The default method adds a suffix based on
617 the names of the directories that contain the files. For example, if
618 you visit files @file{/foo/bar/mumble/name} and
619 @file{/baz/quux/mumble/name} at the same time, their buffers will be
620 named @samp{name<bar/mumble>} and @samp{name<quux/mumble>}, respectively.
621 Emacs adds as many directory parts as are needed to make a unique name.
623 @vindex uniquify-buffer-name-style
624 You can choose from several different styles for constructing unique
625 buffer names, by customizing the option @code{uniquify-buffer-name-style}.
627 The @code{forward} naming method includes part of the file's
628 directory name at the beginning of the buffer name; using this method,
629 buffers visiting the files @file{/u/rms/tmp/Makefile} and
630 @file{/usr/projects/zaphod/Makefile} would be named
631 @samp{tmp/Makefile} and @samp{zaphod/Makefile}.
633 In contrast, the @code{post-forward} naming method would call the
634 buffers @samp{Makefile|tmp} and @samp{Makefile|zaphod}. The default
635 method @code{post-forward-angle-brackets} is like @code{post-forward},
636 except that it encloses the unique path in angle brackets. The
637 @code{reverse} naming method would call them @samp{Makefile\tmp} and
638 @samp{Makefile\zaphod}. The nontrivial difference between
639 @code{post-forward} and @code{reverse} occurs when just one directory
640 name is not enough to distinguish two files; then @code{reverse} puts
641 the directory names in reverse order, so that @file{/top/middle/file}
642 becomes @samp{file\middle\top}, while @code{post-forward} puts them in
643 forward order after the file name, as in @samp{file|top/middle}. If
644 @code{uniquify-buffer-name-style} is set to @code{nil}, the buffer
645 names simply get @samp{<2>}, @samp{<3>}, etc.@: appended.
647 Which rule to follow for putting the directory names in the buffer
648 name is not very important if you are going to @emph{look} at the
649 buffer names before you type one. But as an experienced user, if you
650 know the rule, you won't have to look. And then you may find that one
651 rule or another is easier for you to remember and apply quickly.
654 @subsection Fast minibuffer selection
656 @findex icomplete-mode
657 @cindex Icomplete mode
659 Icomplete global minor mode provides a convenient way to quickly select an
660 element among the possible completions in a minibuffer. When enabled, typing
661 in the minibuffer continuously displays a list of possible completions that
662 match the string you have typed.
664 At any time, you can type @kbd{C-j} to select the first completion in
665 the list. So the way to select a particular completion is to make it the
666 first in the list. There are two ways to do this. You can type more
667 of the completion name and thus narrow down the list, excluding unwanted
668 completions above the desired one. Alternatively, you can use @kbd{C-.}
669 and @kbd{C-,} to rotate the list until the desired buffer is first.
671 @kbd{M-@key{TAB}} will select the first completion in the list, like
672 @kbd{C-j} but without exiting the minibuffer, so you can edit it
673 further. This is typically used when entering a file name, where
674 @kbd{M-@key{TAB}} can be used a few times to descend in the hierarchy
677 To enable Icomplete mode, type @kbd{M-x icomplete-mode}, or customize
678 the variable @code{icomplete-mode} to @code{t} (@pxref{Easy
682 @subsection Customizing Buffer Menus
685 @cindex buffer list, customizable
688 Make a list of buffers similarly to @kbd{M-x list-buffers} but
692 @kbd{M-x bs-show} pops up a buffer list similar to the one normally
693 displayed by @kbd{C-x C-b} but which you can customize. If you prefer
694 this to the usual buffer list, you can bind this command to @kbd{C-x
695 C-b}. To customize this buffer list, use the @code{bs} Custom group
696 (@pxref{Easy Customization}).
701 @findex mouse-buffer-menu
702 @kindex C-Down-Mouse-1
703 MSB global minor mode (``MSB'' stands for ``mouse select buffer'')
704 provides a different and customizable mouse buffer menu which you may
705 prefer. It replaces the bindings of @code{mouse-buffer-menu},
706 normally on @kbd{C-Down-Mouse-1}, and the menu bar buffer menu. You
707 can customize the menu in the @code{msb} Custom group.