Commit | Line | Data |
---|---|---|
3e01fd9d RS |
1 | @c -*-texinfo-*- |
2 | @c This is part of the GNU Emacs Lisp Reference Manual. | |
3 | @c Copyright (C) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc. | |
4 | @c See the file elisp.texi for copying conditions. | |
5 | @setfilename ../info/files | |
6 | @node Files, Backups and Auto-Saving, Documentation, Top | |
7 | @comment node-name, next, previous, up | |
8 | @chapter Files | |
9 | ||
10 | In Emacs, you can find, create, view, save, and otherwise work with | |
11 | files and file directories. This chapter describes most of the | |
12 | file-related functions of Emacs Lisp, but a few others are described in | |
13 | @ref{Buffers}, and those related to backups and auto-saving are | |
14 | described in @ref{Backups and Auto-Saving}. | |
15 | ||
b22f3a19 RS |
16 | Many of the file functions take one or more arguments that are file |
17 | names. A file name is actually a string. Most of these functions | |
18 | expand file name arguments using @code{expand-file-name}, so that | |
19 | @file{~} is handled correctly, as are relative file names (including | |
20 | @samp{../}). These functions don't recognize environment variable | |
21 | substitutions such as @samp{$HOME}. @xref{File Name Expansion}. | |
22 | ||
3e01fd9d RS |
23 | @menu |
24 | * Visiting Files:: Reading files into Emacs buffers for editing. | |
25 | * Saving Buffers:: Writing changed buffers back into files. | |
26 | * Reading from Files:: Reading files into buffers without visiting. | |
27 | * Writing to Files:: Writing new files from parts of buffers. | |
28 | * File Locks:: Locking and unlocking files, to prevent | |
29 | simultaneous editing by two people. | |
30 | * Information about Files:: Testing existence, accessibility, size of files. | |
31 | * Changing File Attributes:: Renaming files, changing protection, etc. | |
32 | * File Names:: Decomposing and expanding file names. | |
33 | * Contents of Directories:: Getting a list of the files in a directory. | |
34 | * Create/Delete Dirs:: Creating and Deleting Directories. | |
35 | * Magic File Names:: Defining "magic" special handling | |
36 | for certain file names. | |
22697dac | 37 | * Format Conversion:: Conversion to and from various file formats. |
841e483d | 38 | * Files and MS-DOS:: Distinguishing text and binary files on MS-DOS. |
3e01fd9d RS |
39 | @end menu |
40 | ||
41 | @node Visiting Files | |
42 | @section Visiting Files | |
43 | @cindex finding files | |
44 | @cindex visiting files | |
45 | ||
46 | Visiting a file means reading a file into a buffer. Once this is | |
47 | done, we say that the buffer is @dfn{visiting} that file, and call the | |
48 | file ``the visited file'' of the buffer. | |
49 | ||
50 | A file and a buffer are two different things. A file is information | |
51 | recorded permanently in the computer (unless you delete it). A buffer, | |
52 | on the other hand, is information inside of Emacs that will vanish at | |
53 | the end of the editing session (or when you kill the buffer). Usually, | |
54 | a buffer contains information that you have copied from a file; then we | |
55 | say the buffer is visiting that file. The copy in the buffer is what | |
56 | you modify with editing commands. Such changes to the buffer do not | |
57 | change the file; therefore, to make the changes permanent, you must | |
58 | @dfn{save} the buffer, which means copying the altered buffer contents | |
59 | back into the file. | |
60 | ||
61 | In spite of the distinction between files and buffers, people often | |
62 | refer to a file when they mean a buffer and vice-versa. Indeed, we say, | |
b22f3a19 | 63 | ``I am editing a file,'' rather than, ``I am editing a buffer that I |
3e01fd9d RS |
64 | will soon save as a file of the same name.'' Humans do not usually need |
65 | to make the distinction explicit. When dealing with a computer program, | |
66 | however, it is good to keep the distinction in mind. | |
67 | ||
68 | @menu | |
69 | * Visiting Functions:: The usual interface functions for visiting. | |
70 | * Subroutines of Visiting:: Lower-level subroutines that they use. | |
71 | @end menu | |
72 | ||
73 | @node Visiting Functions | |
74 | @subsection Functions for Visiting Files | |
75 | ||
76 | This section describes the functions normally used to visit files. | |
77 | For historical reasons, these functions have names starting with | |
78 | @samp{find-} rather than @samp{visit-}. @xref{Buffer File Name}, for | |
79 | functions and variables that access the visited file name of a buffer or | |
80 | that find an existing buffer by its visited file name. | |
81 | ||
bfe721d1 KH |
82 | In a Lisp program, if you want to look at the contents of a file but |
83 | not alter it, the fastest way is to use @code{insert-file-contents} in a | |
84 | temporary buffer. Visiting the file is not necessary and takes longer. | |
85 | @xref{Reading from Files}. | |
86 | ||
3e01fd9d RS |
87 | @deffn Command find-file filename |
88 | This command selects a buffer visiting the file @var{filename}, | |
89 | using an existing buffer if there is one, and otherwise creating a | |
90 | new buffer and reading the file into it. It also returns that buffer. | |
91 | ||
92 | The body of the @code{find-file} function is very simple and looks | |
93 | like this: | |
94 | ||
95 | @example | |
96 | (switch-to-buffer (find-file-noselect filename)) | |
97 | @end example | |
98 | ||
99 | @noindent | |
100 | (See @code{switch-to-buffer} in @ref{Displaying Buffers}.) | |
101 | ||
102 | When @code{find-file} is called interactively, it prompts for | |
103 | @var{filename} in the minibuffer. | |
104 | @end deffn | |
105 | ||
106 | @defun find-file-noselect filename | |
107 | This function is the guts of all the file-visiting functions. It finds | |
108 | or creates a buffer visiting the file @var{filename}, and returns it. | |
109 | It uses an existing buffer if there is one, and otherwise creates a new | |
110 | buffer and reads the file into it. You may make the buffer current or | |
111 | display it in a window if you wish, but this function does not do so. | |
112 | ||
113 | When @code{find-file-noselect} uses an existing buffer, it first | |
114 | verifies that the file has not changed since it was last visited or | |
115 | saved in that buffer. If the file has changed, then this function asks | |
116 | the user whether to reread the changed file. If the user says | |
117 | @samp{yes}, any changes previously made in the buffer are lost. | |
118 | ||
119 | If @code{find-file-noselect} needs to create a buffer, and there is no | |
120 | file named @var{filename}, it displays the message @samp{New file} in | |
121 | the echo area, and leaves the buffer empty. | |
122 | ||
123 | The @code{find-file-noselect} function calls @code{after-find-file} | |
124 | after reading the file (@pxref{Subroutines of Visiting}). That function | |
125 | sets the buffer major mode, parses local variables, warns the user if | |
126 | there exists an auto-save file more recent than the file just visited, | |
127 | and finishes by running the functions in @code{find-file-hooks}. | |
128 | ||
129 | The @code{find-file-noselect} function returns the buffer that is | |
130 | visiting the file @var{filename}. | |
131 | ||
132 | @example | |
133 | @group | |
134 | (find-file-noselect "/etc/fstab") | |
135 | @result{} #<buffer fstab> | |
136 | @end group | |
137 | @end example | |
138 | @end defun | |
139 | ||
3e01fd9d RS |
140 | @deffn Command find-file-other-window filename |
141 | This command selects a buffer visiting the file @var{filename}, but | |
142 | does so in a window other than the selected window. It may use another | |
143 | existing window or split a window; see @ref{Displaying Buffers}. | |
144 | ||
145 | When this command is called interactively, it prompts for | |
146 | @var{filename}. | |
147 | @end deffn | |
148 | ||
149 | @deffn Command find-file-read-only filename | |
150 | This command selects a buffer visiting the file @var{filename}, like | |
151 | @code{find-file}, but it marks the buffer as read-only. @xref{Read Only | |
152 | Buffers}, for related functions and variables. | |
153 | ||
154 | When this command is called interactively, it prompts for | |
155 | @var{filename}. | |
156 | @end deffn | |
157 | ||
158 | @deffn Command view-file filename | |
bfe721d1 KH |
159 | This command visits @var{filename} in View mode, and displays it in a |
160 | recursive edit, returning to the previous buffer when done. View mode | |
161 | is a mode that allows you to skim rapidly through the file but does not | |
162 | let you modify it. Entering View mode runs the normal hook | |
163 | @code{view-mode-hook}. @xref{Hooks}. | |
3e01fd9d RS |
164 | |
165 | When @code{view-file} is called interactively, it prompts for | |
166 | @var{filename}. | |
167 | @end deffn | |
168 | ||
169 | @defvar find-file-hooks | |
170 | The value of this variable is a list of functions to be called after a | |
171 | file is visited. The file's local-variables specification (if any) will | |
172 | have been processed before the hooks are run. The buffer visiting the | |
173 | file is current when the hook functions are run. | |
174 | ||
175 | This variable works just like a normal hook, but we think that renaming | |
176 | it would not be advisable. | |
177 | @end defvar | |
178 | ||
179 | @defvar find-file-not-found-hooks | |
180 | The value of this variable is a list of functions to be called when | |
181 | @code{find-file} or @code{find-file-noselect} is passed a nonexistent | |
182 | file name. @code{find-file-noselect} calls these functions as soon as | |
183 | it detects a nonexistent file. It calls them in the order of the list, | |
184 | until one of them returns non-@code{nil}. @code{buffer-file-name} is | |
185 | already set up. | |
186 | ||
187 | This is not a normal hook because the values of the functions are | |
188 | used and they may not all be called. | |
189 | @end defvar | |
190 | ||
191 | @node Subroutines of Visiting | |
192 | @comment node-name, next, previous, up | |
193 | @subsection Subroutines of Visiting | |
194 | ||
195 | The @code{find-file-noselect} function uses the | |
196 | @code{create-file-buffer} and @code{after-find-file} functions as | |
197 | subroutines. Sometimes it is useful to call them directly. | |
198 | ||
199 | @defun create-file-buffer filename | |
200 | This function creates a suitably named buffer for visiting | |
201 | @var{filename}, and returns it. It uses @var{filename} (sans directory) | |
202 | as the name if that name is free; otherwise, it appends a string such as | |
203 | @samp{<2>} to get an unused name. See also @ref{Creating Buffers}. | |
204 | ||
205 | @strong{Please note:} @code{create-file-buffer} does @emph{not} | |
206 | associate the new buffer with a file and does not select the buffer. | |
bfe721d1 | 207 | It also does not use the default major mode. |
3e01fd9d RS |
208 | |
209 | @example | |
210 | @group | |
211 | (create-file-buffer "foo") | |
212 | @result{} #<buffer foo> | |
213 | @end group | |
214 | @group | |
215 | (create-file-buffer "foo") | |
216 | @result{} #<buffer foo<2>> | |
217 | @end group | |
218 | @group | |
219 | (create-file-buffer "foo") | |
220 | @result{} #<buffer foo<3>> | |
221 | @end group | |
222 | @end example | |
223 | ||
224 | This function is used by @code{find-file-noselect}. | |
225 | It uses @code{generate-new-buffer} (@pxref{Creating Buffers}). | |
226 | @end defun | |
227 | ||
228 | @defun after-find-file &optional error warn | |
229 | This function sets the buffer major mode, and parses local variables | |
230 | (@pxref{Auto Major Mode}). It is called by @code{find-file-noselect} | |
231 | and by the default revert function (@pxref{Reverting}). | |
232 | ||
233 | @cindex new file message | |
234 | @cindex file open error | |
235 | If reading the file got an error because the file does not exist, but | |
236 | its directory does exist, the caller should pass a non-@code{nil} value | |
237 | for @var{error}. In that case, @code{after-find-file} issues a warning: | |
238 | @samp{(New File)}. For more serious errors, the caller should usually not | |
239 | call @code{after-find-file}. | |
240 | ||
241 | If @var{warn} is non-@code{nil}, then this function issues a warning | |
242 | if an auto-save file exists and is more recent than the visited file. | |
243 | ||
244 | The last thing @code{after-find-file} does is call all the functions | |
245 | in @code{find-file-hooks}. | |
246 | @end defun | |
247 | ||
248 | @node Saving Buffers | |
249 | @section Saving Buffers | |
250 | ||
251 | When you edit a file in Emacs, you are actually working on a buffer | |
252 | that is visiting that file---that is, the contents of the file are | |
253 | copied into the buffer and the copy is what you edit. Changes to the | |
254 | buffer do not change the file until you @dfn{save} the buffer, which | |
255 | means copying the contents of the buffer into the file. | |
256 | ||
257 | @deffn Command save-buffer &optional backup-option | |
258 | This function saves the contents of the current buffer in its visited | |
259 | file if the buffer has been modified since it was last visited or saved. | |
260 | Otherwise it does nothing. | |
261 | ||
262 | @code{save-buffer} is responsible for making backup files. Normally, | |
263 | @var{backup-option} is @code{nil}, and @code{save-buffer} makes a backup | |
b22f3a19 RS |
264 | file only if this is the first save since visiting the file. Other |
265 | values for @var{backup-option} request the making of backup files in | |
266 | other circumstances: | |
3e01fd9d RS |
267 | |
268 | @itemize @bullet | |
269 | @item | |
270 | With an argument of 4 or 64, reflecting 1 or 3 @kbd{C-u}'s, the | |
271 | @code{save-buffer} function marks this version of the file to be | |
272 | backed up when the buffer is next saved. | |
273 | ||
274 | @item | |
275 | With an argument of 16 or 64, reflecting 2 or 3 @kbd{C-u}'s, the | |
276 | @code{save-buffer} function unconditionally backs up the previous | |
277 | version of the file before saving it. | |
278 | @end itemize | |
279 | @end deffn | |
280 | ||
281 | @deffn Command save-some-buffers &optional save-silently-p exiting | |
282 | This command saves some modified file-visiting buffers. Normally it | |
283 | asks the user about each buffer. But if @var{save-silently-p} is | |
284 | non-@code{nil}, it saves all the file-visiting buffers without querying | |
285 | the user. | |
286 | ||
287 | The optional @var{exiting} argument, if non-@code{nil}, requests this | |
288 | function to offer also to save certain other buffers that are not | |
289 | visiting files. These are buffers that have a non-@code{nil} local | |
290 | value of @code{buffer-offer-save}. (A user who says yes to saving one | |
291 | of these is asked to specify a file name to use.) The | |
292 | @code{save-buffers-kill-emacs} function passes a non-@code{nil} value | |
293 | for this argument. | |
294 | @end deffn | |
295 | ||
296 | @defvar buffer-offer-save | |
297 | When this variable is non-@code{nil} in a buffer, Emacs offers to save | |
298 | the buffer on exit even if the buffer is not visiting a file. The | |
299 | variable is automatically local in all buffers. Normally, Mail mode | |
300 | (used for editing outgoing mail) sets this to @code{t}. | |
301 | @end defvar | |
302 | ||
303 | @deffn Command write-file filename | |
304 | This function writes the current buffer into file @var{filename}, makes | |
305 | the buffer visit that file, and marks it not modified. Then it renames | |
306 | the buffer based on @var{filename}, appending a string like @samp{<2>} | |
307 | if necessary to make a unique buffer name. It does most of this work by | |
308 | calling @code{set-visited-file-name} and @code{save-buffer}. | |
309 | @end deffn | |
310 | ||
311 | @defvar write-file-hooks | |
312 | The value of this variable is a list of functions to be called before | |
313 | writing out a buffer to its visited file. If one of them returns | |
314 | non-@code{nil}, the file is considered already written and the rest of | |
315 | the functions are not called, nor is the usual code for writing the file | |
316 | executed. | |
317 | ||
318 | If a function in @code{write-file-hooks} returns non-@code{nil}, it | |
319 | is responsible for making a backup file (if that is appropriate). | |
320 | To do so, execute the following code: | |
321 | ||
322 | @example | |
323 | (or buffer-backed-up (backup-buffer)) | |
324 | @end example | |
325 | ||
326 | You might wish to save the file modes value returned by | |
327 | @code{backup-buffer} and use that to set the mode bits of the file that | |
328 | you write. This is what @code{save-buffer} normally does. | |
329 | ||
330 | Even though this is not a normal hook, you can use @code{add-hook} and | |
331 | @code{remove-hook} to manipulate the list. @xref{Hooks}. | |
332 | @end defvar | |
333 | ||
334 | @c Emacs 19 feature | |
335 | @defvar local-write-file-hooks | |
336 | This works just like @code{write-file-hooks}, but it is intended | |
337 | to be made local to particular buffers. It's not a good idea to make | |
338 | @code{write-file-hooks} local to a buffer---use this variable instead. | |
339 | ||
340 | The variable is marked as a permanent local, so that changing the major | |
341 | mode does not alter a buffer-local value. This is convenient for | |
342 | packages that read ``file'' contents in special ways, and set up hooks | |
343 | to save the data in a corresponding way. | |
344 | @end defvar | |
345 | ||
346 | @c Emacs 19 feature | |
347 | @defvar write-contents-hooks | |
348 | This works just like @code{write-file-hooks}, but it is intended for | |
349 | hooks that pertain to the contents of the file, as opposed to hooks that | |
9d000842 | 350 | pertain to where the file came from. Such hooks are usually set up by |
633d651d RS |
351 | major modes, as buffer-local bindings for this variable. |
352 | ||
353 | This variable automatically becomes buffer-local whenever it is set; | |
354 | switching to a new major mode always resets this variable. When you use | |
355 | @code{add-hooks} to add an element to this hook, you should @emph{not} | |
356 | specify a non-@code{nil} @var{local} argument, since this variable is | |
357 | used @emph{only} locally. | |
3e01fd9d RS |
358 | @end defvar |
359 | ||
360 | @c Emacs 19 feature | |
361 | @defvar after-save-hook | |
362 | This normal hook runs after a buffer has been saved in its visited file. | |
363 | @end defvar | |
364 | ||
365 | @defvar file-precious-flag | |
366 | If this variable is non-@code{nil}, then @code{save-buffer} protects | |
367 | against I/O errors while saving by writing the new file to a temporary | |
368 | name instead of the name it is supposed to have, and then renaming it to | |
369 | the intended name after it is clear there are no errors. This procedure | |
370 | prevents problems such as a lack of disk space from resulting in an | |
371 | invalid file. | |
372 | ||
63ff95ee MW |
373 | As a side effect, backups are necessarily made by copying. @xref{Rename |
374 | or Copy}. Yet, at the same time, saving a precious file always breaks | |
375 | all hard links between the file you save and other file names. | |
3e01fd9d | 376 | |
bfe721d1 KH |
377 | Some modes set this variable non-@code{nil} locally in particular |
378 | buffers. | |
3e01fd9d RS |
379 | @end defvar |
380 | ||
381 | @defopt require-final-newline | |
382 | This variable determines whether files may be written out that do | |
383 | @emph{not} end with a newline. If the value of the variable is | |
384 | @code{t}, then @code{save-buffer} silently adds a newline at the end of | |
385 | the file whenever the buffer being saved does not already end in one. | |
386 | If the value of the variable is non-@code{nil}, but not @code{t}, then | |
387 | @code{save-buffer} asks the user whether to add a newline each time the | |
388 | case arises. | |
389 | ||
390 | If the value of the variable is @code{nil}, then @code{save-buffer} | |
391 | doesn't add newlines at all. @code{nil} is the default value, but a few | |
392 | major modes set it to @code{t} in particular buffers. | |
393 | @end defopt | |
394 | ||
395 | @node Reading from Files | |
396 | @comment node-name, next, previous, up | |
397 | @section Reading from Files | |
398 | ||
399 | You can copy a file from the disk and insert it into a buffer | |
400 | using the @code{insert-file-contents} function. Don't use the user-level | |
401 | command @code{insert-file} in a Lisp program, as that sets the mark. | |
402 | ||
403 | @defun insert-file-contents filename &optional visit beg end replace | |
404 | This function inserts the contents of file @var{filename} into the | |
63ff95ee | 405 | current buffer after point. It returns a list of the absolute file name |
3e01fd9d RS |
406 | and the length of the data inserted. An error is signaled if |
407 | @var{filename} is not the name of a file that can be read. | |
408 | ||
bfe721d1 KH |
409 | The function @code{insert-file-contents} checks the file contents |
410 | against the defined file formats, and converts the file contents if | |
411 | appropriate. @xref{Format Conversion}. It also calls the functions in | |
412 | the list @code{after-insert-file-functions}; see @ref{Saving | |
413 | Properties}. | |
3e01fd9d RS |
414 | |
415 | If @var{visit} is non-@code{nil}, this function additionally marks the | |
416 | buffer as unmodified and sets up various fields in the buffer so that it | |
417 | is visiting the file @var{filename}: these include the buffer's visited | |
418 | file name and its last save file modtime. This feature is used by | |
419 | @code{find-file-noselect} and you probably should not use it yourself. | |
420 | ||
421 | If @var{beg} and @var{end} are non-@code{nil}, they should be integers | |
422 | specifying the portion of the file to insert. In this case, @var{visit} | |
423 | must be @code{nil}. For example, | |
424 | ||
425 | @example | |
426 | (insert-file-contents filename nil 0 500) | |
427 | @end example | |
428 | ||
429 | @noindent | |
430 | inserts the first 500 characters of a file. | |
431 | ||
432 | If the argument @var{replace} is non-@code{nil}, it means to replace the | |
433 | contents of the buffer (actually, just the accessible portion) with the | |
434 | contents of the file. This is better than simply deleting the buffer | |
435 | contents and inserting the whole file, because (1) it preserves some | |
436 | marker positions and (2) it puts less data in the undo list. | |
437 | @end defun | |
438 | ||
439 | If you want to pass a file name to another process so that another | |
440 | program can read the file, use the function @code{file-local-copy}; see | |
441 | @ref{Magic File Names}. | |
442 | ||
443 | @node Writing to Files | |
444 | @comment node-name, next, previous, up | |
445 | @section Writing to Files | |
446 | ||
447 | You can write the contents of a buffer, or part of a buffer, directly | |
448 | to a file on disk using the @code{append-to-file} and | |
449 | @code{write-region} functions. Don't use these functions to write to | |
450 | files that are being visited; that could cause confusion in the | |
451 | mechanisms for visiting. | |
452 | ||
453 | @deffn Command append-to-file start end filename | |
454 | This function appends the contents of the region delimited by | |
455 | @var{start} and @var{end} in the current buffer to the end of file | |
456 | @var{filename}. If that file does not exist, it is created. This | |
457 | function returns @code{nil}. | |
458 | ||
459 | An error is signaled if @var{filename} specifies a nonwritable file, | |
460 | or a nonexistent file in a directory where files cannot be created. | |
461 | @end deffn | |
462 | ||
463 | @deffn Command write-region start end filename &optional append visit | |
464 | This function writes the region delimited by @var{start} and @var{end} | |
465 | in the current buffer into the file specified by @var{filename}. | |
466 | ||
467 | @c Emacs 19 feature | |
468 | If @var{start} is a string, then @code{write-region} writes or appends | |
469 | that string, rather than text from the buffer. | |
470 | ||
471 | If @var{append} is non-@code{nil}, then the specified text is appended | |
472 | to the existing file contents (if any). | |
473 | ||
474 | If @var{visit} is @code{t}, then Emacs establishes an association | |
475 | between the buffer and the file: the buffer is then visiting that file. | |
476 | It also sets the last file modification time for the current buffer to | |
477 | @var{filename}'s modtime, and marks the buffer as not modified. This | |
478 | feature is used by @code{save-buffer}, but you probably should not use | |
479 | it yourself. | |
480 | ||
481 | @c Emacs 19 feature | |
482 | If @var{visit} is a string, it specifies the file name to visit. This | |
483 | way, you can write the data to one file (@var{filename}) while recording | |
484 | the buffer as visiting another file (@var{visit}). The argument | |
485 | @var{visit} is used in the echo area message and also for file locking; | |
486 | @var{visit} is stored in @code{buffer-file-name}. This feature is used | |
487 | to implement @code{file-precious-flag}; don't use it yourself unless you | |
488 | really know what you're doing. | |
489 | ||
bfe721d1 KH |
490 | The function @code{write-region} converts the data which it writes to |
491 | the appropriate file formats specified by @code{buffer-file-format}. | |
492 | @xref{Format Conversion}. It also calls the functions in the list | |
493 | @code{write-region-annotate-functions}; see @ref{Saving Properties}. | |
3e01fd9d RS |
494 | |
495 | Normally, @code{write-region} displays a message @samp{Wrote file | |
496 | @var{filename}} in the echo area. If @var{visit} is neither @code{t} | |
497 | nor @code{nil} nor a string, then this message is inhibited. This | |
498 | feature is useful for programs that use files for internal purposes, | |
b22f3a19 | 499 | files that the user does not need to know about. |
3e01fd9d RS |
500 | @end deffn |
501 | ||
502 | @node File Locks | |
503 | @section File Locks | |
504 | @cindex file locks | |
505 | ||
506 | When two users edit the same file at the same time, they are likely to | |
507 | interfere with each other. Emacs tries to prevent this situation from | |
508 | arising by recording a @dfn{file lock} when a file is being modified. | |
509 | Emacs can then detect the first attempt to modify a buffer visiting a | |
510 | file that is locked by another Emacs job, and ask the user what to do. | |
511 | ||
512 | File locks do not work properly when multiple machines can share | |
513 | file systems, such as with NFS. Perhaps a better file locking system | |
514 | will be implemented in the future. When file locks do not work, it is | |
515 | possible for two users to make changes simultaneously, but Emacs can | |
516 | still warn the user who saves second. Also, the detection of | |
517 | modification of a buffer visiting a file changed on disk catches some | |
518 | cases of simultaneous editing; see @ref{Modification Time}. | |
519 | ||
520 | @defun file-locked-p filename | |
521 | This function returns @code{nil} if the file @var{filename} is not | |
522 | locked by this Emacs process. It returns @code{t} if it is locked by | |
523 | this Emacs, and it returns the name of the user who has locked it if it | |
524 | is locked by someone else. | |
525 | ||
526 | @example | |
527 | @group | |
528 | (file-locked-p "foo") | |
529 | @result{} nil | |
530 | @end group | |
531 | @end example | |
532 | @end defun | |
533 | ||
534 | @defun lock-buffer &optional filename | |
535 | This function locks the file @var{filename}, if the current buffer is | |
536 | modified. The argument @var{filename} defaults to the current buffer's | |
537 | visited file. Nothing is done if the current buffer is not visiting a | |
538 | file, or is not modified. | |
539 | @end defun | |
540 | ||
541 | @defun unlock-buffer | |
542 | This function unlocks the file being visited in the current buffer, | |
543 | if the buffer is modified. If the buffer is not modified, then | |
544 | the file should not be locked, so this function does nothing. It also | |
545 | does nothing if the current buffer is not visiting a file. | |
546 | @end defun | |
547 | ||
548 | @defun ask-user-about-lock file other-user | |
549 | This function is called when the user tries to modify @var{file}, but it | |
b22f3a19 | 550 | is locked by another user named @var{other-user}. The value it returns |
3e01fd9d RS |
551 | determines what happens next: |
552 | ||
553 | @itemize @bullet | |
554 | @item | |
555 | A value of @code{t} says to grab the lock on the file. Then | |
556 | this user may edit the file and @var{other-user} loses the lock. | |
557 | ||
558 | @item | |
559 | A value of @code{nil} says to ignore the lock and let this | |
560 | user edit the file anyway. | |
561 | ||
562 | @item | |
563 | @kindex file-locked | |
564 | This function may instead signal a @code{file-locked} error, in which | |
565 | case the change that the user was about to make does not take place. | |
566 | ||
567 | The error message for this error looks like this: | |
568 | ||
569 | @example | |
570 | @error{} File is locked: @var{file} @var{other-user} | |
571 | @end example | |
572 | ||
573 | @noindent | |
574 | where @code{file} is the name of the file and @var{other-user} is the | |
575 | name of the user who has locked the file. | |
576 | @end itemize | |
577 | ||
578 | The default definition of this function asks the user to choose what | |
579 | to do. If you wish, you can replace the @code{ask-user-about-lock} | |
580 | function with your own version that decides in another way. The code | |
581 | for its usual definition is in @file{userlock.el}. | |
582 | @end defun | |
583 | ||
584 | @node Information about Files | |
585 | @section Information about Files | |
586 | ||
b22f3a19 RS |
587 | The functions described in this section all operate on strings that |
588 | designate file names. All the functions have names that begin with the | |
589 | word @samp{file}. These functions all return information about actual | |
590 | files or directories, so their arguments must all exist as actual files | |
591 | or directories unless otherwise noted. | |
3e01fd9d RS |
592 | |
593 | @menu | |
594 | * Testing Accessibility:: Is a given file readable? Writable? | |
595 | * Kinds of Files:: Is it a directory? A symbolic link? | |
596 | * Truenames:: Eliminating symbolic links from a file name. | |
597 | * File Attributes:: How large is it? Any other names? Etc. | |
598 | @end menu | |
599 | ||
600 | @node Testing Accessibility | |
601 | @comment node-name, next, previous, up | |
602 | @subsection Testing Accessibility | |
603 | @cindex accessibility of a file | |
604 | @cindex file accessibility | |
605 | ||
606 | These functions test for permission to access a file in specific ways. | |
607 | ||
608 | @defun file-exists-p filename | |
609 | This function returns @code{t} if a file named @var{filename} appears | |
610 | to exist. This does not mean you can necessarily read the file, only | |
611 | that you can find out its attributes. (On Unix, this is true if the | |
612 | file exists and you have execute permission on the containing | |
613 | directories, regardless of the protection of the file itself.) | |
614 | ||
615 | If the file does not exist, or if fascist access control policies | |
616 | prevent you from finding the attributes of the file, this function | |
617 | returns @code{nil}. | |
618 | @end defun | |
619 | ||
620 | @defun file-readable-p filename | |
621 | This function returns @code{t} if a file named @var{filename} exists | |
622 | and you can read it. It returns @code{nil} otherwise. | |
623 | ||
624 | @example | |
625 | @group | |
626 | (file-readable-p "files.texi") | |
627 | @result{} t | |
628 | @end group | |
629 | @group | |
630 | (file-exists-p "/usr/spool/mqueue") | |
631 | @result{} t | |
632 | @end group | |
633 | @group | |
634 | (file-readable-p "/usr/spool/mqueue") | |
635 | @result{} nil | |
636 | @end group | |
637 | @end example | |
638 | @end defun | |
639 | ||
640 | @c Emacs 19 feature | |
641 | @defun file-executable-p filename | |
642 | This function returns @code{t} if a file named @var{filename} exists and | |
643 | you can execute it. It returns @code{nil} otherwise. If the file is a | |
644 | directory, execute permission means you can check the existence and | |
645 | attributes of files inside the directory, and open those files if their | |
646 | modes permit. | |
647 | @end defun | |
648 | ||
649 | @defun file-writable-p filename | |
b22f3a19 RS |
650 | This function returns @code{t} if the file @var{filename} can be written |
651 | or created by you, and @code{nil} otherwise. A file is writable if the | |
652 | file exists and you can write it. It is creatable if it does not exist, | |
653 | but the specified directory does exist and you can write in that | |
654 | directory. | |
3e01fd9d RS |
655 | |
656 | In the third example below, @file{foo} is not writable because the | |
657 | parent directory does not exist, even though the user could create such | |
658 | a directory. | |
659 | ||
660 | @example | |
661 | @group | |
662 | (file-writable-p "~/foo") | |
663 | @result{} t | |
664 | @end group | |
665 | @group | |
666 | (file-writable-p "/foo") | |
667 | @result{} nil | |
668 | @end group | |
669 | @group | |
670 | (file-writable-p "~/no-such-dir/foo") | |
671 | @result{} nil | |
672 | @end group | |
673 | @end example | |
674 | @end defun | |
675 | ||
676 | @c Emacs 19 feature | |
677 | @defun file-accessible-directory-p dirname | |
678 | This function returns @code{t} if you have permission to open existing | |
b22f3a19 RS |
679 | files in the directory whose name as a file is @var{dirname}; otherwise |
680 | (or if there is no such directory), it returns @code{nil}. The value | |
681 | of @var{dirname} may be either a directory name or the file name of a | |
682 | directory. | |
3e01fd9d RS |
683 | |
684 | Example: after the following, | |
685 | ||
686 | @example | |
687 | (file-accessible-directory-p "/foo") | |
688 | @result{} nil | |
689 | @end example | |
690 | ||
691 | @noindent | |
692 | we can deduce that any attempt to read a file in @file{/foo/} will | |
693 | give an error. | |
694 | @end defun | |
695 | ||
22697dac KH |
696 | @defun file-ownership-preserved-p filename |
697 | This function returns @code{t} if deleting the file @var{filename} and | |
698 | then creating it anew would keep the file's owner unchanged. | |
699 | @end defun | |
700 | ||
3e01fd9d RS |
701 | @defun file-newer-than-file-p filename1 filename2 |
702 | @cindex file age | |
703 | @cindex file modification time | |
b22f3a19 | 704 | This function returns @code{t} if the file @var{filename1} is |
3e01fd9d RS |
705 | newer than file @var{filename2}. If @var{filename1} does not |
706 | exist, it returns @code{nil}. If @var{filename2} does not exist, | |
707 | it returns @code{t}. | |
708 | ||
b22f3a19 RS |
709 | In the following example, assume that the file @file{aug-19} was written |
710 | on the 19th, @file{aug-20} was written on the 20th, and the file | |
711 | @file{no-file} doesn't exist at all. | |
3e01fd9d RS |
712 | |
713 | @example | |
714 | @group | |
715 | (file-newer-than-file-p "aug-19" "aug-20") | |
716 | @result{} nil | |
717 | @end group | |
718 | @group | |
719 | (file-newer-than-file-p "aug-20" "aug-19") | |
720 | @result{} t | |
721 | @end group | |
722 | @group | |
723 | (file-newer-than-file-p "aug-19" "no-file") | |
724 | @result{} t | |
725 | @end group | |
726 | @group | |
727 | (file-newer-than-file-p "no-file" "aug-19") | |
728 | @result{} nil | |
729 | @end group | |
730 | @end example | |
731 | ||
732 | You can use @code{file-attributes} to get a file's last modification | |
733 | time as a list of two numbers. @xref{File Attributes}. | |
734 | @end defun | |
735 | ||
736 | @node Kinds of Files | |
737 | @comment node-name, next, previous, up | |
738 | @subsection Distinguishing Kinds of Files | |
739 | ||
bfe721d1 KH |
740 | This section describes how to distinguish various kinds of files, such |
741 | as directories, symbolic links, and ordinary files. | |
3e01fd9d RS |
742 | |
743 | @defun file-symlink-p filename | |
744 | @cindex file symbolic links | |
745 | If the file @var{filename} is a symbolic link, the @code{file-symlink-p} | |
746 | function returns the file name to which it is linked. This may be the | |
b22f3a19 RS |
747 | name of a text file, a directory, or even another symbolic link, or it |
748 | may be a nonexistent file name. | |
3e01fd9d RS |
749 | |
750 | If the file @var{filename} is not a symbolic link (or there is no such file), | |
751 | @code{file-symlink-p} returns @code{nil}. | |
752 | ||
753 | @example | |
754 | @group | |
755 | (file-symlink-p "foo") | |
756 | @result{} nil | |
757 | @end group | |
758 | @group | |
759 | (file-symlink-p "sym-link") | |
760 | @result{} "foo" | |
761 | @end group | |
762 | @group | |
763 | (file-symlink-p "sym-link2") | |
764 | @result{} "sym-link" | |
765 | @end group | |
766 | @group | |
767 | (file-symlink-p "/bin") | |
768 | @result{} "/pub/bin" | |
769 | @end group | |
770 | @end example | |
771 | ||
772 | @c !!! file-symlink-p: should show output of ls -l for comparison | |
773 | @end defun | |
774 | ||
775 | @defun file-directory-p filename | |
776 | This function returns @code{t} if @var{filename} is the name of an | |
777 | existing directory, @code{nil} otherwise. | |
778 | ||
779 | @example | |
780 | @group | |
781 | (file-directory-p "~rms") | |
782 | @result{} t | |
783 | @end group | |
784 | @group | |
785 | (file-directory-p "~rms/lewis/files.texi") | |
786 | @result{} nil | |
787 | @end group | |
788 | @group | |
789 | (file-directory-p "~rms/lewis/no-such-file") | |
790 | @result{} nil | |
791 | @end group | |
792 | @group | |
793 | (file-directory-p "$HOME") | |
794 | @result{} nil | |
795 | @end group | |
796 | @group | |
797 | (file-directory-p | |
798 | (substitute-in-file-name "$HOME")) | |
799 | @result{} t | |
800 | @end group | |
801 | @end example | |
802 | @end defun | |
803 | ||
22697dac KH |
804 | @defun file-regular-p filename |
805 | This function returns @code{t} if the file @var{filename} exists and is | |
806 | a regular file (not a directory, symbolic link, named pipe, terminal, or | |
807 | other I/O device). | |
808 | @end defun | |
809 | ||
3e01fd9d RS |
810 | @node Truenames |
811 | @subsection Truenames | |
812 | @cindex truename (of file) | |
813 | ||
814 | @c Emacs 19 features | |
815 | The @dfn{truename} of a file is the name that you get by following | |
816 | symbolic links until none remain, then expanding to get rid of @samp{.} | |
817 | and @samp{..} as components. Strictly speaking, a file need not have a | |
818 | unique truename; the number of distinct truenames a file has is equal to | |
819 | the number of hard links to the file. However, truenames are useful | |
820 | because they eliminate symbolic links as a cause of name variation. | |
821 | ||
822 | @defun file-truename filename | |
823 | The function @code{file-truename} returns the true name of the file | |
824 | @var{filename}. This is the name that you get by following symbolic | |
825 | links until none remain. The argument must be an absolute file name. | |
826 | @end defun | |
827 | ||
828 | @xref{Buffer File Name}, for related information. | |
829 | ||
830 | @node File Attributes | |
831 | @comment node-name, next, previous, up | |
832 | @subsection Other Information about Files | |
833 | ||
834 | This section describes the functions for getting detailed information | |
835 | about a file, other than its contents. This information includes the | |
836 | mode bits that control access permission, the owner and group numbers, | |
837 | the number of names, the inode number, the size, and the times of access | |
838 | and modification. | |
839 | ||
840 | @defun file-modes filename | |
841 | @cindex permission | |
842 | @cindex file attributes | |
843 | This function returns the mode bits of @var{filename}, as an integer. | |
844 | The mode bits are also called the file permissions, and they specify | |
845 | access control in the usual Unix fashion. If the low-order bit is 1, | |
b22f3a19 | 846 | then the file is executable by all users, if the second-lowest-order bit |
3e01fd9d RS |
847 | is 1, then the file is writable by all users, etc. |
848 | ||
849 | The highest value returnable is 4095 (7777 octal), meaning that | |
850 | everyone has read, write, and execute permission, that the @sc{suid} bit | |
851 | is set for both others and group, and that the sticky bit is set. | |
852 | ||
853 | @example | |
854 | @group | |
855 | (file-modes "~/junk/diffs") | |
856 | @result{} 492 ; @r{Decimal integer.} | |
857 | @end group | |
858 | @group | |
859 | (format "%o" 492) | |
860 | @result{} "754" ; @r{Convert to octal.} | |
861 | @end group | |
862 | ||
863 | @group | |
864 | (set-file-modes "~/junk/diffs" 438) | |
865 | @result{} nil | |
866 | @end group | |
867 | ||
868 | @group | |
869 | (format "%o" 438) | |
870 | @result{} "666" ; @r{Convert to octal.} | |
871 | @end group | |
872 | ||
873 | @group | |
874 | % ls -l diffs | |
875 | -rw-rw-rw- 1 lewis 0 3063 Oct 30 16:00 diffs | |
876 | @end group | |
877 | @end example | |
878 | @end defun | |
879 | ||
880 | @defun file-nlinks filename | |
881 | This functions returns the number of names (i.e., hard links) that | |
882 | file @var{filename} has. If the file does not exist, then this function | |
883 | returns @code{nil}. Note that symbolic links have no effect on this | |
884 | function, because they are not considered to be names of the files they | |
885 | link to. | |
886 | ||
887 | @example | |
888 | @group | |
889 | % ls -l foo* | |
890 | -rw-rw-rw- 2 rms 4 Aug 19 01:27 foo | |
891 | -rw-rw-rw- 2 rms 4 Aug 19 01:27 foo1 | |
892 | @end group | |
893 | ||
894 | @group | |
895 | (file-nlinks "foo") | |
896 | @result{} 2 | |
897 | @end group | |
898 | @group | |
899 | (file-nlinks "doesnt-exist") | |
900 | @result{} nil | |
901 | @end group | |
902 | @end example | |
903 | @end defun | |
904 | ||
905 | @defun file-attributes filename | |
906 | This function returns a list of attributes of file @var{filename}. If | |
907 | the specified file cannot be opened, it returns @code{nil}. | |
908 | ||
909 | The elements of the list, in order, are: | |
910 | ||
911 | @enumerate 0 | |
912 | @item | |
913 | @code{t} for a directory, a string for a symbolic link (the name | |
914 | linked to), or @code{nil} for a text file. | |
915 | ||
916 | @c Wordy so as to prevent an overfull hbox. --rjc 15mar92 | |
917 | @item | |
918 | The number of names the file has. Alternate names, also known as hard | |
919 | links, can be created by using the @code{add-name-to-file} function | |
920 | (@pxref{Changing File Attributes}). | |
921 | ||
922 | @item | |
923 | The file's @sc{uid}. | |
924 | ||
925 | @item | |
926 | The file's @sc{gid}. | |
927 | ||
928 | @item | |
929 | The time of last access, as a list of two integers. | |
930 | The first integer has the high-order 16 bits of time, | |
931 | the second has the low 16 bits. (This is similar to the | |
932 | value of @code{current-time}; see @ref{Time of Day}.) | |
933 | ||
934 | @item | |
935 | The time of last modification as a list of two integers (as above). | |
936 | ||
937 | @item | |
938 | The time of last status change as a list of two integers (as above). | |
939 | ||
940 | @item | |
941 | The size of the file in bytes. | |
942 | ||
943 | @item | |
b22f3a19 | 944 | The file's modes, as a string of ten letters or dashes, |
3e01fd9d RS |
945 | as in @samp{ls -l}. |
946 | ||
947 | @item | |
948 | @code{t} if the file's @sc{gid} would change if file were | |
949 | deleted and recreated; @code{nil} otherwise. | |
950 | ||
951 | @item | |
952 | The file's inode number. | |
953 | ||
954 | @item | |
955 | The file system number of the file system that the file is in. This | |
b22f3a19 RS |
956 | element and the file's inode number together give enough information to |
957 | distinguish any two files on the system---no two files can have the same | |
958 | values for both of these numbers. | |
3e01fd9d RS |
959 | @end enumerate |
960 | ||
961 | For example, here are the file attributes for @file{files.texi}: | |
962 | ||
963 | @example | |
964 | @group | |
965 | (file-attributes "files.texi") | |
966 | @result{} (nil | |
967 | 1 | |
968 | 2235 | |
969 | 75 | |
970 | (8489 20284) | |
971 | (8489 20284) | |
972 | (8489 20285) | |
973 | 14906 | |
974 | "-rw-rw-rw-" | |
975 | nil | |
976 | 129500 | |
977 | -32252) | |
978 | @end group | |
979 | @end example | |
980 | ||
981 | @noindent | |
982 | and here is how the result is interpreted: | |
983 | ||
984 | @table @code | |
985 | @item nil | |
986 | is neither a directory nor a symbolic link. | |
987 | ||
988 | @item 1 | |
989 | has only one name (the name @file{files.texi} in the current default | |
990 | directory). | |
991 | ||
992 | @item 2235 | |
993 | is owned by the user with @sc{uid} 2235. | |
994 | ||
995 | @item 75 | |
996 | is in the group with @sc{gid} 75. | |
997 | ||
998 | @item (8489 20284) | |
6784ada3 | 999 | was last accessed on Aug 19 00:09. |
3e01fd9d RS |
1000 | |
1001 | @item (8489 20284) | |
1002 | was last modified on Aug 19 00:09. | |
1003 | ||
1004 | @item (8489 20285) | |
1005 | last had its inode changed on Aug 19 00:09. | |
1006 | ||
1007 | @item 14906 | |
1008 | is 14906 characters long. | |
1009 | ||
1010 | @item "-rw-rw-rw-" | |
1011 | has a mode of read and write access for the owner, group, and world. | |
1012 | ||
1013 | @item nil | |
1014 | would retain the same @sc{gid} if it were recreated. | |
1015 | ||
1016 | @item 129500 | |
1017 | has an inode number of 129500. | |
1018 | @item -32252 | |
1019 | is on file system number -32252. | |
1020 | @end table | |
1021 | @end defun | |
1022 | ||
1023 | @node Changing File Attributes | |
1024 | @section Changing File Names and Attributes | |
1025 | @cindex renaming files | |
1026 | @cindex copying files | |
1027 | @cindex deleting files | |
1028 | @cindex linking files | |
1029 | @cindex setting modes of files | |
1030 | ||
1031 | The functions in this section rename, copy, delete, link, and set the | |
1032 | modes of files. | |
1033 | ||
1034 | In the functions that have an argument @var{newname}, if a file by the | |
1035 | name of @var{newname} already exists, the actions taken depend on the | |
1036 | value of the argument @var{ok-if-already-exists}: | |
1037 | ||
1038 | @itemize @bullet | |
1039 | @item | |
1040 | Signal a @code{file-already-exists} error if | |
1041 | @var{ok-if-already-exists} is @code{nil}. | |
1042 | ||
1043 | @item | |
1044 | Request confirmation if @var{ok-if-already-exists} is a number. | |
1045 | ||
1046 | @item | |
1047 | Replace the old file without confirmation if @var{ok-if-already-exists} | |
1048 | is any other value. | |
1049 | @end itemize | |
1050 | ||
1051 | @defun add-name-to-file oldname newname &optional ok-if-already-exists | |
1052 | @cindex file with multiple names | |
1053 | @cindex file hard link | |
1054 | This function gives the file named @var{oldname} the additional name | |
1055 | @var{newname}. This means that @var{newname} becomes a new ``hard | |
1056 | link'' to @var{oldname}. | |
1057 | ||
1058 | In the first part of the following example, we list two files, | |
1059 | @file{foo} and @file{foo3}. | |
1060 | ||
1061 | @example | |
1062 | @group | |
1063 | % ls -l fo* | |
1064 | -rw-rw-rw- 1 rms 29 Aug 18 20:32 foo | |
1065 | -rw-rw-rw- 1 rms 24 Aug 18 20:31 foo3 | |
1066 | @end group | |
1067 | @end example | |
1068 | ||
1069 | Then we evaluate the form @code{(add-name-to-file "~/lewis/foo" | |
1070 | "~/lewis/foo2")}. Again we list the files. This shows two names, | |
1071 | @file{foo} and @file{foo2}. | |
1072 | ||
1073 | @example | |
1074 | @group | |
1075 | (add-name-to-file "~/lewis/foo1" "~/lewis/foo2") | |
1076 | @result{} nil | |
1077 | @end group | |
1078 | ||
1079 | @group | |
1080 | % ls -l fo* | |
1081 | -rw-rw-rw- 2 rms 29 Aug 18 20:32 foo | |
1082 | -rw-rw-rw- 2 rms 29 Aug 18 20:32 foo2 | |
1083 | -rw-rw-rw- 1 rms 24 Aug 18 20:31 foo3 | |
1084 | @end group | |
1085 | @end example | |
1086 | ||
1087 | @c !!! Check whether this set of examples is consistent. --rjc 15mar92 | |
1088 | Finally, we evaluate the following: | |
1089 | ||
1090 | @example | |
1091 | (add-name-to-file "~/lewis/foo" "~/lewis/foo3" t) | |
1092 | @end example | |
1093 | ||
1094 | @noindent | |
1095 | and list the files again. Now there are three names | |
1096 | for one file: @file{foo}, @file{foo2}, and @file{foo3}. The old | |
1097 | contents of @file{foo3} are lost. | |
1098 | ||
1099 | @example | |
1100 | @group | |
1101 | (add-name-to-file "~/lewis/foo1" "~/lewis/foo3") | |
1102 | @result{} nil | |
1103 | @end group | |
1104 | ||
1105 | @group | |
1106 | % ls -l fo* | |
1107 | -rw-rw-rw- 3 rms 29 Aug 18 20:32 foo | |
1108 | -rw-rw-rw- 3 rms 29 Aug 18 20:32 foo2 | |
1109 | -rw-rw-rw- 3 rms 29 Aug 18 20:32 foo3 | |
1110 | @end group | |
1111 | @end example | |
1112 | ||
1113 | This function is meaningless on VMS, where multiple names for one file | |
1114 | are not allowed. | |
1115 | ||
1116 | See also @code{file-nlinks} in @ref{File Attributes}. | |
1117 | @end defun | |
1118 | ||
1119 | @deffn Command rename-file filename newname &optional ok-if-already-exists | |
1120 | This command renames the file @var{filename} as @var{newname}. | |
1121 | ||
1122 | If @var{filename} has additional names aside from @var{filename}, it | |
1123 | continues to have those names. In fact, adding the name @var{newname} | |
1124 | with @code{add-name-to-file} and then deleting @var{filename} has the | |
1125 | same effect as renaming, aside from momentary intermediate states. | |
1126 | ||
1127 | In an interactive call, this function prompts for @var{filename} and | |
1128 | @var{newname} in the minibuffer; also, it requests confirmation if | |
1129 | @var{newname} already exists. | |
1130 | @end deffn | |
1131 | ||
1132 | @deffn Command copy-file oldname newname &optional ok-if-exists time | |
1133 | This command copies the file @var{oldname} to @var{newname}. An | |
1134 | error is signaled if @var{oldname} does not exist. | |
1135 | ||
1136 | If @var{time} is non-@code{nil}, then this functions gives the new | |
1137 | file the same last-modified time that the old one has. (This works on | |
1138 | only some operating systems.) | |
1139 | ||
1140 | In an interactive call, this function prompts for @var{filename} and | |
1141 | @var{newname} in the minibuffer; also, it requests confirmation if | |
1142 | @var{newname} already exists. | |
1143 | @end deffn | |
1144 | ||
1145 | @deffn Command delete-file filename | |
1146 | @pindex rm | |
1147 | This command deletes the file @var{filename}, like the shell command | |
1148 | @samp{rm @var{filename}}. If the file has multiple names, it continues | |
1149 | to exist under the other names. | |
1150 | ||
1151 | A suitable kind of @code{file-error} error is signaled if the file | |
1152 | does not exist, or is not deletable. (On Unix, a file is deletable if | |
1153 | its directory is writable.) | |
1154 | ||
1155 | See also @code{delete-directory} in @ref{Create/Delete Dirs}. | |
1156 | @end deffn | |
1157 | ||
1158 | @deffn Command make-symbolic-link filename newname &optional ok-if-exists | |
1159 | @pindex ln | |
1160 | @kindex file-already-exists | |
1161 | This command makes a symbolic link to @var{filename}, named | |
1162 | @var{newname}. This is like the shell command @samp{ln -s | |
1163 | @var{filename} @var{newname}}. | |
1164 | ||
b22f3a19 RS |
1165 | In an interactive call, this function prompts for @var{filename} and |
1166 | @var{newname} in the minibuffer; also, it requests confirmation if | |
1167 | @var{newname} already exists. | |
3e01fd9d RS |
1168 | @end deffn |
1169 | ||
1170 | @defun define-logical-name varname string | |
1171 | This function defines the logical name @var{name} to have the value | |
1172 | @var{string}. It is available only on VMS. | |
1173 | @end defun | |
1174 | ||
1175 | @defun set-file-modes filename mode | |
1176 | This function sets mode bits of @var{filename} to @var{mode} (which must | |
b22f3a19 | 1177 | be an integer). Only the low 12 bits of @var{mode} are used. |
3e01fd9d RS |
1178 | @end defun |
1179 | ||
1180 | @c Emacs 19 feature | |
1181 | @defun set-default-file-modes mode | |
1182 | This function sets the default file protection for new files created by | |
1183 | Emacs and its subprocesses. Every file created with Emacs initially has | |
1184 | this protection. On Unix, the default protection is the bitwise | |
1185 | complement of the ``umask'' value. | |
1186 | ||
b22f3a19 | 1187 | The argument @var{mode} must be an integer. Only the low 9 bits of |
3e01fd9d RS |
1188 | @var{mode} are used. |
1189 | ||
1190 | Saving a modified version of an existing file does not count as creating | |
1191 | the file; it does not change the file's mode, and does not use the | |
1192 | default file protection. | |
1193 | @end defun | |
1194 | ||
1195 | @defun default-file-modes | |
1196 | This function returns the current default protection value. | |
1197 | @end defun | |
1198 | ||
841e483d RS |
1199 | @cindex MS-DOS and file modes |
1200 | @cindex file modes and MS-DOS | |
1201 | On MS-DOS, there is no such thing as an ``executable'' file mode bit. | |
1202 | So Emacs considers a file executable if its name ends in @samp{.com}, | |
1203 | @samp{.bat} or @samp{.exe}. This is reflected in the values returned | |
1204 | by @code{file-modes} and @code{file-attributes}. | |
1205 | ||
3e01fd9d RS |
1206 | @node File Names |
1207 | @section File Names | |
1208 | @cindex file names | |
1209 | ||
1210 | Files are generally referred to by their names, in Emacs as elsewhere. | |
1211 | File names in Emacs are represented as strings. The functions that | |
1212 | operate on a file all expect a file name argument. | |
1213 | ||
1214 | In addition to operating on files themselves, Emacs Lisp programs | |
1215 | often need to operate on the names; i.e., to take them apart and to use | |
1216 | part of a name to construct related file names. This section describes | |
1217 | how to manipulate file names. | |
1218 | ||
1219 | The functions in this section do not actually access files, so they | |
1220 | can operate on file names that do not refer to an existing file or | |
1221 | directory. | |
1222 | ||
b22f3a19 | 1223 | On VMS, all these functions understand both VMS file-name syntax and |
3e01fd9d RS |
1224 | Unix syntax. This is so that all the standard Lisp libraries can |
1225 | specify file names in Unix syntax and work properly on VMS without | |
b22f3a19 | 1226 | change. On MS-DOS, these functions understand MS-DOS file-name syntax |
841e483d | 1227 | as well as Unix syntax. |
3e01fd9d RS |
1228 | |
1229 | @menu | |
1230 | * File Name Components:: The directory part of a file name, and the rest. | |
1231 | * Directory Names:: A directory's name as a directory | |
1232 | is different from its name as a file. | |
1233 | * Relative File Names:: Some file names are relative to a current directory. | |
1234 | * File Name Expansion:: Converting relative file names to absolute ones. | |
1235 | * Unique File Names:: Generating names for temporary files. | |
1236 | * File Name Completion:: Finding the completions for a given file name. | |
1237 | @end menu | |
1238 | ||
1239 | @node File Name Components | |
1240 | @subsection File Name Components | |
1241 | @cindex directory part (of file name) | |
1242 | @cindex nondirectory part (of file name) | |
1243 | @cindex version number (in file name) | |
1244 | ||
1245 | The operating system groups files into directories. To specify a | |
b22f3a19 RS |
1246 | file, you must specify the directory and the file's name within that |
1247 | directory. Therefore, Emacs considers a file name as having two main | |
1248 | parts: the @dfn{directory name} part, and the @dfn{nondirectory} part | |
1249 | (or @dfn{file name within the directory}). Either part may be empty. | |
1250 | Concatenating these two parts reproduces the original file name. | |
3e01fd9d RS |
1251 | |
1252 | On Unix, the directory part is everything up to and including the last | |
1253 | slash; the nondirectory part is the rest. The rules in VMS syntax are | |
1254 | complicated. | |
1255 | ||
1256 | For some purposes, the nondirectory part is further subdivided into | |
1257 | the name proper and the @dfn{version number}. On Unix, only backup | |
1258 | files have version numbers in their names; on VMS, every file has a | |
1259 | version number, but most of the time the file name actually used in | |
1260 | Emacs omits the version number. Version numbers are found mostly in | |
1261 | directory lists. | |
1262 | ||
1263 | @defun file-name-directory filename | |
1264 | This function returns the directory part of @var{filename} (or | |
1265 | @code{nil} if @var{filename} does not include a directory part). On | |
1266 | Unix, the function returns a string ending in a slash. On VMS, it | |
1267 | returns a string ending in one of the three characters @samp{:}, | |
1268 | @samp{]}, or @samp{>}. | |
1269 | ||
1270 | @example | |
1271 | @group | |
1272 | (file-name-directory "lewis/foo") ; @r{Unix example} | |
1273 | @result{} "lewis/" | |
1274 | @end group | |
1275 | @group | |
1276 | (file-name-directory "foo") ; @r{Unix example} | |
1277 | @result{} nil | |
1278 | @end group | |
1279 | @group | |
1280 | (file-name-directory "[X]FOO.TMP") ; @r{VMS example} | |
1281 | @result{} "[X]" | |
1282 | @end group | |
1283 | @end example | |
1284 | @end defun | |
1285 | ||
1286 | @defun file-name-nondirectory filename | |
1287 | This function returns the nondirectory part of @var{filename}. | |
1288 | ||
1289 | @example | |
1290 | @group | |
1291 | (file-name-nondirectory "lewis/foo") | |
1292 | @result{} "foo" | |
1293 | @end group | |
1294 | @group | |
1295 | (file-name-nondirectory "foo") | |
1296 | @result{} "foo" | |
1297 | @end group | |
1298 | @group | |
1299 | ;; @r{The following example is accurate only on VMS.} | |
1300 | (file-name-nondirectory "[X]FOO.TMP") | |
1301 | @result{} "FOO.TMP" | |
1302 | @end group | |
1303 | @end example | |
1304 | @end defun | |
1305 | ||
1306 | @defun file-name-sans-versions filename | |
1307 | This function returns @var{filename} without any file version numbers, | |
1308 | backup version numbers, or trailing tildes. | |
1309 | ||
1310 | @example | |
1311 | @group | |
1312 | (file-name-sans-versions "~rms/foo.~1~") | |
1313 | @result{} "~rms/foo" | |
1314 | @end group | |
1315 | @group | |
1316 | (file-name-sans-versions "~rms/foo~") | |
1317 | @result{} "~rms/foo" | |
1318 | @end group | |
1319 | @group | |
1320 | (file-name-sans-versions "~rms/foo") | |
1321 | @result{} "~rms/foo" | |
1322 | @end group | |
1323 | @group | |
1324 | ;; @r{The following example applies to VMS only.} | |
1325 | (file-name-sans-versions "foo;23") | |
1326 | @result{} "foo" | |
1327 | @end group | |
1328 | @end example | |
1329 | @end defun | |
1330 | ||
22697dac | 1331 | @defun file-name-sans-extension filename |
bfe721d1 KH |
1332 | This function returns @var{filename} minus its ``extension,'' if any. |
1333 | The extension, in a file name, is the part that starts with the last | |
1334 | @samp{.} in the last name component. For example, | |
1335 | ||
1336 | @example | |
1337 | (file-name-sans-extension "foo.lose.c") | |
1338 | @result{} "foo.lose" | |
1339 | (file-name-sans-extension "big.hack/foo") | |
1340 | @result{} "big.hack/foo" | |
1341 | @end example | |
22697dac KH |
1342 | @end defun |
1343 | ||
3e01fd9d RS |
1344 | @node Directory Names |
1345 | @comment node-name, next, previous, up | |
1346 | @subsection Directory Names | |
1347 | @cindex directory name | |
1348 | @cindex file name of directory | |
1349 | ||
1350 | A @dfn{directory name} is the name of a directory. A directory is a | |
1351 | kind of file, and it has a file name, which is related to the directory | |
1352 | name but not identical to it. (This is not quite the same as the usual | |
1353 | Unix terminology.) These two different names for the same entity are | |
1354 | related by a syntactic transformation. On Unix, this is simple: a | |
1355 | directory name ends in a slash, whereas the directory's name as a file | |
1356 | lacks that slash. On VMS, the relationship is more complicated. | |
1357 | ||
1358 | The difference between a directory name and its name as a file is | |
1359 | subtle but crucial. When an Emacs variable or function argument is | |
1360 | described as being a directory name, a file name of a directory is not | |
1361 | acceptable. | |
1362 | ||
b22f3a19 RS |
1363 | The following two functions convert between directory names and file |
1364 | names. They do nothing special with environment variable substitutions | |
1365 | such as @samp{$HOME}, and the constructs @samp{~}, and @samp{..}. | |
3e01fd9d RS |
1366 | |
1367 | @defun file-name-as-directory filename | |
1368 | This function returns a string representing @var{filename} in a form | |
1369 | that the operating system will interpret as the name of a directory. In | |
1370 | Unix, this means appending a slash to the string. On VMS, the function | |
1371 | converts a string of the form @file{[X]Y.DIR.1} to the form | |
1372 | @file{[X.Y]}. | |
1373 | ||
1374 | @example | |
1375 | @group | |
1376 | (file-name-as-directory "~rms/lewis") | |
1377 | @result{} "~rms/lewis/" | |
1378 | @end group | |
1379 | @end example | |
1380 | @end defun | |
1381 | ||
1382 | @defun directory-file-name dirname | |
1383 | This function returns a string representing @var{dirname} in a form | |
1384 | that the operating system will interpret as the name of a file. On | |
1385 | Unix, this means removing a final slash from the string. On VMS, the | |
1386 | function converts a string of the form @file{[X.Y]} to | |
1387 | @file{[X]Y.DIR.1}. | |
1388 | ||
1389 | @example | |
1390 | @group | |
1391 | (directory-file-name "~lewis/") | |
1392 | @result{} "~lewis" | |
1393 | @end group | |
1394 | @end example | |
1395 | @end defun | |
1396 | ||
1397 | @cindex directory name abbreviation | |
1398 | Directory name abbreviations are useful for directories that are | |
1399 | normally accessed through symbolic links. Sometimes the users recognize | |
1400 | primarily the link's name as ``the name'' of the directory, and find it | |
1401 | annoying to see the directory's ``real'' name. If you define the link | |
1402 | name as an abbreviation for the ``real'' name, Emacs shows users the | |
1403 | abbreviation instead. | |
1404 | ||
1405 | @defvar directory-abbrev-alist | |
1406 | The variable @code{directory-abbrev-alist} contains an alist of | |
1407 | abbreviations to use for file directories. Each element has the form | |
1408 | @code{(@var{from} . @var{to})}, and says to replace @var{from} with | |
1409 | @var{to} when it appears in a directory name. The @var{from} string is | |
1410 | actually a regular expression; it should always start with @samp{^}. | |
1411 | The function @code{abbreviate-file-name} performs these substitutions. | |
1412 | ||
1413 | You can set this variable in @file{site-init.el} to describe the | |
1414 | abbreviations appropriate for your site. | |
1415 | ||
1416 | Here's an example, from a system on which file system @file{/home/fsf} | |
1417 | and so on are normally accessed through symbolic links named @file{/fsf} | |
1418 | and so on. | |
1419 | ||
1420 | @example | |
1421 | (("^/home/fsf" . "/fsf") | |
1422 | ("^/home/gp" . "/gp") | |
1423 | ("^/home/gd" . "/gd")) | |
1424 | @end example | |
1425 | @end defvar | |
1426 | ||
1427 | To convert a directory name to its abbreviation, use this | |
1428 | function: | |
1429 | ||
1430 | @defun abbreviate-file-name dirname | |
1431 | This function applies abbreviations from @code{directory-abbrev-alist} | |
1432 | to its argument, and substitutes @samp{~} for the user's home | |
1433 | directory. | |
1434 | @end defun | |
1435 | ||
1436 | @node Relative File Names | |
1437 | @subsection Absolute and Relative File Names | |
1438 | @cindex absolute file name | |
1439 | @cindex relative file name | |
1440 | ||
1441 | All the directories in the file system form a tree starting at the | |
1442 | root directory. A file name can specify all the directory names | |
1443 | starting from the root of the tree; then it is called an @dfn{absolute} | |
1444 | file name. Or it can specify the position of the file in the tree | |
1445 | relative to a default directory; then it is called a @dfn{relative} | |
1446 | file name. On Unix, an absolute file name starts with a slash or a | |
1447 | tilde (@samp{~}), and a relative one does not. The rules on VMS are | |
1448 | complicated. | |
1449 | ||
1450 | @defun file-name-absolute-p filename | |
1451 | This function returns @code{t} if file @var{filename} is an absolute | |
1452 | file name, @code{nil} otherwise. On VMS, this function understands both | |
1453 | Unix syntax and VMS syntax. | |
1454 | ||
1455 | @example | |
1456 | @group | |
1457 | (file-name-absolute-p "~rms/foo") | |
1458 | @result{} t | |
1459 | @end group | |
1460 | @group | |
1461 | (file-name-absolute-p "rms/foo") | |
1462 | @result{} nil | |
1463 | @end group | |
1464 | @group | |
1465 | (file-name-absolute-p "/user/rms/foo") | |
1466 | @result{} t | |
1467 | @end group | |
1468 | @end example | |
1469 | @end defun | |
1470 | ||
1471 | @node File Name Expansion | |
1472 | @subsection Functions that Expand Filenames | |
1473 | @cindex expansion of file names | |
1474 | ||
1475 | @dfn{Expansion} of a file name means converting a relative file name | |
1476 | to an absolute one. Since this is done relative to a default directory, | |
1477 | you must specify the default directory name as well as the file name to | |
1478 | be expanded. Expansion also simplifies file names by eliminating | |
1479 | redundancies such as @file{./} and @file{@var{name}/../}. | |
1480 | ||
1481 | @defun expand-file-name filename &optional directory | |
1482 | This function converts @var{filename} to an absolute file name. If | |
1483 | @var{directory} is supplied, it is the directory to start with if | |
1484 | @var{filename} is relative. (The value of @var{directory} should itself | |
1485 | be an absolute directory name; it may start with @samp{~}.) | |
1486 | Otherwise, the current buffer's value of @code{default-directory} is | |
1487 | used. For example: | |
1488 | ||
1489 | @example | |
1490 | @group | |
1491 | (expand-file-name "foo") | |
1492 | @result{} "/xcssun/users/rms/lewis/foo" | |
1493 | @end group | |
1494 | @group | |
1495 | (expand-file-name "../foo") | |
1496 | @result{} "/xcssun/users/rms/foo" | |
1497 | @end group | |
1498 | @group | |
1499 | (expand-file-name "foo" "/usr/spool/") | |
1500 | @result{} "/usr/spool/foo" | |
1501 | @end group | |
1502 | @group | |
1503 | (expand-file-name "$HOME/foo") | |
1504 | @result{} "/xcssun/users/rms/lewis/$HOME/foo" | |
1505 | @end group | |
1506 | @end example | |
1507 | ||
1508 | Filenames containing @samp{.} or @samp{..} are simplified to their | |
1509 | canonical form: | |
1510 | ||
1511 | @example | |
1512 | @group | |
1513 | (expand-file-name "bar/../foo") | |
1514 | @result{} "/xcssun/users/rms/lewis/foo" | |
1515 | @end group | |
1516 | @end example | |
1517 | ||
1518 | @samp{~/} is expanded into the user's home directory. A @samp{/} or | |
1519 | @samp{~} following a @samp{/} is taken to be the start of an absolute | |
1520 | file name that overrides what precedes it, so everything before that | |
1521 | @samp{/} or @samp{~} is deleted. For example: | |
1522 | ||
1523 | @example | |
1524 | @group | |
1525 | (expand-file-name | |
1526 | "/a1/gnu//usr/local/lib/emacs/etc/MACHINES") | |
1527 | @result{} "/usr/local/lib/emacs/etc/MACHINES" | |
1528 | @end group | |
1529 | @group | |
1530 | (expand-file-name "/a1/gnu/~/foo") | |
1531 | @result{} "/xcssun/users/rms/foo" | |
1532 | @end group | |
1533 | @end example | |
1534 | ||
1535 | @noindent | |
1536 | In both cases, @file{/a1/gnu/} is discarded because an absolute file | |
1537 | name follows it. | |
1538 | ||
1539 | Note that @code{expand-file-name} does @emph{not} expand environment | |
1540 | variables; only @code{substitute-in-file-name} does that. | |
1541 | @end defun | |
1542 | ||
1543 | @c Emacs 19 feature | |
1544 | @defun file-relative-name filename directory | |
1545 | This function does the inverse of expansion---it tries to return a | |
b22f3a19 | 1546 | relative name that is equivalent to @var{filename} when interpreted |
3e01fd9d RS |
1547 | relative to @var{directory}. (If such a relative name would be longer |
1548 | than the absolute name, it returns the absolute name instead.) | |
1549 | ||
1550 | @example | |
1551 | (file-relative-name "/foo/bar" "/foo/") | |
1552 | @result{} "bar") | |
1553 | (file-relative-name "/foo/bar" "/hack/") | |
1554 | @result{} "/foo/bar") | |
1555 | @end example | |
1556 | @end defun | |
1557 | ||
1558 | @defvar default-directory | |
1559 | The value of this buffer-local variable is the default directory for the | |
1560 | current buffer. It should be an absolute directory name; it may start | |
1561 | with @samp{~}. This variable is local in every buffer. | |
1562 | ||
1563 | @code{expand-file-name} uses the default directory when its second | |
1564 | argument is @code{nil}. | |
1565 | ||
1566 | On Unix systems, the value is always a string ending with a slash. | |
1567 | ||
1568 | @example | |
1569 | @group | |
1570 | default-directory | |
1571 | @result{} "/user/lewis/manual/" | |
1572 | @end group | |
1573 | @end example | |
1574 | @end defvar | |
1575 | ||
1576 | @defun substitute-in-file-name filename | |
1577 | This function replaces environment variables references in | |
1578 | @var{filename} with the environment variable values. Following standard | |
1579 | Unix shell syntax, @samp{$} is the prefix to substitute an environment | |
1580 | variable value. | |
1581 | ||
1582 | The environment variable name is the series of alphanumeric characters | |
1583 | (including underscores) that follow the @samp{$}. If the character following | |
1584 | the @samp{$} is a @samp{@{}, then the variable name is everything up to the | |
1585 | matching @samp{@}}. | |
1586 | ||
1587 | @c Wordy to avoid overfull hbox. --rjc 15mar92 | |
1588 | Here we assume that the environment variable @code{HOME}, which holds | |
1589 | the user's home directory name, has value @samp{/xcssun/users/rms}. | |
1590 | ||
1591 | @example | |
1592 | @group | |
1593 | (substitute-in-file-name "$HOME/foo") | |
1594 | @result{} "/xcssun/users/rms/foo" | |
1595 | @end group | |
1596 | @end example | |
1597 | ||
1598 | If a @samp{~} or a @samp{/} appears following a @samp{/}, after | |
1599 | substitution, everything before the following @samp{/} is discarded: | |
1600 | ||
1601 | @example | |
1602 | @group | |
1603 | (substitute-in-file-name "bar/~/foo") | |
1604 | @result{} "~/foo" | |
1605 | @end group | |
1606 | @group | |
1607 | (substitute-in-file-name "/usr/local/$HOME/foo") | |
1608 | @result{} "/xcssun/users/rms/foo" | |
1609 | @end group | |
1610 | @end example | |
1611 | ||
1612 | On VMS, @samp{$} substitution is not done, so this function does nothing | |
1613 | on VMS except discard superfluous initial components as shown above. | |
1614 | @end defun | |
1615 | ||
1616 | @node Unique File Names | |
1617 | @subsection Generating Unique File Names | |
1618 | ||
1619 | Some programs need to write temporary files. Here is the usual way to | |
1620 | construct a name for such a file: | |
1621 | ||
1622 | @example | |
1623 | (make-temp-name (concat "/tmp/" @var{name-of-application})) | |
1624 | @end example | |
1625 | ||
1626 | @noindent | |
1627 | Here we use the directory @file{/tmp/} because that is the standard | |
1628 | place on Unix for temporary files. The job of @code{make-temp-name} is | |
1629 | to prevent two different users or two different jobs from trying to use | |
1630 | the same name. | |
1631 | ||
1632 | @defun make-temp-name string | |
1633 | This function generates string that can be used as a unique name. The | |
b22f3a19 RS |
1634 | name starts with @var{string}, and ends with a number that is different |
1635 | in each Emacs job. | |
3e01fd9d RS |
1636 | |
1637 | @example | |
1638 | @group | |
1639 | (make-temp-name "/tmp/foo") | |
1640 | @result{} "/tmp/foo021304" | |
1641 | @end group | |
1642 | @end example | |
1643 | ||
1644 | To prevent conflicts among different libraries running in the same | |
1645 | Emacs, each Lisp program that uses @code{make-temp-name} should have its | |
1646 | own @var{string}. The number added to the end of the name distinguishes | |
1647 | between the same application running in different Emacs jobs. | |
1648 | @end defun | |
1649 | ||
1650 | @node File Name Completion | |
1651 | @subsection File Name Completion | |
1652 | @cindex file name completion subroutines | |
1653 | @cindex completion, file name | |
1654 | ||
1655 | This section describes low-level subroutines for completing a file | |
1656 | name. For other completion functions, see @ref{Completion}. | |
1657 | ||
1658 | @defun file-name-all-completions partial-filename directory | |
1659 | This function returns a list of all possible completions for a file | |
1660 | whose name starts with @var{partial-filename} in directory | |
1661 | @var{directory}. The order of the completions is the order of the files | |
1662 | in the directory, which is unpredictable and conveys no useful | |
1663 | information. | |
1664 | ||
1665 | The argument @var{partial-filename} must be a file name containing no | |
1666 | directory part and no slash. The current buffer's default directory is | |
1667 | prepended to @var{directory}, if @var{directory} is not absolute. | |
1668 | ||
1669 | In the following example, suppose that the current default directory, | |
1670 | @file{~rms/lewis}, has five files whose names begin with @samp{f}: | |
1671 | @file{foo}, @file{file~}, @file{file.c}, @file{file.c.~1~}, and | |
1672 | @file{file.c.~2~}.@refill | |
1673 | ||
1674 | @example | |
1675 | @group | |
1676 | (file-name-all-completions "f" "") | |
1677 | @result{} ("foo" "file~" "file.c.~2~" | |
1678 | "file.c.~1~" "file.c") | |
1679 | @end group | |
1680 | ||
1681 | @group | |
1682 | (file-name-all-completions "fo" "") | |
1683 | @result{} ("foo") | |
1684 | @end group | |
1685 | @end example | |
1686 | @end defun | |
1687 | ||
1688 | @defun file-name-completion filename directory | |
1689 | This function completes the file name @var{filename} in directory | |
1690 | @var{directory}. It returns the longest prefix common to all file names | |
1691 | in directory @var{directory} that start with @var{filename}. | |
1692 | ||
1693 | If only one match exists and @var{filename} matches it exactly, the | |
1694 | function returns @code{t}. The function returns @code{nil} if directory | |
1695 | @var{directory} contains no name starting with @var{filename}. | |
1696 | ||
1697 | In the following example, suppose that the current default directory | |
1698 | has five files whose names begin with @samp{f}: @file{foo}, | |
1699 | @file{file~}, @file{file.c}, @file{file.c.~1~}, and | |
1700 | @file{file.c.~2~}.@refill | |
1701 | ||
1702 | @example | |
1703 | @group | |
1704 | (file-name-completion "fi" "") | |
1705 | @result{} "file" | |
1706 | @end group | |
1707 | ||
1708 | @group | |
1709 | (file-name-completion "file.c.~1" "") | |
1710 | @result{} "file.c.~1~" | |
1711 | @end group | |
1712 | ||
1713 | @group | |
1714 | (file-name-completion "file.c.~1~" "") | |
1715 | @result{} t | |
1716 | @end group | |
1717 | ||
1718 | @group | |
1719 | (file-name-completion "file.c.~3" "") | |
1720 | @result{} nil | |
1721 | @end group | |
1722 | @end example | |
1723 | @end defun | |
1724 | ||
1725 | @defopt completion-ignored-extensions | |
1726 | @code{file-name-completion} usually ignores file names that end in any | |
1727 | string in this list. It does not ignore them when all the possible | |
1728 | completions end in one of these suffixes or when a buffer showing all | |
1729 | possible completions is displayed.@refill | |
1730 | ||
1731 | A typical value might look like this: | |
1732 | ||
1733 | @example | |
1734 | @group | |
1735 | completion-ignored-extensions | |
1736 | @result{} (".o" ".elc" "~" ".dvi") | |
1737 | @end group | |
1738 | @end example | |
1739 | @end defopt | |
1740 | ||
1741 | @node Contents of Directories | |
1742 | @section Contents of Directories | |
1743 | @cindex directory-oriented functions | |
1744 | @cindex file names in directory | |
1745 | ||
1746 | A directory is a kind of file that contains other files entered under | |
1747 | various names. Directories are a feature of the file system. | |
1748 | ||
1749 | Emacs can list the names of the files in a directory as a Lisp list, | |
1750 | or display the names in a buffer using the @code{ls} shell command. In | |
1751 | the latter case, it can optionally display information about each file, | |
1752 | depending on the options passed to the @code{ls} command. | |
1753 | ||
1754 | @defun directory-files directory &optional full-name match-regexp nosort | |
1755 | This function returns a list of the names of the files in the directory | |
1756 | @var{directory}. By default, the list is in alphabetical order. | |
1757 | ||
1758 | If @var{full-name} is non-@code{nil}, the function returns the files' | |
1759 | absolute file names. Otherwise, it returns the names relative to | |
1760 | the specified directory. | |
1761 | ||
1762 | If @var{match-regexp} is non-@code{nil}, this function returns only | |
1763 | those file names that contain a match for that regular expression---the | |
1764 | other file names are excluded from the list. | |
1765 | ||
1766 | @c Emacs 19 feature | |
1767 | If @var{nosort} is non-@code{nil}, @code{directory-files} does not sort | |
1768 | the list, so you get the file names in no particular order. Use this if | |
1769 | you want the utmost possible speed and don't care what order the files | |
1770 | are processed in. If the order of processing is visible to the user, | |
1771 | then the user will probably be happier if you do sort the names. | |
1772 | ||
1773 | @example | |
1774 | @group | |
1775 | (directory-files "~lewis") | |
1776 | @result{} ("#foo#" "#foo.el#" "." ".." | |
1777 | "dired-mods.el" "files.texi" | |
1778 | "files.texi.~1~") | |
1779 | @end group | |
1780 | @end example | |
1781 | ||
1782 | An error is signaled if @var{directory} is not the name of a directory | |
1783 | that can be read. | |
1784 | @end defun | |
1785 | ||
1786 | @defun file-name-all-versions file dirname | |
1787 | This function returns a list of all versions of the file named | |
1788 | @var{file} in directory @var{dirname}. | |
1789 | @end defun | |
1790 | ||
1791 | @defun insert-directory file switches &optional wildcard full-directory-p | |
b22f3a19 RS |
1792 | This function inserts (in the current buffer) a directory listing for |
1793 | directory @var{file}, formatted with @code{ls} according to | |
1794 | @var{switches}. It leaves point after the inserted text. | |
3e01fd9d | 1795 | |
b22f3a19 | 1796 | The argument @var{file} may be either a directory name or a file |
3e01fd9d RS |
1797 | specification including wildcard characters. If @var{wildcard} is |
1798 | non-@code{nil}, that means treat @var{file} as a file specification with | |
1799 | wildcards. | |
1800 | ||
1801 | If @var{full-directory-p} is non-@code{nil}, that means @var{file} is a | |
b22f3a19 RS |
1802 | directory and switches do not contain @samp{-d}, so that the listing |
1803 | should show the full contents of the directory. (The @samp{-d} option | |
1804 | to @code{ls} says to describe a directory itself rather than its | |
1805 | contents.) | |
3e01fd9d RS |
1806 | |
1807 | This function works by running a directory listing program whose name is | |
1808 | in the variable @code{insert-directory-program}. If @var{wildcard} is | |
1809 | non-@code{nil}, it also runs the shell specified by | |
1810 | @code{shell-file-name}, to expand the wildcards. | |
1811 | @end defun | |
1812 | ||
1813 | @defvar insert-directory-program | |
1814 | This variable's value is the program to run to generate a directory listing | |
1815 | for the function @code{insert-directory}. | |
1816 | @end defvar | |
1817 | ||
1818 | @node Create/Delete Dirs | |
1819 | @section Creating and Deleting Directories | |
1820 | @c Emacs 19 features | |
1821 | ||
b22f3a19 RS |
1822 | Most Emacs Lisp file-manipulation functions get errors when used on |
1823 | files that are directories. For example, you cannot delete a directory | |
1824 | with @code{delete-file}. These special functions exist to create and | |
1825 | delete directories. | |
1826 | ||
3e01fd9d RS |
1827 | @defun make-directory dirname |
1828 | This function creates a directory named @var{dirname}. | |
1829 | @end defun | |
1830 | ||
1831 | @defun delete-directory dirname | |
1832 | This function deletes the directory named @var{dirname}. The function | |
1833 | @code{delete-file} does not work for files that are directories; you | |
bfe721d1 KH |
1834 | must use @code{delete-directory} for them. If the directory contains |
1835 | any files, @code{delete-directory} signals an error. | |
3e01fd9d RS |
1836 | @end defun |
1837 | ||
1838 | @node Magic File Names | |
1839 | @section Making Certain File Names ``Magic'' | |
1840 | @cindex magic file names | |
1841 | ||
1842 | @c Emacs 19 feature | |
1843 | You can implement special handling for certain file names. This is | |
1844 | called making those names @dfn{magic}. You must supply a regular | |
b22f3a19 | 1845 | expression to define the class of names (all those that match the |
3e01fd9d RS |
1846 | regular expression), plus a handler that implements all the primitive |
1847 | Emacs file operations for file names that do match. | |
1848 | ||
b22f3a19 | 1849 | The variable @code{file-name-handler-alist} holds a list of handlers, |
3e01fd9d RS |
1850 | together with regular expressions that determine when to apply each |
1851 | handler. Each element has this form: | |
1852 | ||
1853 | @example | |
1854 | (@var{regexp} . @var{handler}) | |
1855 | @end example | |
1856 | ||
1857 | @noindent | |
1858 | All the Emacs primitives for file access and file name transformation | |
1859 | check the given file name against @code{file-name-handler-alist}. If | |
1860 | the file name matches @var{regexp}, the primitives handle that file by | |
1861 | calling @var{handler}. | |
1862 | ||
1863 | The first argument given to @var{handler} is the name of the primitive; | |
1864 | the remaining arguments are the arguments that were passed to that | |
1865 | operation. (The first of these arguments is typically the file name | |
1866 | itself.) For example, if you do this: | |
1867 | ||
1868 | @example | |
1869 | (file-exists-p @var{filename}) | |
1870 | @end example | |
1871 | ||
1872 | @noindent | |
1873 | and @var{filename} has handler @var{handler}, then @var{handler} is | |
1874 | called like this: | |
1875 | ||
1876 | @example | |
1877 | (funcall @var{handler} 'file-exists-p @var{filename}) | |
1878 | @end example | |
1879 | ||
b22f3a19 | 1880 | Here are the operations that a magic file name handler gets to handle: |
3e01fd9d RS |
1881 | |
1882 | @noindent | |
1883 | @code{add-name-to-file}, @code{copy-file}, @code{delete-directory}, | |
1884 | @code{delete-file},@* | |
63ff95ee | 1885 | @code{diff-latest-backup-file}, |
3e01fd9d | 1886 | @code{directory-file-name}, |
63ff95ee | 1887 | @code{directory-files}, |
3e01fd9d RS |
1888 | @code{dired-compress-file}, @code{dired-uncache}, |
1889 | @code{expand-file-name},@* | |
1890 | @code{file-accessible-directory-p}, | |
1891 | @code{file-attributes}, @code{file-directory-p}, | |
1892 | @code{file-executable-p}, @code{file-exists-p}, @code{file-local-copy}, | |
1893 | @code{file-modes}, @code{file-name-all-completions}, | |
1894 | @code{file-name-as-directory}, @code{file-name-completion}, | |
1895 | @code{file-name-directory}, @code{file-name-nondirectory}, | |
1896 | @code{file-name-sans-versions}, @code{file-newer-than-file-p}, | |
5949c48a | 1897 | @code{file-readable-p}, @code{file-regular-p}, @code{file-symlink-p}, |
63ff95ee MW |
1898 | @code{file-truename}, @code{file-writable-p}, |
1899 | @code{get-file-buffer}, | |
bfe721d1 | 1900 | @code{insert-directory}, |
3e01fd9d RS |
1901 | @code{insert-file-contents}, @code{load}, @code{make-directory}, |
1902 | @code{make-symbolic-link}, @code{rename-file}, @code{set-file-modes}, | |
1903 | @code{set-visited-file-modtime}, @code{unhandled-file-name-directory}, | |
1904 | @code{verify-visited-file-modtime}, @code{write-region}. | |
1905 | ||
6ca88231 RS |
1906 | Handlers for @code{insert-file-contents} typically need to clear the |
1907 | buffer's modified flag, with @code{(set-buffer-modified-p nil)}, if the | |
1908 | @var{visit} argument is non-@code{nil}. This also has the effect of | |
1909 | unlocking the buffer if it is locked. | |
1910 | ||
3e01fd9d | 1911 | The handler function must handle all of the above operations, and |
b22f3a19 RS |
1912 | possibly others to be added in the future. It need not implement all |
1913 | these operations itself---when it has nothing special to do for a | |
1914 | certain operation, it can reinvoke the primitive, to handle the | |
1915 | operation ``in the usual way''. It should always reinvoke the primitive | |
1916 | for an operation it does not recognize. Here's one way to do this: | |
3e01fd9d | 1917 | |
841e483d | 1918 | @smallexample |
3e01fd9d RS |
1919 | (defun my-file-handler (operation &rest args) |
1920 | ;; @r{First check for the specific operations} | |
1921 | ;; @r{that we have special handling for.} | |
1922 | (cond ((eq operation 'insert-file-contents) @dots{}) | |
1923 | ((eq operation 'write-region) @dots{}) | |
1924 | @dots{} | |
1925 | ;; @r{Handle any operation we don't know about.} | |
841e483d | 1926 | (t (let ((inhibit-file-name-handlers |
b22f3a19 | 1927 | (cons 'my-file-handler |
841e483d RS |
1928 | (and (eq inhibit-file-name-operation operation) |
1929 | inhibit-file-name-handlers))) | |
1930 | (inhibit-file-name-operation operation)) | |
3e01fd9d | 1931 | (apply operation args))))) |
841e483d RS |
1932 | @end smallexample |
1933 | ||
1934 | When a handler function decides to call the ordinary Emacs primitive for | |
1935 | the operation at hand, it needs to prevent the primitive from calling | |
1936 | the same handler once again, thus leading to an infinite recursion. The | |
1937 | example above shows how to do this, with the variables | |
1938 | @code{inhibit-file-name-handlers} and | |
1939 | @code{inhibit-file-name-operation}. Be careful to use them exactly as | |
1940 | shown above; the details are crucial for proper behavior in the case of | |
1941 | multiple handlers, and for operations that have two file names that may | |
1942 | each have handlers. | |
1943 | ||
1944 | @defvar inhibit-file-name-handlers | |
1945 | This variable holds a list of handlers whose use is presently inhibited | |
1946 | for a certain operation. | |
1947 | @end defvar | |
3e01fd9d | 1948 | |
841e483d RS |
1949 | @defvar inhibit-file-name-operation |
1950 | The operation for which certain handlers are presently inhibited. | |
1951 | @end defvar | |
1952 | ||
1953 | @defun find-file-name-handler file operation | |
3e01fd9d | 1954 | This function returns the handler function for file name @var{file}, or |
841e483d RS |
1955 | @code{nil} if there is none. The argument @var{operation} should be the |
1956 | operation to be performed on the file---the value you will pass to the | |
1957 | handler as its first argument when you call it. The operation is needed | |
1958 | for comparison with @code{inhibit-file-name-operation}. | |
3e01fd9d RS |
1959 | @end defun |
1960 | ||
1961 | @defun file-local-copy filename | |
b22f3a19 RS |
1962 | This function copies file @var{filename} to an ordinary non-magic file, |
1963 | if it isn't one already. | |
1964 | ||
1965 | If @var{filename} specifies a ``magic'' file name, which programs | |
1966 | outside Emacs cannot directly read or write, this copies the contents to | |
1967 | an ordinary file and returns that file's name. | |
3e01fd9d RS |
1968 | |
1969 | If @var{filename} is an ordinary file name, not magic, then this function | |
1970 | does nothing and returns @code{nil}. | |
1971 | @end defun | |
1972 | ||
1973 | @defun unhandled-file-name-directory filename | |
1974 | This function returns the name of a directory that is not magic. | |
1975 | It uses the directory part of @var{filename} if that is not magic. | |
1976 | Otherwise, it asks the handler what to do. | |
1977 | ||
1978 | This is useful for running a subprocess; every subprocess must have a | |
1979 | non-magic directory to serve as its current directory, and this function | |
1980 | is a good way to come up with one. | |
1981 | @end defun | |
841e483d | 1982 | |
22697dac KH |
1983 | @node Format Conversion |
1984 | @section File Format Conversion | |
1985 | ||
1986 | @cindex file format conversion | |
1987 | @cindex encoding file formats | |
1988 | @cindex decoding file formats | |
1989 | The variable @code{format-alist} defines a list of @dfn{file formats}, | |
bfe721d1 | 1990 | which describe textual representations used in files for the data (text, |
22697dac | 1991 | text-properties, and possibly other information) in an Emacs buffer. |
bfe721d1 KH |
1992 | Emacs performs format conversion if appropriate when reading and writing |
1993 | files. | |
22697dac KH |
1994 | |
1995 | @defvar format-alist | |
1996 | This list contains one format definition for each defined file format. | |
1997 | @end defvar | |
1998 | ||
1999 | @cindex format definition | |
2000 | Each format definition is a list of this form: | |
2001 | ||
2002 | @example | |
2003 | (@var{name} @var{doc-string} @var{regexp} @var{from-fn} @var{to-fn} @var{modify} @var{mode-fn}) | |
2004 | @end example | |
2005 | ||
2006 | Here is what the elements in a format definition mean: | |
2007 | ||
2008 | @table @var | |
2009 | @item name | |
2010 | The name of this format. | |
2011 | ||
2012 | @item doc-string | |
2013 | A documentation string for the format. | |
2014 | ||
2015 | @item regexp | |
2016 | A regular expression which is used to recognize files represented in | |
2017 | this format. | |
2018 | ||
2019 | @item from-fn | |
2020 | A function to call to decode data in this format (to convert file data into | |
2021 | the usual Emacs data representation). | |
2022 | ||
2023 | The @var{from-fn} is called with two args, @var{begin} and @var{end}, | |
2024 | which specify the part of the buffer it should convert. It should convert | |
2025 | the text by editing it in place. Since this can change the length of the | |
2026 | text, @var{from-fn} should return the modified end position. | |
2027 | ||
bfe721d1 | 2028 | One responsibility of @var{from-fn} is to make sure that the beginning |
22697dac KH |
2029 | of the file no longer matches @var{regexp}. Otherwise it is likely to |
2030 | get called again. | |
2031 | ||
2032 | @item to-fn | |
2033 | A function to call to encode data in this format (to convert | |
2034 | the usual Emacs data representation into this format). | |
2035 | ||
2036 | The @var{to-fn} is called with two args, @var{begin} and @var{end}, | |
2037 | which specify the part of the buffer it should convert. There are | |
2038 | two ways it can do the conversion: | |
2039 | ||
2040 | @itemize @bullet | |
2041 | @item | |
2042 | By editing the buffer in place. In this case, @var{to-fn} should | |
2043 | return the end-position of the range of text, as modified. | |
2044 | ||
2045 | @item | |
2046 | By returning a list of annotations. This is a list of elements of the | |
2047 | form @code{(@var{position} . @var{string})}, where @var{position} is an | |
2048 | integer specifying the relative position in the text to be written, and | |
2049 | @var{string} is the annotation to add there. The list must be sorted in | |
2050 | order of position when @var{to-fn} returns it. | |
2051 | ||
2052 | When @code{write-region} actually writes the text from the buffer to the | |
2053 | file, it intermixes the specified annotations at the corresponding | |
2054 | positions. All this takes place without modifying the buffer. | |
2055 | @end itemize | |
2056 | ||
2057 | @item modify | |
2058 | A flag, @code{t} if the encoding function modifies the buffer, and | |
2059 | @code{nil} if it works by returning a list of annotations. | |
2060 | ||
2061 | @item mode | |
2062 | A mode function to call after visiting a file converted from this | |
2063 | format. | |
2064 | @end table | |
2065 | ||
2066 | The function @code{insert-file-contents} automatically recognizes file | |
2067 | formats when it reads the specified file. It checks the text of the | |
2068 | beginning of the file against the regular expressions of the format | |
2069 | definitions, and if it finds a match, it calls the decoding function for | |
2070 | that format. Then it checks all the known formats over again. | |
2071 | It keeps checking them until none of them is applicable. | |
2072 | ||
2073 | Visiting a file, with @code{find-file-noselect} or the commands that use | |
2074 | it, performs conversion likewise (because it calls | |
bfe721d1 KH |
2075 | @code{insert-file-contents}); it also calls the mode function for each |
2076 | format that it decodes. It stores a list of the format names in the | |
2077 | buffer-local variable @code{buffer-file-format}. | |
22697dac KH |
2078 | |
2079 | @defvar buffer-file-format | |
bfe721d1 KH |
2080 | This variable states the format of the visited file. More precisely, |
2081 | this is a list of the file format names that were decoded in the course | |
2082 | of visiting the current buffer's file. It is always local in all | |
22697dac KH |
2083 | buffers. |
2084 | @end defvar | |
2085 | ||
2086 | When @code{write-region} writes data into a file, it first calls the | |
bfe721d1 KH |
2087 | encoding functions for the formats listed in @code{buffer-file-format}, |
2088 | in the order of appearance in the list. | |
22697dac KH |
2089 | |
2090 | @defun format-write-file file format | |
2091 | This command writes the current buffer contents into the file @var{file} | |
2092 | in format @var{format}, and makes that format the default for future | |
bfe721d1 KH |
2093 | saves of the buffer. The argument @var{format} is a list of format |
2094 | names. | |
22697dac KH |
2095 | @end defun |
2096 | ||
63ff95ee MW |
2097 | @defun format-find-file file format |
2098 | This command finds the file @var{file}, converting it according to | |
2099 | format @var{format}. It also makes @var{format} the default if the | |
2100 | buffer is saved later. | |
2101 | ||
2102 | The argument @var{format} is a list of format names. If @var{format} is | |
2103 | @code{nil}, no conversion takes place. Interactively, typing just | |
2104 | @key{RET} for @var{format} specifies @code{nil}. | |
2105 | @end defun | |
2106 | ||
2107 | @defun format-insert-file file format %optional beg end | |
2108 | This command inserts the contents of file @var{file}, converting it | |
2109 | according to format @var{format}. If @var{beg} and @var{end} are | |
2110 | non-@code{nil}, they specify which part of the file to read, as in | |
2111 | @code{insert-file-contents} (@pxref{Reading from Files}). | |
2112 | ||
2113 | The return value is like what @code{insert-file-contents} returns: a | |
2114 | list of the absolute file name and the length of the data inserted | |
2115 | (after conversion). | |
2116 | ||
2117 | The argument @var{format} is a list of format names. If @var{format} is | |
2118 | @code{nil}, no conversion takes place. Interactively, typing just | |
2119 | @key{RET} for @var{format} specifies @code{nil}. | |
2120 | @end defun | |
2121 | ||
22697dac KH |
2122 | @defvar auto-save-file-format |
2123 | This variable specifies the format to use for auto-saving. Its value is | |
2124 | a list of format names, just like the value of | |
2125 | @code{buffer-file-format}; but it is used instead of | |
2126 | @code{buffer-file-format} for writing auto-save files. This variable | |
2127 | is always local in all buffers. | |
2128 | @end defvar | |
2129 | ||
841e483d RS |
2130 | @node Files and MS-DOS |
2131 | @section Files and MS-DOS | |
2132 | @cindex MS-DOS file types | |
2133 | @cindex file types on MS-DOS | |
2134 | @cindex text files and binary files | |
2135 | @cindex binary files and text files | |
2136 | ||
2137 | Emacs on MS-DOS makes a distinction between text files and binary | |
b22f3a19 RS |
2138 | files. This is necessary because ordinary text files on MS-DOS use a |
2139 | two character sequence between lines: carriage-return and linefeed | |
bfe721d1 | 2140 | (@sc{crlf}). Emacs expects just a newline character (a linefeed) between |
b22f3a19 RS |
2141 | lines. When Emacs reads or writes a text file on MS-DOS, it needs to |
2142 | convert the line separators. This means it needs to know which files | |
2143 | are text files and which are binary. It makes this decision when | |
2144 | visiting a file, and records the decision in the variable | |
2145 | @code{buffer-file-type} for use when the file is saved. | |
2146 | ||
2147 | @xref{MS-DOS Subprocesses}, for a related feature for subprocesses. | |
841e483d RS |
2148 | |
2149 | @defvar buffer-file-type | |
2150 | This variable, automatically local in each buffer, records the file type | |
b22f3a19 RS |
2151 | of the buffer's visited file. The value is @code{nil} for text, |
2152 | @code{t} for binary. | |
841e483d RS |
2153 | @end defvar |
2154 | ||
2155 | @defun find-buffer-file-type filename | |
2156 | This function determines whether file @var{filename} is a text file | |
2157 | or a binary file. It returns @code{nil} for text, @code{t} for binary. | |
2158 | @end defun | |
2159 | ||
2160 | @defopt file-name-buffer-file-type-alist | |
2161 | This variable holds an alist for distinguishing text files from binary | |
2162 | files. Each element has the form (@var{regexp} . @var{type}), where | |
2163 | @var{regexp} is matched against the file name, and @var{type} may be is | |
2164 | @code{nil} for text, @code{t} for binary, or a function to call to | |
2165 | compute which. If it is a function, then it is called with a single | |
2166 | argument (the file name) and should return @code{t} or @code{nil}. | |
2167 | @end defopt | |
2168 | ||
2169 | @defopt default-buffer-file-type | |
2170 | This variable specifies the default file type for files whose names | |
2171 | don't indicate anything in particular. Its value should be @code{nil} | |
2172 | for text, or @code{t} for binary. | |
2173 | @end defopt | |
2174 | ||
2175 | @deffn Command find-file-text filename | |
2176 | Like @code{find-file}, but treat the file as text regardless of its name. | |
2177 | @end deffn | |
2178 | ||
2179 | @deffn Command find-file-binary filename | |
2180 | Like @code{find-file}, but treat the file as binary regardless of its | |
2181 | name. | |
2182 | @end deffn |