From: Roland Winkler <roland.winkler@physik.uni-erlangen.de>
Subject: status report of tar-summarize-buffer and/or set-buffer-multibyte?
Date: Sun, 24 Aug 2003 19:07:16 +0200 [thread overview]
Message-ID: <16200.61636.695272.396005@tfkp07.physik.uni-erlangen.de> (raw)
In GNU Emacs 21.2.1 (i386-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2002-04-09 on tfkp12
configured using `configure --prefix=/nfs/common --libexecdir=/nfs/common/lib --bindir=/nfs/common/lib/emacs/21.2/bin/i686-Linux --mandir=/nfs/common/share/man --infodir=/nfs/common/share/info --with-gcc --with-pop --with-x --with-x-toolkit=athena i386-pc-linux'
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: POSIX
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_US
locale-coding-system: iso-latin-1
default-enable-multibyte-characters: nil
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
Usually tar mode is a nice tool for viewing tar files. But today,
when I tried to view a moderately-sized tar file (25 Mb) it seemed
to me that emacs would hang indefinitely. After a while, I figured
out that the culprit was the line
(set-buffer-multibyte t)
in tar-summarize-buffer. On my computer this function needed about
two minutes to do its job. Would it make sense here to provide a
status report so that impatient people like me are not fooled to
believe emacs hangs indefintely? Is this possible??
The point is that tar-mode issues the messages "Parsing tar file..."
and "Parsing tar file...done" which gives the impression that the
parsing was the biggest part to be done when a tar file is loaded.
Apparently, this is not always correct.
Roland
PS: Let me know if you are interested in an example file. I don't
want to send 25 Mb of junk to everybody who is reading this.
reply other threads:[~2003-08-24 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=16200.61636.695272.396005@tfkp07.physik.uni-erlangen.de \
--to=roland.winkler@physik.uni-erlangen.de \
/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.