all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles.bader@necel.com>
Cc: emacs-devel@gnu.org, Kenichi Handa <handa@m17n.org>
Subject: Re: Emacs manipulate files with long-lines very slowly.
Date: Fri, 08 Dec 2006 18:18:13 +0900	[thread overview]
Message-ID: <buoodqebvai.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <20061208090419.GA8476@localdomain> (Hongyi Zhao's message of "Fri\, 8 Dec 2006 17\:04\:19 +0800")

Hongyi Zhao <hongyi.zhao@gmail.com> writes:
> But I can open it with gedit and edit it very quickly, is there any tricks
> to solve the problem or some bugs in Emacs?

Is that really a windows file?  The lines are (mostly) separated with CR
(^M), which as far as I know is _not_ the windows line separator, but in
fact the old macintosh line separator.  Emacs normally handles such
files well, but in this case, there seem to be a few lines which use
newline instead of CR, so emacs thinks it isn't a macintosh file either.

I'd suggest just forcing it to use a consistent convention.

Try the following:

   (1) visit the file
   (2) force newlines to be written using CR:  C-x C-m f mac RET
   (3) save the file:  C-x C-s
   (4) kill the buffer:  C-x C-k RET
   (5) revisit the changed file

-Miles

-- 
"I distrust a research person who is always obviously busy on a task."
   --Robert Frosch, VP, GM Research

  reply	other threads:[~2006-12-08  9:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08  9:04 Emacs manipulate files with long-lines very slowly Hongyi Zhao
2006-12-08  9:18 ` Miles Bader [this message]
2006-12-08 10:10   ` Hongyi Zhao
2006-12-08 10:09     ` Miles Bader
2006-12-08 10:52       ` Hongyi Zhao
2006-12-08 10:58         ` Miles Bader
2006-12-12 11:42     ` Kenichi Handa
2006-12-09  1:26 ` Richard Stallman

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=buoodqebvai.fsf@dhapc248.dev.necel.com \
    --to=miles.bader@necel.com \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=miles@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 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.