From: Eli Zaretskii <eliz@gnu.org>
To: "Moore, Rider" <rmoore@cooley.com>
Cc: 67672@debbugs.gnu.org, schand@cooley.com
Subject: bug#67672: EMACS - Slow opening files
Date: Thu, 07 Dec 2023 20:01:32 +0200 [thread overview]
Message-ID: <83ttot28oz.fsf@gnu.org> (raw)
In-Reply-To: <CY8PR11MB7133A9A521A6D74703E8A993AE8BA@CY8PR11MB7133.namprd11.prod.outlook.com> (rmoore@cooley.com)
> From: "Moore, Rider" <rmoore@cooley.com>
> CC: "67672@debbugs.gnu.org" <67672@debbugs.gnu.org>
> Date: Thu, 7 Dec 2023 16:39:32 +0000
>
> The computer is offline at all times and the volume is mounted via truecrypt.
Then perhaps volumes mounted via truecrypt implement some file I/O
operations slowly? Can you start "M-x profiler-start" before opening
a file on such a volume, then "M-x profiler-report" after the file is
opened, and post the full expanded profile here?
next prev parent reply other threads:[~2023-12-07 18:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 22:43 bug#67672: EMACS - Slow opening files Chand, Suresh
2023-12-07 6:43 ` Eli Zaretskii
2023-12-07 16:39 ` Moore, Rider
2023-12-07 18:01 ` Eli Zaretskii [this message]
2023-12-07 18:16 ` Moore, Rider
2023-12-07 18:28 ` Eli Zaretskii
2023-12-08 21:41 ` Moore, Rider
2023-12-09 7:29 ` Eli Zaretskii
2023-12-11 17:16 ` Moore, Rider
2023-12-11 17:53 ` Eli Zaretskii
2023-12-12 15:52 ` Moore, Rider
2023-12-12 17:07 ` Eli Zaretskii
2023-12-12 17:57 ` Moore, Rider
2023-12-12 18:40 ` Eli Zaretskii
2023-12-12 19:06 ` Moore, Rider
2023-12-12 19:15 ` Eli Zaretskii
2023-12-12 19:33 ` Moore, Rider
2023-12-12 19:46 ` Eli Zaretskii
2023-12-12 19:58 ` Moore, Rider
2023-12-12 21:03 ` Ihor Radchenko
2023-12-12 21:18 ` Moore, Rider
2023-12-12 21:25 ` Ihor Radchenko
2023-12-12 21:25 ` Moore, Rider
2023-12-12 21:29 ` Moore, Rider
2023-12-12 21:43 ` Ihor Radchenko
2023-12-12 21:32 ` Ihor Radchenko
2023-12-12 21:38 ` Moore, Rider
2023-12-12 21:56 ` Ihor Radchenko
2023-12-13 11:49 ` Eli Zaretskii
2023-12-13 11:59 ` Dmitry Gutov
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=83ttot28oz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67672@debbugs.gnu.org \
--cc=rmoore@cooley.com \
--cc=schand@cooley.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.