all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: JARZz <jarss@protonmail.com>
Cc: "emacs-orgmode\\\\@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: searching agenda from TRAMP
Date: Fri, 01 Oct 2021 19:26:08 +0800	[thread overview]
Message-ID: <874ka1dm0f.fsf@localhost> (raw)
In-Reply-To: <W9JoC2bJDD0NiZd4-OGAs9FNenWVqVlvHpn1EW1nFqyGlnYFXcXUAPlbXsnmRWGRbuUZnehhCy8q-2pp6QfCY88-zfnm_StCy1_ZupawV9U=@protonmail.com>

JARZz <jarss@protonmail.com> writes:

>> Does opening org files manually take a lot of time for you?
>>
>> Are you using org-id?
>>
>> Can you track down the problematic function using M-x profiler-start /
>
> These are good questions.
> I *do* use org-id. I started doing this more recently. I use a package called super-links. That could be a cause of it?

Can you temporarily set org-id-track-globally to nil and try whatever
commands is slow for you?

> I can run profiler-start but I'm not sure what I'm looking for. Everything works OK (as far as I can tell), it's only when I want to search something specific it takes forever and a half. But of course, I'll take the advise above and try to run clean Emacs, see what happens then.

As a generic advice, you can do profiler-start -> run the command that
you know is slow -> profiler-report -> post the report here.  Profiler
report can be as helpful as debugger backtrace when tracking down
performance issues.

Best,
Ihor


      reply	other threads:[~2021-10-01 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  2:56 searching agenda from TRAMP JARZz
2021-10-01  4:31 ` Adam Porter
2021-10-01  6:28 ` Ihor Radchenko
2021-10-01 10:50   ` JARZz
2021-10-01 11:26     ` Ihor Radchenko [this message]

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=874ka1dm0f.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jarss@protonmail.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.