From: Eli Zaretskii <eliz@gnu.org>
To: Shuguang Sun <shuguang@gmail.com>
Cc: 29846@debbugs.gnu.org
Subject: bug#29846: scroll and fontify takes longer time for file in slow network
Date: Mon, 25 Dec 2017 18:48:18 +0200 [thread overview]
Message-ID: <83o9mmiwj1.fsf@gnu.org> (raw)
In-Reply-To: <CACspjXcHfxnxT3kxqdNajAw1qBg3gAVgzp07dib2vKscajQrng@mail.gmail.com> (message from Shuguang Sun on Mon, 25 Dec 2017 17:47:52 +0800)
> From: Shuguang Sun <shuguang@gmail.com>
> Date: Mon, 25 Dec 2017 17:47:52 +0800
>
> Backup, auto-save, and lockfiles has been disabled in .dir-locals
>
> ((nil
> (make-backup-files . nil)
> (create-lockfiles . nil)
> (auto-save-default . nil)
> (auto-save-timeout . 10000)
> ))
You've disabled file locking, but Emacs still checks whether some
other Emacs session locked the file. It does that as part of
restore-buffer-modified-p, which is called by JIT font-lock (because
fontification makes the buffer modified and JIT font-lock needs to
undo that after it fontifies a chunk of buffer). Checking whether a
file is locked entails calling unlock_file, which in turn calls
read_lock_data, which tries to open the lock file. I'm guessing that
this is slow on that remote volume of yours.
Maybe we should support a special value of create-lockfiles which
would mean don't create lockfiles and don't test fro lockfiles created
by other Emacs sessions.
next prev parent reply other threads:[~2017-12-25 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 6:03 bug#29846: scroll and fontify takes longer time for file in slow network Shuguang Sun
2017-12-25 9:47 ` Shuguang Sun
2017-12-25 12:28 ` Eli Zaretskii
2017-12-25 14:41 ` Shuguang Sun
2017-12-25 16:48 ` Eli Zaretskii [this message]
2017-12-26 1:04 ` Shuguang Sun
2017-12-27 20:49 ` Stefan Monnier
2017-12-28 16:21 ` Eli Zaretskii
2017-12-28 19:03 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o9mmiwj1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29846@debbugs.gnu.org \
--cc=shuguang@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.