From: Ergus via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org
Subject: Slow redisplay
Date: Sun, 25 Aug 2019 12:32:51 +0200 [thread overview]
Message-ID: <20190825103251.osstrlohmzp6bmvr@Ergus> (raw)
Hi:
With the actual master branch I am observing a very important lagging in
redisplay after being using emacs for 3-4 of hours. The rediplay happens
like in stop motion speed, I can see the redisplay line being updated
slowly and it takes sometimes like 1 seconds (from the top to the bottom
of the screen) in my best laptop.
(I only use emacs in tui) So the only solution after a while is to close
emacs and reopen again.
I used to have these lines:
(defun my/minibuffer-setup-hook ()
(setq gc-cons-threshold most-positive-fixnum))
(defun my/minibuffer-exit-hook ()
(setq gc-cons-threshold 800000))
(add-hook 'minibuffer-setup-hook #'my/minibuffer-setup-hook)
(add-hook 'minibuffer-exit-hook #'my/minibuffer-exit-hook)
In my config, but after removing them (because someone suggested that
the redisplay lagging could be related with the gc) the problem is still
there (less critical, but still there after some hours).
Any suggestion to find where is the issue comming from? Or what should I
see to make a better report?
In-Reply-To: <20190824213001.GC17256@protected.rcdrun.com>
On Sat, Aug 24, 2019 at 11:30:01PM +0200, Jean Louis wrote:
>* Eli Zaretskii <eliz@gnu.org> [2019-08-24 21:04]:
>> > Date: Sat, 24 Aug 2019 20:50:46 +0200
>> > From: Jean Louis <bugs@gnu.support>
>> > Cc: help-gnu-emacs@gnu.org
>> >
>> > * Eli Zaretskii <eliz@gnu.org> [2019-08-24 20:26]:
>> > > > Date: Sat, 24 Aug 2019 19:37:11 +0200
>> > > > From: Jean Louis <bugs@gnu.support>
>> > > > Cc: GNU Emacs Help <help-gnu-emacs@gnu.org>
>> > > >
>> > > > - use simple editing of buffer with kill-buffer-hook, if I can come
>> > > > back to initial program execution, as program execution must be wait
>> > > > for editing to finish, I do not know how
>> > >
>> > > A command such as "M-x loop-continue" (possibly bound globally to some
>> > > key sequence) should be enough to resolve the "come back to initial
>> > > program execution" part.
>> >
>> > I do not have loop-continue, is it in some package?
>>
>> That's a command you need to write. It is supposed to go to the next
>> field and generate a buffer for the user to edit that field.
>
>I know what you mean. But command that handles next fields is in
>the depth 0, I just need to return to senior function, or find
>way how to wait on find-file
>
>Jean
>
next reply other threads:[~2019-08-25 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 10:32 Ergus via Users list for the GNU Emacs text editor [this message]
2019-08-25 11:10 ` Slow redisplay Eli Zaretskii
2019-08-26 4:20 ` Ergus
2019-08-26 7:42 ` 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=20190825103251.osstrlohmzp6bmvr@Ergus \
--to=help-gnu-emacs@gnu.org \
--cc=bugs@gnu.support \
--cc=spacibba@aol.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.
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).