From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: revert-buffer without question?
Date: Thu, 24 Feb 2005 16:03:58 -0700 [thread overview]
Message-ID: <3874r3F5leqq2U1@individual.net> (raw)
In-Reply-To: <pan.2005.02.24.20.28.50.3916@robber.de>
Toni K. Trampert wrote:
>Phillip Lord wrote:
>>(defun revert-buffer-noask()
>> (interactive)
>> (revert-buffer nil t))
>>
>>should do it.
>
> It does it.
>
> What is the meaning of the "nil t" construction?
,----[ C-h f revert-buffer RET ]
| revert-buffer is an interactive compiled Lisp function in `files'.
| (revert-buffer &optional IGNORE-AUTO NOCONFIRM PRESERVE-MODES)
|
| Replace current buffer text with the text of the visited file on disk.
| This undoes all changes since the file was visited or saved.
| With a prefix argument, offer to revert from latest auto-save file, if
| that is more recent than the visited file.
|
| This command also works for special buffers that contain text which
| doesn't come from a file, but reflects some other data base instead:
| for example, Dired buffers and buffer-list buffers. In these cases,
| it reconstructs the buffer contents from the appropriate data base.
|
| When called from Lisp, the first argument is IGNORE-AUTO; only offer
| to revert from the auto-save file when this is nil. Note that the
| sense of this argument is the reverse of the prefix argument, for the
| sake of backward compatibility. IGNORE-AUTO is optional, defaulting
| to nil.
|
| Optional second argument NOCONFIRM means don't ask for confirmation at
| all. (The local variable `revert-without-query', if non-nil, prevents
| confirmation.)
|
| Optional third argument PRESERVE-MODES non-nil means don't alter
| the files modes. Normally we reinitialize them using `normal-mode'.
|
| If the value of `revert-buffer-function' is non-nil, it is called to
| do all the work for this command. Otherwise, the hooks
| `before-revert-hook' and `after-revert-hook' are run at the beginning
| and the end, and if `revert-buffer-insert-file-contents-function' is
| non-nil, it is called instead of rereading visited file contents.
`----
--
Kevin Rodgers
next prev parent reply other threads:[~2005-02-24 23:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 14:39 revert-buffer without question? Toni K. Trampert
2005-02-24 14:57 ` Phillip Lord
2005-02-24 20:28 ` Toni K. Trampert
2005-02-24 22:57 ` August
2005-02-24 23:03 ` Kevin Rodgers [this message]
2005-02-25 0:43 ` Enila Nero
2005-03-07 6:36 ` Kyle Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3874r3F5leqq2U1@individual.net \
--to=ihs_4664@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).