summaryrefslogtreecommitdiff
path: root/lisp/format.el
diff options
context:
space:
mode:
authorErik Naggum <erik@naggum.no>1996-01-14 07:34:30 +0000
committerErik Naggum <erik@naggum.no>1996-01-14 07:34:30 +0000
commit9cd5830fc150859fd828783fafe807036f641c0f (patch)
tree92b353a31fed07964155b45734ea17a4f3294bf0 /lisp/format.el
parent6a8cea1cd7a411eae7420ac78a1a675fec07f985 (diff)
downloademacs-9cd5830fc150859fd828783fafe807036f641c0f.tar.gz
Update FSF's address.
Diffstat (limited to 'lisp/format.el')
-rw-r--r--lisp/format.el65
1 files changed, 35 insertions, 30 deletions
diff --git a/lisp/format.el b/lisp/format.el
index c3c8c393b13..2a66b56846a 100644
--- a/lisp/format.el
+++ b/lisp/format.el
@@ -1,4 +1,5 @@
;;; format.el --- read and save files in multiple formats
+
;; Copyright (c) 1994, 1995 Free Software Foundation
;; Author: Boris Goldowsky <boris@gnu.ai.mit.edu>
@@ -9,53 +10,57 @@
;; it under the terms of the GNU General Public License as published by
;; the Free Software Foundation; either version 2, or (at your option)
;; any later version.
-;;
+
;; GNU Emacs is distributed in the hope that it will be useful,
;; but WITHOUT ANY WARRANTY; without even the implied warranty of
;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
;; GNU General Public License for more details.
-;;
+
;; You should have received a copy of the GNU General Public License
-;; along with GNU Emacs; see the file COPYING. If not, write to
-;; the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.
+;; along with GNU Emacs; see the file COPYING. If not, write to the
+;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+;; Boston, MA 02111-1307, USA.
;;; Commentary:
-;; This file defines a unified mechanism for saving & loading files stored in
-;; different formats. `format-alist' contains information that directs
+
+;; This file defines a unified mechanism for saving & loading files stored
+;; in different formats. `format-alist' contains information that directs
;; Emacs to call an encoding or decoding function when reading or writing
;; files that match certain conditions.
;;
-;; When a file is visited, its format is determined by matching the beginning
-;; of the file against regular expressions stored in `format-alist'. If this
-;; fails, you can manually translate the buffer using `format-decode-buffer'.
-;; In either case, the formats used are listed in the variable
-;; `buffer-file-format', and become the default format for saving the buffer.
-;; To save a buffer in a different format, change this variable, or use
-;; `format-write-file'.
+;; When a file is visited, its format is determined by matching the
+;; beginning of the file against regular expressions stored in
+;; `format-alist'. If this fails, you can manually translate the buffer
+;; using `format-decode-buffer'. In either case, the formats used are
+;; listed in the variable `buffer-file-format', and become the default
+;; format for saving the buffer. To save a buffer in a different format,
+;; change this variable, or use `format-write-file'.
;;
;; Auto-save files are normally created in the same format as the visited
-;; file, but the variable `auto-save-file-format' can be set to a particularly
-;; fast or otherwise preferred format to be used for auto-saving (or nil to do
-;; no encoding on auto-save files, but then you risk losing any
-;; text-properties in the buffer).
+;; file, but the variable `auto-save-file-format' can be set to a
+;; particularly fast or otherwise preferred format to be used for
+;; auto-saving (or nil to do no encoding on auto-save files, but then you
+;; risk losing any text-properties in the buffer).
;;
-;; You can manually translate a buffer into or out of a particular format with
-;; the functions `format-encode-buffer' and `format-decode-buffer'.
-;; To translate just the region use the functions `format-encode-region' and
-;; `format-decode-region'.
+;; You can manually translate a buffer into or out of a particular format
+;; with the functions `format-encode-buffer' and `format-decode-buffer'.
+;; To translate just the region use the functions `format-encode-region'
+;; and `format-decode-region'.
;;
-;; You can define a new format by writing the encoding and decoding functions,
-;; and adding an entry to `format-alist'. See enriched.el for an example of
-;; how to implement a file format. There are various functions defined
-;; in this file that may be useful for writing the encoding and decoding
-;; functions:
-;; * `format-annotate-region' and `format-deannotate-region' allow a single
-;; alist of information to be used for encoding and decoding. The alist
-;; defines a correspondence between strings in the file ("annotations")
-;; and text-properties in the buffer.
+;; You can define a new format by writing the encoding and decoding
+;; functions, and adding an entry to `format-alist'. See enriched.el for
+;; an example of how to implement a file format. There are various
+;; functions defined in this file that may be useful for writing the
+;; encoding and decoding functions:
+;; * `format-annotate-region' and `format-deannotate-region' allow a
+;; single alist of information to be used for encoding and decoding.
+;; The alist defines a correspondence between strings in the file
+;; ("annotations") and text-properties in the buffer.
;; * `format-replace-strings' is similarly useful for doing simple
;; string->string translations in a reversible manner.
+;;; Code:
+
(put 'buffer-file-format 'permanent-local t)
(defconst format-alist