unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: alin <as1789@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: as the accident occued...  long lines in emacs buffers.
Date: Fri, 13 Nov 2015 21:09:21 +0200	[thread overview]
Message-ID: <87wptlpvha.fsf@gmail.com> (raw)
In-Reply-To: 83d1vdg2ea.fsf@gnu.org



Eli Zaretskii <eliz@gnu.org> writes:

>> From: David Kastrup <dak@gnu.org>
>> Date: Fri, 13 Nov 2015 17:40:02 +0100
>> Cc: John Wiegley <jwiegley@gmail.com>, Brandon Invergo <brandon@invergo.net>,
>> 	emacs-devel@gnu.org
>> 
>> > I'll settle for "as fast as one would expect given its behavior on short
>> > lines".
>> 
>> Though purportedly this should have been somewhat addressed by
>> 
>> cache-long-scans is a variable defined in ‘C source code’.
>> Its value is t
>
> No, this variable is unrelated.  It only helps when Emacs looks for a
> newline.  By contrast, redisplay slowness with long lines has almost
> nothing to do with searching a buffer for newlines, its main cause is
> that to move to the next visual line the display engine must
> completely traverse the current line.



Anyway.  Emacs does not work well.  This is a fact that I see many times
when I open shell-processes.

I have the full plan in my mind to execute it.  And all the needed
experience and background.

I cannot work alone.  I need somebody to discuss with him/her and help
me read/see what I am doing and what's the next step.  As this is a a
complex problem and I do not want to lose the time working.  This would
be painful to think to alone.

I think I will be available to do this in the months
Mars-Avr-May-June-July-Au. If somebody around Paris want to involve in
this, please answer me in the mean time.

If not, I will be available for this task after July 2018 or sporadic.
I think it will take 7-8 week-ends to execute it.  It will be lot of
work.





Alin.



-- 
No GNUs is bad news.



  parent reply	other threads:[~2015-11-13 19:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87k2q1xsg9.fsf@gmail.com>
     [not found] ` <1446668449.11811.11.camel@invergo.net>
     [not found]   ` <87mvupvonu.fsf@gmail.com>
     [not found]     ` <1447368233.11811.52.camel@invergo.net>
     [not found]       ` <87wptmyaml.fsf@gmail.com>
     [not found]         ` <1447409234.32571.1.camel@invergo.net>
2015-11-13 15:28           ` The Little Computer alin
     [not found]             ` <m24mgp7v7i.fsf@Vulcan.attlocal.net>
2015-11-13 16:27               ` as the accident occued... long lines in emacs buffers Alin Soare
2015-11-13 16:33                 ` David Kastrup
2015-11-13 16:40                   ` David Kastrup
2015-11-13 17:39                     ` alin
2015-11-13 18:50                     ` Eli Zaretskii
2015-11-13 19:01                       ` alin
2015-11-13 19:09                       ` alin [this message]
2015-11-13 16:46                   ` alin

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=87wptlpvha.fsf@gmail.com \
    --to=as1789@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).