From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: window-scroll-functions and performance
Date: Tue, 16 Aug 2011 10:03:38 +0200 [thread overview]
Message-ID: <87wred236t.fsf@gmail.com> (raw)
In-Reply-To: <83wreduahf.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Aug 2011 09:38:36 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
>> Date: Tue, 16 Aug 2011 07:56:23 +0200
>>
>> Similar to this, scrolling in org buffers is actually very slow
>> (impossible to use) unless all headers are open.
>> Turning off bidi solve problem:
>
> Please show me an example of a file where it is "impossible to use"
> scrolling. Also, please tell which scrolling commands you used, and
> make sure this problem exists in "emacs -Q". I will then look into
> this. You can file a bug report if you wish.
This happen in emacs -Q too.
All scrolling commands, but also next/previous-line are affected.
Unfortunately i have no example file to send. My org files are quite big
and contain personal notes and infos.
> Thanks.
>
> (I do use Org mode, and I have a huge Org file, and I cannot say that
> scrolling there is impossible to use, even on my 6-year old hardware.
> But perhaps your Org files have something special in them that
> triggers this problem.)
Perhaps, do you have things like
#+BEGIN_SRC lisp
;; some lisp code here
#+END_SRC
in your org files?
--
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2011-08-16 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 19:48 window-scroll-functions and performance Antoine Levitt
2011-08-15 20:28 ` Eli Zaretskii
2011-08-15 21:02 ` Antoine Levitt
2011-08-16 5:56 ` Thierry Volpiatto
2011-08-16 6:38 ` Eli Zaretskii
2011-08-16 8:03 ` Thierry Volpiatto [this message]
2011-08-16 9:12 ` Eli Zaretskii
2011-08-16 6:49 ` 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=87wred236t.fsf@gmail.com \
--to=thierry.volpiatto@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).