unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexis <flexibeast@gmail.com>
To: 18530@debbugs.gnu.org
Cc: Amit Barve <mtbar131@gmail.com>
Subject: bug#18530: 24.3; Emacs unable to handle very large lines
Date: Sun, 28 Sep 2014 20:10:45 +1000	[thread overview]
Message-ID: <87wq8of3bn.fsf@gmail.com> (raw)
In-Reply-To: <CAMy5G4jCKcfCWF=zWEAUszCO1k=jN_A79jNvez1=7+u-DMCELg@mail.gmail.com>


Amit Barve writes:

> Thanks a lot Alexis for your reply!

You're welcome. :-)

> "toggle-truncate-lines" and "fil-paragraph" worked!!
> Though execution of both commands take a long time
> but after that I can move and edit very quickly!

Oh, well, i wasn't suggesting those commands as any kind of solution; i
just wanted to indicate what behaviours i observed when using those
commands.

> These commands work when emacs is opened with -nw option
> if I open emacs in GUI mode then line count is still shown as
> 'L??'

Hm, okay. In my own tests, above i was using Emacs in an X window, not
in a terminal ....

> Anyway thanks a lot! Now I can work with such big files!
> but I think this can still be considered as bug!
> because vim opens the file quite easily and without any
> modifications!

*nod* Yes, when i open test.txt in Vim, moving to the end of the line
with $, or to the beginning of the line with ^, both take less than a
second. And cursor movement with j, k etc. is basically
responsive. Whereas in Emacs, trying to move point up or down results in
20+ seconds of lag before point is actually moved.

As another data point: i tried disabling `visual-line-mode`, instead
loading longlines.el from EmacsWiki and enabling
`longlines-mode`. `longlines-mode` was /much/ more responsive - moving
point up, down, to beginning of line, or to end of line, all only had a
lag of 1-2 seconds.





  parent reply	other threads:[~2014-09-28 10:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22  5:27 bug#18530: 24.3; Emacs unable to handle very large lines Amit Barve
2014-09-28  7:16 ` Alexis
     [not found]   ` <CAMy5G4jCKcfCWF=zWEAUszCO1k=jN_A79jNvez1=7+u-DMCELg@mail.gmail.com>
2014-09-28 10:10     ` Alexis [this message]
2014-09-28 16:21       ` Eli Zaretskii
2014-09-29  1:26         ` Amit Barve
2014-09-29  2:30           ` Stefan Monnier
2014-09-29  2:42             ` Eli Zaretskii
2014-09-29  2:51               ` Amit Barve
2014-09-28 16:19   ` Eli Zaretskii

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=87wq8of3bn.fsf@gmail.com \
    --to=flexibeast@gmail.com \
    --cc=18530@debbugs.gnu.org \
    --cc=mtbar131@gmail.com \
    /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).