summaryrefslogtreecommitdiff
path: root/lisp/tar-mode.el
diff options
context:
space:
mode:
authorDave Love <fx@gnu.org>1998-04-29 22:34:42 +0000
committerDave Love <fx@gnu.org>1998-04-29 22:34:42 +0000
commit4063eb1c9cdda753fd4d2a2b10456f5df3cfed6e (patch)
treeccfddc5695ab78290814c8790a68e2135f70e821 /lisp/tar-mode.el
parent9516059404050d7ba391c5415d2684327ee55276 (diff)
downloademacs-4063eb1c9cdda753fd4d2a2b10456f5df3cfed6e.tar.gz
(tar-mode-write-file): Protect from null tar-header-offset.
Diffstat (limited to 'lisp/tar-mode.el')
-rw-r--r--lisp/tar-mode.el5
1 files changed, 4 insertions, 1 deletions
diff --git a/lisp/tar-mode.el b/lisp/tar-mode.el
index c2d2033a641..dd12d9bbca9 100644
--- a/lisp/tar-mode.el
+++ b/lisp/tar-mode.el
@@ -1205,7 +1205,10 @@ Leaves the region wide."
;; Doing this here confuses things - the region gets left too wide!
;; I suppose this is run in a context where changing the buffer is bad.
;; (tar-pad-to-blocksize)
- (write-region tar-header-offset (point-max) buffer-file-name nil t)
+ ;; tar-header-offset turns out to be null for files fetched with W3,
+ ;; at least.
+ (write-region (or tar-header-offset (point-min)) (point-max)
+ buffer-file-name nil t)
(tar-clear-modification-flags)
(set-buffer-modified-p nil))
(narrow-to-region 1 tar-header-offset))