all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Hansen <larsh@math.ku.dk>
Cc: emacs-devel@gnu.org
Subject: Documentation of write-contents-functions
Date: Wed, 23 Jun 2004 11:14:42 +0200	[thread overview]
Message-ID: <40D94A02.3090809@math.ku.dk> (raw)

[-- Attachment #1: Type: text/plain, Size: 138 bytes --]

To me the description in files.texi of write-contents-functions does not 
make much sense.
I suggest the chances attached.
Do you agree?


[-- Attachment #2: files.texi.diff --]
[-- Type: text/plain, Size: 1402 bytes --]

*** files.texi.~1.66.~	Sun May 30 08:41:47 2004
--- files.texi	Tue Jun 22 21:04:00 2004
***************
*** 416,426 ****
  @c Emacs 19 feature
  @defvar write-contents-functions
  This works just like @code{write-file-functions}, but it is intended for
! hooks that pertain to the contents of the file, as opposed to hooks that
! pertain to where the file came from.  Such hooks are usually set up by
  major modes, as buffer-local bindings for this variable.  If any of the
! functions in this hook returns non-@code{nil}, @code{write-file-functions}
! is not run.
  
  This variable automatically becomes buffer-local whenever it is set;
  switching to a new major mode always resets this variable, but
--- 416,427 ----
  @c Emacs 19 feature
  @defvar write-contents-functions
  This works just like @code{write-file-functions}, but it is intended for
! hooks that pertain to the contents of the buffer, as opposed to hooks that
! pertain to the file the buffers visits.  Such hooks are usually set up by
  major modes, as buffer-local bindings for this variable.  If any of the
! functions in this hook returns non-@code{nil}, the file is considered
! already written and the rest are not called and neither are the functions
! in @code{write-file-functions}.
  
  This variable automatically becomes buffer-local whenever it is set;
  switching to a new major mode always resets this variable, but

[-- Attachment #3: files.el.diff --]
[-- Type: text/plain, Size: 893 bytes --]

*** files.el.~1.705.~	Thu Jun 17 08:26:50 2004
--- files.el	Tue Jun 22 21:02:01 2004
***************
*** 393,399 ****
  (defvar write-contents-functions nil
    "List of functions to be called before writing out a buffer to a file.
  If one of them returns non-nil, the file is considered already written
! and the rest are not called.
  
  This variable is meant to be used for hooks that pertain to the
  buffer's contents, not to the particular visited file; thus,
--- 393,400 ----
  (defvar write-contents-functions nil
    "List of functions to be called before writing out a buffer to a file.
  If one of them returns non-nil, the file is considered already written
! and the rest are not called and neither are the functions in
! `write-file-functions'.
  
  This variable is meant to be used for hooks that pertain to the
  buffer's contents, not to the particular visited file; thus,

[-- Attachment #4: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

             reply	other threads:[~2004-06-23  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23  9:14 Lars Hansen [this message]
2004-06-23 14:13 ` Documentation of write-contents-functions Luc Teirlinck

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40D94A02.3090809@math.ku.dk \
    --to=larsh@math.ku.dk \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.