emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: refile too slow
Date: Thu, 5 Oct 2017 15:30:22 -0700	[thread overview]
Message-ID: <CAJcAo8tM=f_SnUVj4nXBi+vmnemvDTOR7B_3aoHq0s5iH98_2g@mail.gmail.com> (raw)
In-Reply-To: <87fuaxk63j.fsf@nicolasgoaziou.fr>

On 10/5/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> i think delete-dups is suspicious here.  is its only purpose to
>
> Why is delete-dups suspicious? Have you got a very large number of
> refile locations? If so, would it make sense to refine your target
> definitions?

already do that.  my fallback "get most things down to a reasonable
level" refile and refile goto were ok until recently.  then they
became untenably slow.  i can't refine it more without missing stuff
that i need.

> Its purpose, as its name suggests, is to remove duplicate refile
> locations you could get.

so only useful if i set the variable with duplicate stuff?

===

delete-dups seems suspicious but what do i know.  i wonder if
cl-delete-duplicates is more efficient.

(defun delete-dups (list)
  "Destructively remove `equal' duplicates from LIST.
Store the result in LIST and return it.  LIST must be a proper list.
Of several `equal' occurrences of an element in LIST, the first
one is kept."
  (let ((tail list))
    (while tail
      (setcdr tail (delete (car tail) (cdr tail)))
      (setq tail (cdr tail))))
  list)

  reply	other threads:[~2017-10-05 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJcAo8uE4_eTDPdticnkXuTk1nNDasPLYLPR=Tdp-_1UJJsABA@mail.gmail.com>
2017-09-30 23:59 ` refile too slow Samuel Wales
2017-10-05 14:43   ` Nicolas Goaziou
2017-10-05 22:30     ` Samuel Wales [this message]
2017-10-25  3:04       ` Samuel Wales

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJcAo8tM=f_SnUVj4nXBi+vmnemvDTOR7B_3aoHq0s5iH98_2g@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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/org-mode.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).