Mercurial > emacs
annotate doc/lispref/buffers.texi @ 102404:b2bd32bf5b5e
(rmail-output-as-mbox): Use rmail-ensure-blank-line.
(rmail-output-to-rmail-buffer): Add the new message at the end of the
existing messages, ensuring there is a blank line between them. (Bug#2521)
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Thu, 05 Mar 2009 03:43:01 +0000 |
parents | cb5d2387102c |
children | a6980029e2a0 |
rev | line source |
---|---|
84052 | 1 @c -*-texinfo-*- |
2 @c This is part of the GNU Emacs Lisp Reference Manual. | |
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999, 2001, 2002, | |
100974 | 4 @c 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc. |
84052 | 5 @c See the file elisp.texi for copying conditions. |
84116
0ba80d073e27
(setfilename): Go up one more level to ../../info.
Glenn Morris <rgm@gnu.org>
parents:
84052
diff
changeset
|
6 @setfilename ../../info/buffers |
84052 | 7 @node Buffers, Windows, Backups and Auto-Saving, Top |
8 @chapter Buffers | |
9 @cindex buffer | |
10 | |
11 A @dfn{buffer} is a Lisp object containing text to be edited. Buffers | |
12 are used to hold the contents of files that are being visited; there may | |
13 also be buffers that are not visiting files. While several buffers may | |
14 exist at one time, only one buffer is designated the @dfn{current | |
15 buffer} at any time. Most editing commands act on the contents of the | |
16 current buffer. Each buffer, including the current buffer, may or may | |
17 not be displayed in any windows. | |
18 | |
19 @menu | |
20 * Buffer Basics:: What is a buffer? | |
21 * Current Buffer:: Designating a buffer as current | |
22 so that primitives will access its contents. | |
23 * Buffer Names:: Accessing and changing buffer names. | |
24 * Buffer File Name:: The buffer file name indicates which file is visited. | |
25 * Buffer Modification:: A buffer is @dfn{modified} if it needs to be saved. | |
26 * Modification Time:: Determining whether the visited file was changed | |
27 ``behind Emacs's back''. | |
28 * Read Only Buffers:: Modifying text is not allowed in a read-only buffer. | |
29 * The Buffer List:: How to look at all the existing buffers. | |
30 * Creating Buffers:: Functions that create buffers. | |
31 * Killing Buffers:: Buffers exist until explicitly killed. | |
32 * Indirect Buffers:: An indirect buffer shares text with some other buffer. | |
98963
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
33 * Swapping Text:: Swapping text between two buffers. |
84052 | 34 * Buffer Gap:: The gap in the buffer. |
35 @end menu | |
36 | |
37 @node Buffer Basics | |
38 @comment node-name, next, previous, up | |
39 @section Buffer Basics | |
40 | |
41 @ifnottex | |
42 A @dfn{buffer} is a Lisp object containing text to be edited. Buffers | |
43 are used to hold the contents of files that are being visited; there may | |
44 also be buffers that are not visiting files. Although several buffers | |
45 normally exist, only one buffer is designated the @dfn{current | |
46 buffer} at any time. Most editing commands act on the contents of the | |
47 current buffer. Each buffer, including the current buffer, may or may | |
48 not be displayed in any windows. | |
49 @end ifnottex | |
50 | |
51 Buffers in Emacs editing are objects that have distinct names and hold | |
52 text that can be edited. Buffers appear to Lisp programs as a special | |
53 data type. You can think of the contents of a buffer as a string that | |
54 you can extend; insertions and deletions may occur in any part of the | |
55 buffer. @xref{Text}. | |
56 | |
57 A Lisp buffer object contains numerous pieces of information. Some of | |
58 this information is directly accessible to the programmer through | |
59 variables, while other information is accessible only through | |
60 special-purpose functions. For example, the visited file name is | |
61 directly accessible through a variable, while the value of point is | |
62 accessible only through a primitive function. | |
63 | |
64 Buffer-specific information that is directly accessible is stored in | |
65 @dfn{buffer-local} variable bindings, which are variable values that are | |
66 effective only in a particular buffer. This feature allows each buffer | |
67 to override the values of certain variables. Most major modes override | |
68 variables such as @code{fill-column} or @code{comment-column} in this | |
69 way. For more information about buffer-local variables and functions | |
70 related to them, see @ref{Buffer-Local Variables}. | |
71 | |
72 For functions and variables related to visiting files in buffers, see | |
73 @ref{Visiting Files} and @ref{Saving Buffers}. For functions and | |
74 variables related to the display of buffers in windows, see | |
75 @ref{Buffers and Windows}. | |
76 | |
77 @defun bufferp object | |
78 This function returns @code{t} if @var{object} is a buffer, | |
79 @code{nil} otherwise. | |
80 @end defun | |
81 | |
82 @node Current Buffer | |
83 @section The Current Buffer | |
84 @cindex selecting a buffer | |
85 @cindex changing to another buffer | |
86 @cindex current buffer | |
87 | |
88 There are, in general, many buffers in an Emacs session. At any time, | |
89 one of them is designated as the @dfn{current buffer}. This is the | |
90 buffer in which most editing takes place, because most of the primitives | |
91 for examining or changing text in a buffer operate implicitly on the | |
92 current buffer (@pxref{Text}). Normally the buffer that is displayed on | |
93 the screen in the selected window is the current buffer, but this is not | |
94 always so: a Lisp program can temporarily designate any buffer as | |
95 current in order to operate on its contents, without changing what is | |
96 displayed on the screen. | |
97 | |
98 The way to designate a current buffer in a Lisp program is by calling | |
99 @code{set-buffer}. The specified buffer remains current until a new one | |
100 is designated. | |
101 | |
102 When an editing command returns to the editor command loop, the | |
103 command loop designates the buffer displayed in the selected window as | |
104 current, to prevent confusion: the buffer that the cursor is in when | |
105 Emacs reads a command is the buffer that the command will apply to. | |
106 (@xref{Command Loop}.) Therefore, @code{set-buffer} is not the way to | |
107 switch visibly to a different buffer so that the user can edit it. For | |
108 that, you must use the functions described in @ref{Displaying Buffers}. | |
109 | |
110 @strong{Warning:} Lisp functions that change to a different current buffer | |
111 should not depend on the command loop to set it back afterwards. | |
112 Editing commands written in Emacs Lisp can be called from other programs | |
113 as well as from the command loop; it is convenient for the caller if | |
114 the subroutine does not change which buffer is current (unless, of | |
115 course, that is the subroutine's purpose). Therefore, you should | |
116 normally use @code{set-buffer} within a @code{save-current-buffer} or | |
117 @code{save-excursion} (@pxref{Excursions}) form that will restore the | |
118 current buffer when your function is done. Here is an example, the | |
119 code for the command @code{append-to-buffer} (with the documentation | |
120 string abridged): | |
121 | |
122 @example | |
123 @group | |
124 (defun append-to-buffer (buffer start end) | |
125 "Append to specified buffer the text of the region. | |
126 @dots{}" | |
127 (interactive "BAppend to buffer: \nr") | |
128 (let ((oldbuf (current-buffer))) | |
129 (save-current-buffer | |
130 (set-buffer (get-buffer-create buffer)) | |
131 (insert-buffer-substring oldbuf start end)))) | |
132 @end group | |
133 @end example | |
134 | |
135 @noindent | |
136 This function binds a local variable to record the current buffer, and | |
137 then @code{save-current-buffer} arranges to make it current again. | |
138 Next, @code{set-buffer} makes the specified buffer current. Finally, | |
139 @code{insert-buffer-substring} copies the string from the original | |
140 current buffer to the specified (and now current) buffer. | |
141 | |
142 If the buffer appended to happens to be displayed in some window, | |
143 the next redisplay will show how its text has changed. Otherwise, you | |
144 will not see the change immediately on the screen. The buffer becomes | |
145 current temporarily during the execution of the command, but this does | |
146 not cause it to be displayed. | |
147 | |
148 If you make local bindings (with @code{let} or function arguments) for | |
149 a variable that may also have buffer-local bindings, make sure that the | |
150 same buffer is current at the beginning and at the end of the local | |
151 binding's scope. Otherwise you might bind it in one buffer and unbind | |
152 it in another! There are two ways to do this. In simple cases, you may | |
153 see that nothing ever changes the current buffer within the scope of the | |
154 binding. Otherwise, use @code{save-current-buffer} or | |
155 @code{save-excursion} to make sure that the buffer current at the | |
156 beginning is current again whenever the variable is unbound. | |
157 | |
158 Do not rely on using @code{set-buffer} to change the current buffer | |
159 back, because that won't do the job if a quit happens while the wrong | |
160 buffer is current. Here is what @emph{not} to do: | |
161 | |
162 @example | |
163 @group | |
164 (let (buffer-read-only | |
165 (obuf (current-buffer))) | |
166 (set-buffer @dots{}) | |
167 @dots{} | |
168 (set-buffer obuf)) | |
169 @end group | |
170 @end example | |
171 | |
172 @noindent | |
173 Using @code{save-current-buffer}, as shown here, handles quitting, | |
174 errors, and @code{throw}, as well as ordinary evaluation. | |
175 | |
176 @example | |
177 @group | |
178 (let (buffer-read-only) | |
179 (save-current-buffer | |
180 (set-buffer @dots{}) | |
181 @dots{})) | |
182 @end group | |
183 @end example | |
184 | |
185 @defun current-buffer | |
186 This function returns the current buffer. | |
187 | |
188 @example | |
189 @group | |
190 (current-buffer) | |
191 @result{} #<buffer buffers.texi> | |
192 @end group | |
193 @end example | |
194 @end defun | |
195 | |
196 @defun set-buffer buffer-or-name | |
99126
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
197 This function makes @var{buffer-or-name} the current buffer. |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
198 @var{buffer-or-name} must be an existing buffer or the name of an |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
199 existing buffer. The return value is the buffer made current. |
84052 | 200 |
99082
82fc5c6c82f6
(Current Buffer): Reword documentation of set-buffer.
Martin Rudalics <rudalics@gmx.at>
parents:
99047
diff
changeset
|
201 This function does not display the buffer in any window, so the user |
82fc5c6c82f6
(Current Buffer): Reword documentation of set-buffer.
Martin Rudalics <rudalics@gmx.at>
parents:
99047
diff
changeset
|
202 cannot necessarily see the buffer. But Lisp programs will now operate |
82fc5c6c82f6
(Current Buffer): Reword documentation of set-buffer.
Martin Rudalics <rudalics@gmx.at>
parents:
99047
diff
changeset
|
203 on it. |
84052 | 204 @end defun |
205 | |
206 @defspec save-current-buffer body@dots{} | |
207 The @code{save-current-buffer} special form saves the identity of the | |
208 current buffer, evaluates the @var{body} forms, and finally restores | |
209 that buffer as current. The return value is the value of the last | |
210 form in @var{body}. The current buffer is restored even in case of an | |
211 abnormal exit via @code{throw} or error (@pxref{Nonlocal Exits}). | |
212 | |
213 If the buffer that used to be current has been killed by the time of | |
214 exit from @code{save-current-buffer}, then it is not made current again, | |
215 of course. Instead, whichever buffer was current just before exit | |
216 remains current. | |
217 @end defspec | |
218 | |
219 @defmac with-current-buffer buffer-or-name body@dots{} | |
220 The @code{with-current-buffer} macro saves the identity of the current | |
221 buffer, makes @var{buffer-or-name} current, evaluates the @var{body} | |
99126
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
222 forms, and finally restores the current buffer. @var{buffer-or-name} |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
223 must specify an existing buffer or the name of an existing buffer. |
84052 | 224 |
99126
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
225 The return value is the value of the last form in @var{body}. The |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
226 current buffer is restored even in case of an abnormal exit via |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
227 @code{throw} or error (@pxref{Nonlocal Exits}). |
84052 | 228 @end defmac |
229 | |
230 @defmac with-temp-buffer body@dots{} | |
231 @anchor{Definition of with-temp-buffer} | |
232 The @code{with-temp-buffer} macro evaluates the @var{body} forms | |
233 with a temporary buffer as the current buffer. It saves the identity of | |
234 the current buffer, creates a temporary buffer and makes it current, | |
235 evaluates the @var{body} forms, and finally restores the previous | |
236 current buffer while killing the temporary buffer. By default, undo | |
237 information (@pxref{Undo}) is not recorded in the buffer created by | |
238 this macro (but @var{body} can enable that, if needed). | |
239 | |
240 The return value is the value of the last form in @var{body}. You can | |
241 return the contents of the temporary buffer by using | |
242 @code{(buffer-string)} as the last form. | |
243 | |
244 The current buffer is restored even in case of an abnormal exit via | |
245 @code{throw} or error (@pxref{Nonlocal Exits}). | |
246 | |
247 See also @code{with-temp-file} in @ref{Definition of with-temp-file,, | |
248 Writing to Files}. | |
249 @end defmac | |
250 | |
251 @node Buffer Names | |
252 @section Buffer Names | |
253 @cindex buffer names | |
254 | |
255 Each buffer has a unique name, which is a string. Many of the | |
256 functions that work on buffers accept either a buffer or a buffer name | |
257 as an argument. Any argument called @var{buffer-or-name} is of this | |
258 sort, and an error is signaled if it is neither a string nor a buffer. | |
259 Any argument called @var{buffer} must be an actual buffer | |
260 object, not a name. | |
261 | |
262 @cindex hidden buffers | |
263 @cindex buffers without undo information | |
264 Buffers that are ephemeral and generally uninteresting to the user | |
265 have names starting with a space, so that the @code{list-buffers} and | |
266 @code{buffer-menu} commands don't mention them (but if such a buffer | |
267 visits a file, it @strong{is} mentioned). A name starting with | |
268 space also initially disables recording undo information; see | |
269 @ref{Undo}. | |
270 | |
271 @defun buffer-name &optional buffer | |
99082
82fc5c6c82f6
(Current Buffer): Reword documentation of set-buffer.
Martin Rudalics <rudalics@gmx.at>
parents:
99047
diff
changeset
|
272 This function returns the name of @var{buffer} as a string. |
82fc5c6c82f6
(Current Buffer): Reword documentation of set-buffer.
Martin Rudalics <rudalics@gmx.at>
parents:
99047
diff
changeset
|
273 @var{buffer} defaults to the current buffer. |
84052 | 274 |
275 If @code{buffer-name} returns @code{nil}, it means that @var{buffer} | |
276 has been killed. @xref{Killing Buffers}. | |
277 | |
278 @example | |
279 @group | |
280 (buffer-name) | |
281 @result{} "buffers.texi" | |
282 @end group | |
283 | |
284 @group | |
285 (setq foo (get-buffer "temp")) | |
286 @result{} #<buffer temp> | |
287 @end group | |
288 @group | |
289 (kill-buffer foo) | |
290 @result{} nil | |
291 @end group | |
292 @group | |
293 (buffer-name foo) | |
294 @result{} nil | |
295 @end group | |
296 @group | |
297 foo | |
298 @result{} #<killed buffer> | |
299 @end group | |
300 @end example | |
301 @end defun | |
302 | |
303 @deffn Command rename-buffer newname &optional unique | |
304 This function renames the current buffer to @var{newname}. An error | |
305 is signaled if @var{newname} is not a string. | |
306 | |
307 @c Emacs 19 feature | |
308 Ordinarily, @code{rename-buffer} signals an error if @var{newname} is | |
309 already in use. However, if @var{unique} is non-@code{nil}, it modifies | |
310 @var{newname} to make a name that is not in use. Interactively, you can | |
311 make @var{unique} non-@code{nil} with a numeric prefix argument. | |
312 (This is how the command @code{rename-uniquely} is implemented.) | |
313 | |
314 This function returns the name actually given to the buffer. | |
315 @end deffn | |
316 | |
317 @defun get-buffer buffer-or-name | |
318 This function returns the buffer specified by @var{buffer-or-name}. | |
319 If @var{buffer-or-name} is a string and there is no buffer with that | |
320 name, the value is @code{nil}. If @var{buffer-or-name} is a buffer, it | |
321 is returned as given; that is not very useful, so the argument is usually | |
322 a name. For example: | |
323 | |
324 @example | |
325 @group | |
326 (setq b (get-buffer "lewis")) | |
327 @result{} #<buffer lewis> | |
328 @end group | |
329 @group | |
330 (get-buffer b) | |
331 @result{} #<buffer lewis> | |
332 @end group | |
333 @group | |
334 (get-buffer "Frazzle-nots") | |
335 @result{} nil | |
336 @end group | |
337 @end example | |
338 | |
339 See also the function @code{get-buffer-create} in @ref{Creating Buffers}. | |
340 @end defun | |
341 | |
342 @c Emacs 19 feature | |
343 @defun generate-new-buffer-name starting-name &optional ignore | |
344 This function returns a name that would be unique for a new buffer---but | |
345 does not create the buffer. It starts with @var{starting-name}, and | |
346 produces a name not currently in use for any buffer by appending a | |
347 number inside of @samp{<@dots{}>}. It starts at 2 and keeps | |
348 incrementing the number until it is not the name of an existing buffer. | |
349 | |
350 If the optional second argument @var{ignore} is non-@code{nil}, it | |
351 should be a string, a potential buffer name. It means to consider | |
352 that potential buffer acceptable, if it is tried, even it is the name | |
353 of an existing buffer (which would normally be rejected). Thus, if | |
354 buffers named @samp{foo}, @samp{foo<2>}, @samp{foo<3>} and | |
355 @samp{foo<4>} exist, | |
356 | |
357 @example | |
358 (generate-new-buffer-name "foo") | |
359 @result{} "foo<5>" | |
360 (generate-new-buffer-name "foo" "foo<3>") | |
361 @result{} "foo<3>" | |
362 (generate-new-buffer-name "foo" "foo<6>") | |
363 @result{} "foo<5>" | |
364 @end example | |
365 | |
366 See the related function @code{generate-new-buffer} in @ref{Creating | |
367 Buffers}. | |
368 @end defun | |
369 | |
370 @node Buffer File Name | |
371 @section Buffer File Name | |
372 @cindex visited file | |
373 @cindex buffer file name | |
374 @cindex file name of buffer | |
375 | |
376 The @dfn{buffer file name} is the name of the file that is visited in | |
377 that buffer. When a buffer is not visiting a file, its buffer file name | |
378 is @code{nil}. Most of the time, the buffer name is the same as the | |
379 nondirectory part of the buffer file name, but the buffer file name and | |
380 the buffer name are distinct and can be set independently. | |
381 @xref{Visiting Files}. | |
382 | |
383 @defun buffer-file-name &optional buffer | |
384 This function returns the absolute file name of the file that | |
385 @var{buffer} is visiting. If @var{buffer} is not visiting any file, | |
386 @code{buffer-file-name} returns @code{nil}. If @var{buffer} is not | |
387 supplied, it defaults to the current buffer. | |
388 | |
389 @example | |
390 @group | |
391 (buffer-file-name (other-buffer)) | |
392 @result{} "/usr/user/lewis/manual/files.texi" | |
393 @end group | |
394 @end example | |
395 @end defun | |
396 | |
397 @defvar buffer-file-name | |
398 This buffer-local variable contains the name of the file being visited | |
399 in the current buffer, or @code{nil} if it is not visiting a file. It | |
400 is a permanent local variable, unaffected by | |
401 @code{kill-all-local-variables}. | |
402 | |
403 @example | |
404 @group | |
405 buffer-file-name | |
406 @result{} "/usr/user/lewis/manual/buffers.texi" | |
407 @end group | |
408 @end example | |
409 | |
410 It is risky to change this variable's value without doing various other | |
411 things. Normally it is better to use @code{set-visited-file-name} (see | |
412 below); some of the things done there, such as changing the buffer name, | |
413 are not strictly necessary, but others are essential to avoid confusing | |
414 Emacs. | |
415 @end defvar | |
416 | |
417 @defvar buffer-file-truename | |
418 This buffer-local variable holds the abbreviated truename of the file | |
419 visited in the current buffer, or @code{nil} if no file is visited. | |
420 It is a permanent local, unaffected by | |
421 @code{kill-all-local-variables}. @xref{Truenames}, and | |
422 @ref{Definition of abbreviate-file-name}. | |
423 @end defvar | |
424 | |
425 @defvar buffer-file-number | |
426 This buffer-local variable holds the file number and directory device | |
427 number of the file visited in the current buffer, or @code{nil} if no | |
428 file or a nonexistent file is visited. It is a permanent local, | |
429 unaffected by @code{kill-all-local-variables}. | |
430 | |
431 The value is normally a list of the form @code{(@var{filenum} | |
432 @var{devnum})}. This pair of numbers uniquely identifies the file among | |
433 all files accessible on the system. See the function | |
434 @code{file-attributes}, in @ref{File Attributes}, for more information | |
435 about them. | |
436 | |
437 If @code{buffer-file-name} is the name of a symbolic link, then both | |
438 numbers refer to the recursive target. | |
439 @end defvar | |
440 | |
441 @defun get-file-buffer filename | |
442 This function returns the buffer visiting file @var{filename}. If | |
443 there is no such buffer, it returns @code{nil}. The argument | |
444 @var{filename}, which must be a string, is expanded (@pxref{File Name | |
445 Expansion}), then compared against the visited file names of all live | |
446 buffers. Note that the buffer's @code{buffer-file-name} must match | |
447 the expansion of @var{filename} exactly. This function will not | |
448 recognize other names for the same file. | |
449 | |
450 @example | |
451 @group | |
452 (get-file-buffer "buffers.texi") | |
453 @result{} #<buffer buffers.texi> | |
454 @end group | |
455 @end example | |
456 | |
457 In unusual circumstances, there can be more than one buffer visiting | |
458 the same file name. In such cases, this function returns the first | |
459 such buffer in the buffer list. | |
460 @end defun | |
461 | |
462 @defun find-buffer-visiting filename &optional predicate | |
463 This is like @code{get-file-buffer}, except that it can return any | |
464 buffer visiting the file @emph{possibly under a different name}. That | |
465 is, the buffer's @code{buffer-file-name} does not need to match the | |
466 expansion of @var{filename} exactly, it only needs to refer to the | |
467 same file. If @var{predicate} is non-@code{nil}, it should be a | |
468 function of one argument, a buffer visiting @var{filename}. The | |
469 buffer is only considered a suitable return value if @var{predicate} | |
470 returns non-@code{nil}. If it can not find a suitable buffer to | |
471 return, @code{find-buffer-visiting} returns @code{nil}. | |
472 @end defun | |
473 | |
474 @deffn Command set-visited-file-name filename &optional no-query along-with-file | |
475 If @var{filename} is a non-empty string, this function changes the | |
476 name of the file visited in the current buffer to @var{filename}. (If the | |
477 buffer had no visited file, this gives it one.) The @emph{next time} | |
478 the buffer is saved it will go in the newly-specified file. | |
479 | |
480 This command marks the buffer as modified, since it does not (as far | |
481 as Emacs knows) match the contents of @var{filename}, even if it | |
482 matched the former visited file. It also renames the buffer to | |
483 correspond to the new file name, unless the new name is already in | |
484 use. | |
485 | |
486 If @var{filename} is @code{nil} or the empty string, that stands for | |
487 ``no visited file.'' In this case, @code{set-visited-file-name} marks | |
488 the buffer as having no visited file, without changing the buffer's | |
489 modified flag. | |
490 | |
491 Normally, this function asks the user for confirmation if there | |
492 already is a buffer visiting @var{filename}. If @var{no-query} is | |
493 non-@code{nil}, that prevents asking this question. If there already | |
494 is a buffer visiting @var{filename}, and the user confirms or | |
495 @var{query} is non-@code{nil}, this function makes the new buffer name | |
496 unique by appending a number inside of @samp{<@dots{}>} to @var{filename}. | |
497 | |
498 If @var{along-with-file} is non-@code{nil}, that means to assume that | |
499 the former visited file has been renamed to @var{filename}. In this | |
500 case, the command does not change the buffer's modified flag, nor the | |
501 buffer's recorded last file modification time as reported by | |
502 @code{visited-file-modtime} (@pxref{Modification Time}). If | |
503 @var{along-with-file} is @code{nil}, this function clears the recorded | |
504 last file modification time, after which @code{visited-file-modtime} | |
505 returns zero. | |
506 | |
507 @c Wordy to avoid overfull hbox. --rjc 16mar92 | |
508 When the function @code{set-visited-file-name} is called interactively, it | |
509 prompts for @var{filename} in the minibuffer. | |
510 @end deffn | |
511 | |
512 @defvar list-buffers-directory | |
513 This buffer-local variable specifies a string to display in a buffer | |
514 listing where the visited file name would go, for buffers that don't | |
515 have a visited file name. Dired buffers use this variable. | |
516 @end defvar | |
517 | |
518 @node Buffer Modification | |
519 @section Buffer Modification | |
520 @cindex buffer modification | |
521 @cindex modification flag (of buffer) | |
522 | |
523 Emacs keeps a flag called the @dfn{modified flag} for each buffer, to | |
524 record whether you have changed the text of the buffer. This flag is | |
525 set to @code{t} whenever you alter the contents of the buffer, and | |
526 cleared to @code{nil} when you save it. Thus, the flag shows whether | |
527 there are unsaved changes. The flag value is normally shown in the mode | |
528 line (@pxref{Mode Line Variables}), and controls saving (@pxref{Saving | |
529 Buffers}) and auto-saving (@pxref{Auto-Saving}). | |
530 | |
531 Some Lisp programs set the flag explicitly. For example, the function | |
532 @code{set-visited-file-name} sets the flag to @code{t}, because the text | |
533 does not match the newly-visited file, even if it is unchanged from the | |
534 file formerly visited. | |
535 | |
536 The functions that modify the contents of buffers are described in | |
537 @ref{Text}. | |
538 | |
539 @defun buffer-modified-p &optional buffer | |
540 This function returns @code{t} if the buffer @var{buffer} has been modified | |
541 since it was last read in from a file or saved, or @code{nil} | |
542 otherwise. If @var{buffer} is not supplied, the current buffer | |
543 is tested. | |
544 @end defun | |
545 | |
546 @defun set-buffer-modified-p flag | |
547 This function marks the current buffer as modified if @var{flag} is | |
548 non-@code{nil}, or as unmodified if the flag is @code{nil}. | |
549 | |
550 Another effect of calling this function is to cause unconditional | |
551 redisplay of the mode line for the current buffer. In fact, the | |
552 function @code{force-mode-line-update} works by doing this: | |
553 | |
554 @example | |
555 @group | |
556 (set-buffer-modified-p (buffer-modified-p)) | |
557 @end group | |
558 @end example | |
559 @end defun | |
560 | |
561 @defun restore-buffer-modified-p flag | |
562 Like @code{set-buffer-modified-p}, but does not force redisplay | |
563 of mode lines. | |
564 @end defun | |
565 | |
566 @deffn Command not-modified &optional arg | |
567 This command marks the current buffer as unmodified, and not needing | |
568 to be saved. If @var{arg} is non-@code{nil}, it marks the buffer as | |
569 modified, so that it will be saved at the next suitable occasion. | |
570 Interactively, @var{arg} is the prefix argument. | |
571 | |
572 Don't use this function in programs, since it prints a message in the | |
573 echo area; use @code{set-buffer-modified-p} (above) instead. | |
574 @end deffn | |
575 | |
576 @defun buffer-modified-tick &optional buffer | |
577 This function returns @var{buffer}'s modification-count. This is a | |
578 counter that increments every time the buffer is modified. If | |
579 @var{buffer} is @code{nil} (or omitted), the current buffer is used. | |
580 The counter can wrap around occasionally. | |
581 @end defun | |
582 | |
583 @defun buffer-chars-modified-tick &optional buffer | |
584 This function returns @var{buffer}'s character-change modification-count. | |
585 Changes to text properties leave this counter unchanged; however, each | |
586 time text is inserted or removed from the buffer, the counter is reset | |
87903 | 587 to the value that would be returned by @code{buffer-modified-tick}. |
84052 | 588 By comparing the values returned by two @code{buffer-chars-modified-tick} |
589 calls, you can tell whether a character change occurred in that buffer | |
590 in between the calls. If @var{buffer} is @code{nil} (or omitted), the | |
591 current buffer is used. | |
592 @end defun | |
593 | |
594 @node Modification Time | |
595 @comment node-name, next, previous, up | |
596 @section Buffer Modification Time | |
597 @cindex comparing file modification time | |
598 @cindex modification time of buffer | |
599 | |
600 Suppose that you visit a file and make changes in its buffer, and | |
601 meanwhile the file itself is changed on disk. At this point, saving the | |
602 buffer would overwrite the changes in the file. Occasionally this may | |
603 be what you want, but usually it would lose valuable information. Emacs | |
604 therefore checks the file's modification time using the functions | |
605 described below before saving the file. (@xref{File Attributes}, | |
606 for how to examine a file's modification time.) | |
607 | |
608 @defun verify-visited-file-modtime buffer | |
609 This function compares what @var{buffer} has recorded for the | |
610 modification time of its visited file against the actual modification | |
611 time of the file as recorded by the operating system. The two should be | |
612 the same unless some other process has written the file since Emacs | |
613 visited or saved it. | |
614 | |
615 The function returns @code{t} if the last actual modification time and | |
616 Emacs's recorded modification time are the same, @code{nil} otherwise. | |
617 It also returns @code{t} if the buffer has no recorded last | |
618 modification time, that is if @code{visited-file-modtime} would return | |
619 zero. | |
620 | |
621 It always returns @code{t} for buffers that are not visiting a file, | |
622 even if @code{visited-file-modtime} returns a non-zero value. For | |
623 instance, it always returns @code{t} for dired buffers. It returns | |
624 @code{t} for buffers that are visiting a file that does not exist and | |
625 never existed, but @code{nil} for file-visiting buffers whose file has | |
626 been deleted. | |
627 @end defun | |
628 | |
629 @defun clear-visited-file-modtime | |
630 This function clears out the record of the last modification time of | |
631 the file being visited by the current buffer. As a result, the next | |
632 attempt to save this buffer will not complain of a discrepancy in | |
633 file modification times. | |
634 | |
635 This function is called in @code{set-visited-file-name} and other | |
636 exceptional places where the usual test to avoid overwriting a changed | |
637 file should not be done. | |
638 @end defun | |
639 | |
640 @c Emacs 19 feature | |
641 @defun visited-file-modtime | |
642 This function returns the current buffer's recorded last file | |
643 modification time, as a list of the form @code{(@var{high} @var{low})}. | |
644 (This is the same format that @code{file-attributes} uses to return | |
645 time values; see @ref{File Attributes}.) | |
646 | |
647 If the buffer has no recorded last modification time, this function | |
648 returns zero. This case occurs, for instance, if the buffer is not | |
649 visiting a file or if the time has been explicitly cleared by | |
650 @code{clear-visited-file-modtime}. Note, however, that | |
651 @code{visited-file-modtime} returns a list for some non-file buffers | |
652 too. For instance, in a Dired buffer listing a directory, it returns | |
653 the last modification time of that directory, as recorded by Dired. | |
654 | |
655 For a new buffer visiting a not yet existing file, @var{high} is | |
656 @minus{}1 and @var{low} is 65535, that is, | |
657 @ifnottex | |
658 @w{2**16 - 1.} | |
659 @end ifnottex | |
660 @tex | |
661 @math{2^{16}-1}. | |
662 @end tex | |
663 @end defun | |
664 | |
665 @c Emacs 19 feature | |
666 @defun set-visited-file-modtime &optional time | |
667 This function updates the buffer's record of the last modification time | |
668 of the visited file, to the value specified by @var{time} if @var{time} | |
669 is not @code{nil}, and otherwise to the last modification time of the | |
670 visited file. | |
671 | |
672 If @var{time} is neither @code{nil} nor zero, it should have the form | |
673 @code{(@var{high} . @var{low})} or @code{(@var{high} @var{low})}, in | |
674 either case containing two integers, each of which holds 16 bits of the | |
675 time. | |
676 | |
677 This function is useful if the buffer was not read from the file | |
678 normally, or if the file itself has been changed for some known benign | |
679 reason. | |
680 @end defun | |
681 | |
682 @defun ask-user-about-supersession-threat filename | |
683 This function is used to ask a user how to proceed after an attempt to | |
684 modify an buffer visiting file @var{filename} when the file is newer | |
685 than the buffer text. Emacs detects this because the modification | |
686 time of the file on disk is newer than the last save-time of the | |
687 buffer. This means some other program has probably altered the file. | |
688 | |
689 @kindex file-supersession | |
690 Depending on the user's answer, the function may return normally, in | |
691 which case the modification of the buffer proceeds, or it may signal a | |
692 @code{file-supersession} error with data @code{(@var{filename})}, in which | |
693 case the proposed buffer modification is not allowed. | |
694 | |
695 This function is called automatically by Emacs on the proper | |
696 occasions. It exists so you can customize Emacs by redefining it. | |
697 See the file @file{userlock.el} for the standard definition. | |
698 | |
699 See also the file locking mechanism in @ref{File Locks}. | |
700 @end defun | |
701 | |
702 @node Read Only Buffers | |
703 @section Read-Only Buffers | |
704 @cindex read-only buffer | |
705 @cindex buffer, read-only | |
706 | |
707 If a buffer is @dfn{read-only}, then you cannot change its contents, | |
708 although you may change your view of the contents by scrolling and | |
709 narrowing. | |
710 | |
711 Read-only buffers are used in two kinds of situations: | |
712 | |
713 @itemize @bullet | |
714 @item | |
715 A buffer visiting a write-protected file is normally read-only. | |
716 | |
717 Here, the purpose is to inform the user that editing the buffer with the | |
718 aim of saving it in the file may be futile or undesirable. The user who | |
719 wants to change the buffer text despite this can do so after clearing | |
720 the read-only flag with @kbd{C-x C-q}. | |
721 | |
722 @item | |
723 Modes such as Dired and Rmail make buffers read-only when altering the | |
724 contents with the usual editing commands would probably be a mistake. | |
725 | |
726 The special commands of these modes bind @code{buffer-read-only} to | |
727 @code{nil} (with @code{let}) or bind @code{inhibit-read-only} to | |
728 @code{t} around the places where they themselves change the text. | |
729 @end itemize | |
730 | |
731 @defvar buffer-read-only | |
732 This buffer-local variable specifies whether the buffer is read-only. | |
733 The buffer is read-only if this variable is non-@code{nil}. | |
734 @end defvar | |
735 | |
736 @defvar inhibit-read-only | |
737 If this variable is non-@code{nil}, then read-only buffers and, | |
738 depending on the actual value, some or all read-only characters may be | |
739 modified. Read-only characters in a buffer are those that have | |
740 non-@code{nil} @code{read-only} properties (either text properties or | |
741 overlay properties). @xref{Special Properties}, for more information | |
742 about text properties. @xref{Overlays}, for more information about | |
743 overlays and their properties. | |
744 | |
745 If @code{inhibit-read-only} is @code{t}, all @code{read-only} character | |
746 properties have no effect. If @code{inhibit-read-only} is a list, then | |
747 @code{read-only} character properties have no effect if they are members | |
748 of the list (comparison is done with @code{eq}). | |
749 @end defvar | |
750 | |
751 @deffn Command toggle-read-only &optional arg | |
752 This command toggles whether the current buffer is read-only. It is | |
753 intended for interactive use; do not use it in programs. At any given | |
754 point in a program, you should know whether you want the read-only flag | |
755 on or off; so you can set @code{buffer-read-only} explicitly to the | |
756 proper value, @code{t} or @code{nil}. | |
757 | |
758 If @var{arg} is non-@code{nil}, it should be a raw prefix argument. | |
759 @code{toggle-read-only} sets @code{buffer-read-only} to @code{t} if | |
760 the numeric value of that prefix argument is positive and to | |
761 @code{nil} otherwise. @xref{Prefix Command Arguments}. | |
762 @end deffn | |
763 | |
764 @defun barf-if-buffer-read-only | |
765 This function signals a @code{buffer-read-only} error if the current | |
766 buffer is read-only. @xref{Using Interactive}, for another way to | |
767 signal an error if the current buffer is read-only. | |
768 @end defun | |
769 | |
770 @node The Buffer List | |
771 @section The Buffer List | |
772 @cindex buffer list | |
773 | |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
774 The @dfn{buffer list} is a list of all live buffers. The order of the |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
775 buffers in this list is based primarily on how recently each buffer has |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
776 been displayed in a window. Several functions, notably |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
777 @code{other-buffer}, use this ordering. A buffer list displayed for the |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
778 user also follows this order. |
84052 | 779 |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
780 Creating a buffer adds it to the end of the buffer list, and killing a |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
781 buffer removes it from that list. A buffer moves to the front of this |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
782 list whenever it is chosen for display in a window (@pxref{Displaying |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
783 Buffers}) or a window displaying it is selected (@pxref{Selecting |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
784 Windows}). A buffer moves to the end of the list when it is buried (see |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
785 @code{bury-buffer}, below). There are no functions available to the |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
786 Lisp programmer which directly manipulate the buffer list. |
87903 | 787 |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
788 In addition to the fundamental buffer list just described, Emacs |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
789 maintains a local buffer list for each frame, in which the buffers that |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
790 have been displayed (or had their windows selected) in that frame come |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
791 first. (This order is recorded in the frame's @code{buffer-list} frame |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
792 parameter; see @ref{Buffer Parameters}.) Buffers never displayed in |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
793 that frame come afterward, ordered according to the fundamental buffer |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
794 list. |
84052 | 795 |
796 @defun buffer-list &optional frame | |
797 This function returns the buffer list, including all buffers, even those | |
798 whose names begin with a space. The elements are actual buffers, not | |
799 their names. | |
800 | |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
801 If @var{frame} is a frame, this returns @var{frame}'s local buffer list. |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
802 If @var{frame} is @code{nil} or omitted, the fundamental buffer list is |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
803 used: the buffers appear in order of most recent display or selection, |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
804 regardless of which frames they were displayed on. |
84052 | 805 |
806 @example | |
807 @group | |
808 (buffer-list) | |
809 @result{} (#<buffer buffers.texi> | |
810 #<buffer *Minibuf-1*> #<buffer buffer.c> | |
811 #<buffer *Help*> #<buffer TAGS>) | |
812 @end group | |
813 | |
814 @group | |
815 ;; @r{Note that the name of the minibuffer} | |
816 ;; @r{begins with a space!} | |
817 (mapcar (function buffer-name) (buffer-list)) | |
818 @result{} ("buffers.texi" " *Minibuf-1*" | |
819 "buffer.c" "*Help*" "TAGS") | |
820 @end group | |
821 @end example | |
822 @end defun | |
823 | |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
824 The list returned by @code{buffer-list} is constructed specifically; |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
825 it is not an internal Emacs data structure, and modifying it has no |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
826 effect on the order of buffers. If you want to change the order of |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
827 buffers in the fundamental buffer list, here is an easy way: |
84052 | 828 |
829 @example | |
830 (defun reorder-buffer-list (new-list) | |
831 (while new-list | |
832 (bury-buffer (car new-list)) | |
833 (setq new-list (cdr new-list)))) | |
834 @end example | |
835 | |
836 With this method, you can specify any order for the list, but there is | |
837 no danger of losing a buffer or adding something that is not a valid | |
838 live buffer. | |
839 | |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
840 To change the order or value of a specific frame's buffer list, set |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
841 that frame's @code{buffer-list} parameter with |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
842 @code{modify-frame-parameters} (@pxref{Parameter Access}). |
84052 | 843 |
844 @defun other-buffer &optional buffer visible-ok frame | |
845 This function returns the first buffer in the buffer list other than | |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
846 @var{buffer}. Usually, this is the buffer appearing in the most |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
847 recently selected window (in frame @var{frame} or else the selected |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
848 frame, @pxref{Input Focus}), aside from @var{buffer}. Buffers whose |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
849 names start with a space are not considered at all. |
84052 | 850 |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
851 If @var{buffer} is not supplied (or if it is not a live buffer), then |
84052 | 852 @code{other-buffer} returns the first buffer in the selected frame's |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
853 local buffer list. (If @var{frame} is non-@code{nil}, it returns the |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
854 first buffer in @var{frame}'s local buffer list instead.) |
84052 | 855 |
856 If @var{frame} has a non-@code{nil} @code{buffer-predicate} parameter, | |
857 then @code{other-buffer} uses that predicate to decide which buffers to | |
858 consider. It calls the predicate once for each buffer, and if the value | |
859 is @code{nil}, that buffer is ignored. @xref{Buffer Parameters}. | |
860 | |
861 @c Emacs 19 feature | |
862 If @var{visible-ok} is @code{nil}, @code{other-buffer} avoids returning | |
863 a buffer visible in any window on any visible frame, except as a last | |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
864 resort. If @var{visible-ok} is non-@code{nil}, then it does not matter |
84052 | 865 whether a buffer is displayed somewhere or not. |
866 | |
867 If no suitable buffer exists, the buffer @samp{*scratch*} is returned | |
868 (and created, if necessary). | |
869 @end defun | |
870 | |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
871 @defun last-buffer &optional buffer visible-ok frame |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
872 This function returns the last buffer in @var{frame}'s buffer list other |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
873 than @var{BUFFER}. If @var{frame} is omitted or @code{nil}, it uses the |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
874 selected frame's buffer list. |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
875 |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
876 The argument @var{visible-ok} is handled as with @code{other-buffer}, |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
877 see above. If no suitable buffer can be found, the buffer |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
878 @samp{*scratch*} is returned. |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
879 @end defun |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
880 |
84052 | 881 @deffn Command bury-buffer &optional buffer-or-name |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
882 This command puts @var{buffer-or-name} at the end of the buffer list, |
84052 | 883 without changing the order of any of the other buffers on the list. |
884 This buffer therefore becomes the least desirable candidate for | |
885 @code{other-buffer} to return. The argument can be either a buffer | |
886 itself or the name of one. | |
887 | |
888 @code{bury-buffer} operates on each frame's @code{buffer-list} parameter | |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
889 as well as the fundamental buffer list; therefore, the buffer that you |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
890 bury will come last in the value of @code{(buffer-list @var{frame})} and |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
891 in the value of @code{(buffer-list)}. |
84052 | 892 |
893 If @var{buffer-or-name} is @code{nil} or omitted, this means to bury the | |
894 current buffer. In addition, if the buffer is displayed in the selected | |
895 window, this switches to some other buffer (obtained using | |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
896 @code{other-buffer}) in the selected window. @xref{Displaying Buffers}. |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
897 But if the selected window is dedicated to its buffer, it deletes that |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
898 window if there are other windows left on its frame. Otherwise, if the |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
899 selected window is the only window on its frame, it iconifies that |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
900 frame. If @var{buffer-or-name} is displayed in some other window, it |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
901 remains displayed there. |
84052 | 902 |
903 To replace a buffer in all the windows that display it, use | |
904 @code{replace-buffer-in-windows}. @xref{Buffers and Windows}. | |
905 @end deffn | |
906 | |
100804
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
907 @deffn Command unbury-buffer |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
908 This command switches to the last buffer in the local buffer list of the |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
909 selected frame. More precisely, it calls the function |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
910 @code{switch-to-buffer} (@pxref{Displaying Buffers}), to display the |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
911 buffer returned by @code{last-buffer}, see above, in the selected |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
912 window. |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
913 @end deffn |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
914 |
007ec92e4924
(The Buffer List): Clarify what moves a buffer to
Martin Rudalics <rudalics@gmx.at>
parents:
99126
diff
changeset
|
915 |
84052 | 916 @node Creating Buffers |
917 @section Creating Buffers | |
918 @cindex creating buffers | |
919 @cindex buffers, creating | |
920 | |
921 This section describes the two primitives for creating buffers. | |
922 @code{get-buffer-create} creates a buffer if it finds no existing buffer | |
923 with the specified name; @code{generate-new-buffer} always creates a new | |
924 buffer and gives it a unique name. | |
925 | |
926 Other functions you can use to create buffers include | |
927 @code{with-output-to-temp-buffer} (@pxref{Temporary Displays}) and | |
928 @code{create-file-buffer} (@pxref{Visiting Files}). Starting a | |
929 subprocess can also create a buffer (@pxref{Processes}). | |
930 | |
99082
82fc5c6c82f6
(Current Buffer): Reword documentation of set-buffer.
Martin Rudalics <rudalics@gmx.at>
parents:
99047
diff
changeset
|
931 @defun get-buffer-create buffer-or-name |
99126
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
932 This function returns a buffer named @var{buffer-or-name}. The buffer |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
933 returned does not become the current buffer---this function does not |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
934 change which buffer is current. |
84052 | 935 |
99126
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
936 @var{buffer-or-name} must be either a string or an existing buffer. If |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
937 it is a string and a live buffer with that name already exists, |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
938 @code{get-buffer-create} returns that buffer. If no such buffer exists, |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
939 it creates a new buffer. If @var{buffer-or-name} is a buffer instead of |
b7fa14d891a6
(Current Buffer): Reword set-buffer and
Martin Rudalics <rudalics@gmx.at>
parents:
99082
diff
changeset
|
940 a string, it is returned as given, even if it is dead. |
84052 | 941 |
942 @example | |
943 @group | |
944 (get-buffer-create "foo") | |
945 @result{} #<buffer foo> | |
946 @end group | |
947 @end example | |
948 | |
949 The major mode for a newly created buffer is set to Fundamental mode. | |
950 (The variable @code{default-major-mode} is handled at a higher level; | |
951 see @ref{Auto Major Mode}.) If the name begins with a space, the | |
952 buffer initially disables undo information recording (@pxref{Undo}). | |
953 @end defun | |
954 | |
955 @defun generate-new-buffer name | |
956 This function returns a newly created, empty buffer, but does not make | |
957 it current. If there is no buffer named @var{name}, then that is the | |
958 name of the new buffer. If that name is in use, this function adds | |
959 suffixes of the form @samp{<@var{n}>} to @var{name}, where @var{n} is an | |
960 integer. It tries successive integers starting with 2 until it finds an | |
961 available name. | |
962 | |
963 An error is signaled if @var{name} is not a string. | |
964 | |
965 @example | |
966 @group | |
967 (generate-new-buffer "bar") | |
968 @result{} #<buffer bar> | |
969 @end group | |
970 @group | |
971 (generate-new-buffer "bar") | |
972 @result{} #<buffer bar<2>> | |
973 @end group | |
974 @group | |
975 (generate-new-buffer "bar") | |
976 @result{} #<buffer bar<3>> | |
977 @end group | |
978 @end example | |
979 | |
980 The major mode for the new buffer is set to Fundamental mode. The | |
981 variable @code{default-major-mode} is handled at a higher level. | |
982 @xref{Auto Major Mode}. | |
983 | |
984 See the related function @code{generate-new-buffer-name} in @ref{Buffer | |
985 Names}. | |
986 @end defun | |
987 | |
988 @node Killing Buffers | |
989 @section Killing Buffers | |
990 @cindex killing buffers | |
991 @cindex buffers, killing | |
992 | |
993 @dfn{Killing a buffer} makes its name unknown to Emacs and makes the | |
994 memory space it occupied available for other use. | |
995 | |
996 The buffer object for the buffer that has been killed remains in | |
997 existence as long as anything refers to it, but it is specially marked | |
998 so that you cannot make it current or display it. Killed buffers retain | |
999 their identity, however; if you kill two distinct buffers, they remain | |
1000 distinct according to @code{eq} although both are dead. | |
1001 | |
1002 If you kill a buffer that is current or displayed in a window, Emacs | |
1003 automatically selects or displays some other buffer instead. This means | |
1004 that killing a buffer can in general change the current buffer. | |
1005 Therefore, when you kill a buffer, you should also take the precautions | |
1006 associated with changing the current buffer (unless you happen to know | |
1007 that the buffer being killed isn't current). @xref{Current Buffer}. | |
1008 | |
1009 If you kill a buffer that is the base buffer of one or more indirect | |
1010 buffers, the indirect buffers are automatically killed as well. | |
1011 | |
1012 The @code{buffer-name} of a killed buffer is @code{nil}. You can use | |
1013 this feature to test whether a buffer has been killed: | |
1014 | |
1015 @example | |
1016 @group | |
1017 (defun buffer-killed-p (buffer) | |
1018 "Return t if BUFFER is killed." | |
1019 (not (buffer-name buffer))) | |
1020 @end group | |
1021 @end example | |
1022 | |
99036
26ffccc14770
(Killing Buffers): Update documentation of kill-buffer.
Martin Rudalics <rudalics@gmx.at>
parents:
98963
diff
changeset
|
1023 @deffn Command kill-buffer &optional buffer-or-name |
84052 | 1024 This function kills the buffer @var{buffer-or-name}, freeing all its |
1025 memory for other uses or to be returned to the operating system. If | |
99036
26ffccc14770
(Killing Buffers): Update documentation of kill-buffer.
Martin Rudalics <rudalics@gmx.at>
parents:
98963
diff
changeset
|
1026 @var{buffer-or-name} is @code{nil} or omitted, it kills the current |
26ffccc14770
(Killing Buffers): Update documentation of kill-buffer.
Martin Rudalics <rudalics@gmx.at>
parents:
98963
diff
changeset
|
1027 buffer. |
84052 | 1028 |
1029 Any processes that have this buffer as the @code{process-buffer} are | |
1030 sent the @code{SIGHUP} signal, which normally causes them to terminate. | |
1031 (The basic meaning of @code{SIGHUP} is that a dialup line has been | |
1032 disconnected.) @xref{Signals to Processes}. | |
1033 | |
1034 If the buffer is visiting a file and contains unsaved changes, | |
1035 @code{kill-buffer} asks the user to confirm before the buffer is killed. | |
1036 It does this even if not called interactively. To prevent the request | |
1037 for confirmation, clear the modified flag before calling | |
1038 @code{kill-buffer}. @xref{Buffer Modification}. | |
1039 | |
99047
1dcf806b4a8d
(Killing Buffers): Fix last change.
Eli Zaretskii <eliz@gnu.org>
parents:
99036
diff
changeset
|
1040 This function calls @code{replace-buffer-in-windows} for cleaning up |
1dcf806b4a8d
(Killing Buffers): Fix last change.
Eli Zaretskii <eliz@gnu.org>
parents:
99036
diff
changeset
|
1041 all windows currently displaying the buffer to be killed. |
99036
26ffccc14770
(Killing Buffers): Update documentation of kill-buffer.
Martin Rudalics <rudalics@gmx.at>
parents:
98963
diff
changeset
|
1042 |
84052 | 1043 Killing a buffer that is already dead has no effect. |
1044 | |
1045 This function returns @code{t} if it actually killed the buffer. It | |
1046 returns @code{nil} if the user refuses to confirm or if | |
1047 @var{buffer-or-name} was already dead. | |
1048 | |
1049 @smallexample | |
1050 (kill-buffer "foo.unchanged") | |
1051 @result{} t | |
1052 (kill-buffer "foo.changed") | |
1053 | |
1054 ---------- Buffer: Minibuffer ---------- | |
1055 Buffer foo.changed modified; kill anyway? (yes or no) @kbd{yes} | |
1056 ---------- Buffer: Minibuffer ---------- | |
1057 | |
1058 @result{} t | |
1059 @end smallexample | |
1060 @end deffn | |
1061 | |
1062 @defvar kill-buffer-query-functions | |
1063 After confirming unsaved changes, @code{kill-buffer} calls the functions | |
1064 in the list @code{kill-buffer-query-functions}, in order of appearance, | |
1065 with no arguments. The buffer being killed is the current buffer when | |
1066 they are called. The idea of this feature is that these functions will | |
1067 ask for confirmation from the user. If any of them returns @code{nil}, | |
1068 @code{kill-buffer} spares the buffer's life. | |
1069 @end defvar | |
1070 | |
1071 @defvar kill-buffer-hook | |
1072 This is a normal hook run by @code{kill-buffer} after asking all the | |
1073 questions it is going to ask, just before actually killing the buffer. | |
1074 The buffer to be killed is current when the hook functions run. | |
1075 @xref{Hooks}. This variable is a permanent local, so its local binding | |
1076 is not cleared by changing major modes. | |
1077 @end defvar | |
1078 | |
1079 @defvar buffer-offer-save | |
1080 This variable, if non-@code{nil} in a particular buffer, tells | |
1081 @code{save-buffers-kill-emacs} and @code{save-some-buffers} (if the | |
1082 second optional argument to that function is @code{t}) to offer to | |
1083 save that buffer, just as they offer to save file-visiting buffers. | |
1084 @xref{Definition of save-some-buffers}. The variable | |
1085 @code{buffer-offer-save} automatically becomes buffer-local when set | |
1086 for any reason. @xref{Buffer-Local Variables}. | |
1087 @end defvar | |
1088 | |
1089 @defvar buffer-save-without-query | |
1090 This variable, if non-@code{nil} in a particular buffer, tells | |
1091 @code{save-buffers-kill-emacs} and @code{save-some-buffers} to save | |
1092 this buffer (if it's modified) without asking the user. The variable | |
1093 automatically becomes buffer-local when set for any reason. | |
1094 @end defvar | |
1095 | |
1096 @defun buffer-live-p object | |
1097 This function returns @code{t} if @var{object} is a buffer which has | |
1098 not been killed, @code{nil} otherwise. | |
1099 @end defun | |
1100 | |
1101 @node Indirect Buffers | |
1102 @section Indirect Buffers | |
1103 @cindex indirect buffers | |
1104 @cindex base buffer | |
1105 | |
1106 An @dfn{indirect buffer} shares the text of some other buffer, which | |
1107 is called the @dfn{base buffer} of the indirect buffer. In some ways it | |
1108 is the analogue, for buffers, of a symbolic link among files. The base | |
1109 buffer may not itself be an indirect buffer. | |
1110 | |
1111 The text of the indirect buffer is always identical to the text of its | |
1112 base buffer; changes made by editing either one are visible immediately | |
1113 in the other. This includes the text properties as well as the characters | |
1114 themselves. | |
1115 | |
1116 In all other respects, the indirect buffer and its base buffer are | |
1117 completely separate. They have different names, independent values of | |
1118 point, independent narrowing, independent markers and overlays (though | |
1119 inserting or deleting text in either buffer relocates the markers and | |
1120 overlays for both), independent major modes, and independent | |
1121 buffer-local variable bindings. | |
1122 | |
1123 An indirect buffer cannot visit a file, but its base buffer can. If | |
1124 you try to save the indirect buffer, that actually saves the base | |
1125 buffer. | |
1126 | |
1127 Killing an indirect buffer has no effect on its base buffer. Killing | |
1128 the base buffer effectively kills the indirect buffer in that it cannot | |
1129 ever again be the current buffer. | |
1130 | |
1131 @deffn Command make-indirect-buffer base-buffer name &optional clone | |
1132 This creates and returns an indirect buffer named @var{name} whose | |
1133 base buffer is @var{base-buffer}. The argument @var{base-buffer} may | |
1134 be a live buffer or the name (a string) of an existing buffer. If | |
1135 @var{name} is the name of an existing buffer, an error is signaled. | |
1136 | |
1137 If @var{clone} is non-@code{nil}, then the indirect buffer originally | |
1138 shares the ``state'' of @var{base-buffer} such as major mode, minor | |
1139 modes, buffer local variables and so on. If @var{clone} is omitted | |
1140 or @code{nil} the indirect buffer's state is set to the default state | |
1141 for new buffers. | |
1142 | |
1143 If @var{base-buffer} is an indirect buffer, its base buffer is used as | |
1144 the base for the new buffer. If, in addition, @var{clone} is | |
1145 non-@code{nil}, the initial state is copied from the actual base | |
1146 buffer, not from @var{base-buffer}. | |
1147 @end deffn | |
1148 | |
1149 @defun clone-indirect-buffer newname display-flag &optional norecord | |
1150 This function creates and returns a new indirect buffer that shares | |
1151 the current buffer's base buffer and copies the rest of the current | |
1152 buffer's attributes. (If the current buffer is not indirect, it is | |
1153 used as the base buffer.) | |
1154 | |
1155 If @var{display-flag} is non-@code{nil}, that means to display the new | |
1156 buffer by calling @code{pop-to-buffer}. If @var{norecord} is | |
1157 non-@code{nil}, that means not to put the new buffer to the front of | |
1158 the buffer list. | |
1159 @end defun | |
1160 | |
1161 @defun buffer-base-buffer &optional buffer | |
1162 This function returns the base buffer of @var{buffer}, which defaults | |
1163 to the current buffer. If @var{buffer} is not indirect, the value is | |
1164 @code{nil}. Otherwise, the value is another buffer, which is never an | |
1165 indirect buffer. | |
1166 @end defun | |
1167 | |
98963
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1168 @node Swapping Text |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1169 @section Swapping Text Between Two Buffers |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1170 @cindex swap text between buffers |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1171 @cindex virtual buffers |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1172 |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1173 Specialized modes sometimes need to let the user access from the |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1174 same buffer several vastly different types of text. For example, you |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1175 may need to display a summary of the buffer text, in addition to |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1176 letting the user access the text itself. |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1177 |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1178 This could be implemented with multiple buffers (kept in sync when |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1179 the user edits the text), or with narrowing (@pxref{Narrowing}). But |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1180 these alternatives might sometimes become tedious or prohibitively |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1181 expensive, especially if each type of text requires expensive |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1182 buffer-global operations in order to provide correct display and |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1183 editing commands. |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1184 |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1185 Emacs provides another facility for such modes: you can quickly swap |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1186 buffer text between two buffers with @code{buffer-swap-text}. This |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1187 function is very fast because it doesn't move any text, it only |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1188 changes the internal data structures of the buffer object to point to |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1189 a different chunk of text. Using it, you can pretend that a group of |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1190 two or more buffers are actually a single virtual buffer that holds |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1191 the contents of all the individual buffers together. |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1192 |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1193 @defun buffer-swap-text buffer |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1194 This function swaps text between the current buffer and its argument |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1195 @var{buffer}. It signals an error if one of the two buffers is an |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1196 indirect buffer (@pxref{Indirect Buffers}) or is a base buffer of an |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1197 indirect buffer. |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1198 |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1199 All the buffer properties that are related to the buffer text are |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1200 swapped as well: the positions of point and mark, all the markers, the |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1201 overlays, the text properties, the undo list, the value of the |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1202 @code{enable-multibyte-characters} flag (@pxref{Text Representations, |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1203 enable-multibyte-characters}), etc. |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1204 @end defun |
5acd30038b76
(Swapping Text): New section, documents `buffer-swap-text'.
Eli Zaretskii <eliz@gnu.org>
parents:
87903
diff
changeset
|
1205 |
84052 | 1206 @node Buffer Gap |
1207 @section The Buffer Gap | |
1208 | |
1209 Emacs buffers are implemented using an invisible @dfn{gap} to make | |
1210 insertion and deletion faster. Insertion works by filling in part of | |
1211 the gap, and deletion adds to the gap. Of course, this means that the | |
1212 gap must first be moved to the locus of the insertion or deletion. | |
1213 Emacs moves the gap only when you try to insert or delete. This is why | |
1214 your first editing command in one part of a large buffer, after | |
1215 previously editing in another far-away part, sometimes involves a | |
1216 noticeable delay. | |
1217 | |
1218 This mechanism works invisibly, and Lisp code should never be affected | |
1219 by the gap's current location, but these functions are available for | |
1220 getting information about the gap status. | |
1221 | |
1222 @defun gap-position | |
1223 This function returns the current gap position in the current buffer. | |
1224 @end defun | |
1225 | |
1226 @defun gap-size | |
1227 This function returns the current gap size of the current buffer. | |
1228 @end defun | |
1229 | |
1230 @ignore | |
1231 arch-tag: 2e53cfab-5691-41f6-b5a8-9c6a3462399c | |
1232 @end ignore |