summaryrefslogtreecommitdiff
path: root/lisp/tar-mode.el
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2011-11-14 15:59:56 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2011-11-14 15:59:56 -0800
commit91af3942e9ab5540b3ab4dde6733bc883dc2abdd (patch)
tree7a83e35278714a4498663fc968d36210d8c6436e /lisp/tar-mode.el
parent5ef215d87480e348e432b4e323b1ba24e27ebf81 (diff)
downloademacs-91af3942e9ab5540b3ab4dde6733bc883dc2abdd.tar.gz
Spelling fixes.
Diffstat (limited to 'lisp/tar-mode.el')
-rw-r--r--lisp/tar-mode.el2
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/tar-mode.el b/lisp/tar-mode.el
index cfa406c2b48..ff528fcc9df 100644
--- a/lisp/tar-mode.el
+++ b/lisp/tar-mode.el
@@ -142,7 +142,7 @@ This information is useful, but it takes screen space away from file names."
;; The Tar data is made up of bytes and better manipulated as bytes
;; and can be very large, so insert/delete can be costly. The summary we
-;; want to display may contain non-ascci chars, of course, so we'd like it
+;; want to display may contain non-ascii chars, of course, so we'd like it
;; to be multibyte. We used to keep both in the same buffer and switch
;; from/to uni/multibyte. But this had several downsides:
;; - set-buffer-multibyte has an O(N^2) worst case that tends to be triggered