unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Amit Barve <mtbar131@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18530@debbugs.gnu.org, Alexis <flexibeast@gmail.com>
Subject: bug#18530: 24.3; Emacs unable to handle very large lines
Date: Mon, 29 Sep 2014 06:56:53 +0530	[thread overview]
Message-ID: <CAMy5G4hO-iPzaise_9VphEeH9TPdC-zEB44yCsDba94SkCvuag@mail.gmail.com> (raw)
In-Reply-To: <83wq8nn2bq.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

Eil I accept that emacs is way powerful than vim and other
editors. Even I am also a strong supporter of emacs.

I filed this bug because for me it was very difficult to work
with "long lines" and I don't want to use some other editor
just for this purpose.

I think if we can get over this limitation of emacs it will
make emacs a little more powerful!


On Sun, Sep 28, 2014 at 9:51 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Alexis <flexibeast@gmail.com>
> > Date: Sun, 28 Sep 2014 20:10:45 +1000
> > Cc: Amit Barve <mtbar131@gmail.com>
> >
> > *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.
>
> Does Vim support different font sizes on the same line, inline images,
> display properties, overlays, invisible text, etc.?  These features is
> what makes this particular case hard; other editors don't need to
> handle all that complexity.
>

[-- Attachment #2: Type: text/html, Size: 1729 bytes --]

  reply	other threads:[~2014-09-29  1:26 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
2014-09-28 16:21       ` Eli Zaretskii
2014-09-29  1:26         ` Amit Barve [this message]
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=CAMy5G4hO-iPzaise_9VphEeH9TPdC-zEB44yCsDba94SkCvuag@mail.gmail.com \
    --to=mtbar131@gmail.com \
    --cc=18530@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=flexibeast@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).