415 |
|
|
416 |
@c Emacs 19 feature |
@c Emacs 19 feature |
417 |
@defvar write-contents-functions |
@defvar write-contents-functions |
418 |
This works just like @code{write-file-functions}, but it is intended for |
This works just like @code{write-file-functions}, but it is intended |
419 |
hooks that pertain to the contents of the file, as opposed to hooks that |
for hooks that pertain to the buffer's contents, not to the particular |
420 |
pertain to the file's name or location. Such hooks are usually set up by |
visited file or its location. Such hooks are usually set up by major |
421 |
major modes, as buffer-local bindings for this variable. If any of the |
modes, as buffer-local bindings for this variable. This variable |
422 |
functions in this hook returns non-@code{nil}, the file is considered |
automatically becomes buffer-local whenever it is set; switching to a |
423 |
already written and the rest are not called and neither are the functions |
new major mode always resets this variable, but calling |
424 |
in @code{write-file-functions}. |
@code{set-visited-file-name} does not. |
425 |
|
|
426 |
This variable automatically becomes buffer-local whenever it is set; |
If any of the functions in this hook returns non-@code{nil}, the file |
427 |
switching to a new major mode always resets this variable, but |
is considered already written and the rest are not called and neither |
428 |
calling @code{set-visited-file-name} does not. |
are the functions in @code{write-file-functions}. |
429 |
@end defvar |
@end defvar |
430 |
|
|
431 |
@defopt before-save-hook |
@defopt before-save-hook |
2646 |
@end defun |
@end defun |
2647 |
|
|
2648 |
@defun file-remote-p filename |
@defun file-remote-p filename |
2649 |
This function returns @code{t} if @var{filename} is a remote file. |
This function tests whether @var{filename} is a remote file. If |
2650 |
|
@var{filename} is local (not remote), the return value is @code{nil}. |
2651 |
|
If @var{filename} is indeed remote, the return value is a string that |
2652 |
|
identifies the remote system. |
2653 |
|
|
2654 |
|
This identifier string may include a host name, a user name, and |
2655 |
|
characters designating the method used to access the remote system. |
2656 |
|
For example, the remote identifier string for the filename |
2657 |
|
@code{/ssh:user@@host:/some/file} is @code{/ssh:user@@host:}. |
2658 |
|
|
2659 |
|
If @code{file-remote-p} returns the same identifier for two different |
2660 |
|
filenames, that means they are stored on the same file system and can |
2661 |
|
be accessed locally with respect to each other. This means, for |
2662 |
|
example, that it is possible to start a remote process accessing both |
2663 |
|
files at the same time. Implementors of file handlers need to ensure |
2664 |
|
this principle is valid. |
2665 |
@end defun |
@end defun |
2666 |
|
|
2667 |
@defun unhandled-file-name-directory filename |
@defun unhandled-file-name-directory filename |