From: Kenichi Handa <handa@m17n.org>
To: Sam Steingold <sds@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: cvs head issues: slow utf-8 save; frames resising
Date: Thu, 13 Mar 2008 10:23:13 +0900 [thread overview]
Message-ID: <E1JZcA5-0002Se-CN@etlken.m17n.org> (raw)
In-Reply-To: <47D83C38.7040708@gnu.org> (message from Sam Steingold on Wed, 12 Mar 2008 16:25:28 -0400)
In article <47D83C38.7040708@gnu.org>, Sam Steingold <sds@gnu.org> writes:
> 1. ever since the unicode merge, saving utf-8 files with non-ascii
> characters in them takes tens of seconds.
It seems that the slow part is in select-safe-coding-system.
Please try to save a buffer by this.
Esc : (let ((select-safe-coding-system-function nil)) (save-buffer)) RET
How is the speed?
---
Kenichi Handa
handa@ni.aist.go.jp
prev parent reply other threads:[~2008-03-13 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 20:25 cvs head issues: slow utf-8 save; frames resising Sam Steingold
2008-03-13 1:23 ` Kenichi Handa [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1JZcA5-0002Se-CN@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=sds@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).