From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id SNWCLTc1B2DrTwAA0tVLHw (envelope-from ) for ; Tue, 19 Jan 2021 19:38:31 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id yPhgKTc1B2B3UgAAbx9fmQ (envelope-from ) for ; Tue, 19 Jan 2021 19:38:31 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 527859402C8 for ; Tue, 19 Jan 2021 19:38:31 +0000 (UTC) Received: from localhost ([::1]:44320 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l1wpg-0004Aw-V0 for larch@yhetil.org; Tue, 19 Jan 2021 14:38:28 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:50558) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l1vsD-0004f1-6n for emacs-orgmode@gnu.org; Tue, 19 Jan 2021 13:37:01 -0500 Received: from mail-qt1-x82a.google.com ([2607:f8b0:4864:20::82a]:45304) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l1vs9-0001Ze-I3 for emacs-orgmode@gnu.org; Tue, 19 Jan 2021 13:37:00 -0500 Received: by mail-qt1-x82a.google.com with SMTP id d15so9009569qtw.12 for ; Tue, 19 Jan 2021 10:36:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version:content-transfer-encoding; bh=YY4w+OBNB5lgZ8ZDfl0tMuIIzQEB6qLuJnv5f2S1yqY=; b=ujjlgvP5CCRu4LWzobugvQfO5wUKqaNyqmstVDNI9iKYqRgG4FKlc3doB07UQUmxuz vVig3xSVZJ0WilTi/66m5BldcUn1myJYPvFC12nJ4xkSUJ7+Dfse8kvdA52a2oyxrg/6 wNAFaeKo20SiJuSz3W++YIezTlM/Uhzed5GGr1oUeVqBx69qJWgH6y5SYBXyWmcp5B5S r8HiQ9XJwSwzCtlmzAMpcQipgmtjlsXazxpAaAmfMyYivO95azoKUcqDCbegd3dLJVyM PGWH+xd4+vXGxVFBDqGyFu+3nfh/VubPCZR+vk/gQcAApZH/YSpvJp9t4g8Yi3KXsYUO BGSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version:content-transfer-encoding; bh=YY4w+OBNB5lgZ8ZDfl0tMuIIzQEB6qLuJnv5f2S1yqY=; b=pps2Zr8iJyJdpq4YHgzZKFEJhoN5evOg5rz4AE/S41wZ2TD+QhqgDd905/PBdpLB0c wBgFSH/+k9O5hY0vMrW/vWB4zITTbVgiG9iaQshUrU1IGeSqRA9E0M4x5IQ9k0vh1+kl K28EnIyH5swM1khOZitJty5M1Bry/kUYVF/LvhJ2ncmg8tmHEqMFYMUCp9GMLljLFGab Nxa9FuHPkWq06TeQjy3DJgqWSdM+Wu9rlkGLt0Vo2fWwKLJBU0Rl6Q2udEYXL4LFRWQC oPJ5Xwy2RLOIrnUHrV+8djUmIIZKMzOhWSo94mYFmgvM8Dj5QM4w3ytjwUkNBGJuxb9l 3pEA== X-Gm-Message-State: AOAM53189jhFUK5QzYdsHu/pkDYVPMvBcoNOQLki5gx3mCF5w/ogjG+I FSmrYY+S85N0uE4445Jj/3BxspIfsLA= X-Google-Smtp-Source: ABdhPJy7bP72LbRpuMJAgQq6CPu9igXV9Wj3LEsKJnr/vDeT5+psc7CH2SIB9OPFBI+kut0Ez9nK9g== X-Received: by 2002:aed:37a5:: with SMTP id j34mr5473261qtb.13.1611081415890; Tue, 19 Jan 2021 10:36:55 -0800 (PST) Received: from r1 ([190.239.232.181]) by smtp.gmail.com with ESMTPSA id a22sm13286585qkl.121.2021.01.19.10.36.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 19 Jan 2021 10:36:55 -0800 (PST) References: User-agent: mu4e 1.4.14; emacs 27.1 From: doltes To: arozbiz@gmail.com Subject: Re: How can I keep Org-id links from breaking when moving files? In-reply-to: Date: Tue, 19 Jan 2021 13:32:56 -0500 Message-ID: <87ft2wvktj.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::82a; envelope-from=doltes512@gmail.com; helo=mail-qt1-x82a.google.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -2.05 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=ujjlgvP5; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 527859402C8 X-Spam-Score: -2.05 X-Migadu-Scanner: scn0.migadu.com X-TUID: bSWYOZl1SWrc arozbiz@gmail.com writes: > This question is in the context of using Org-id UUIDs for linking between > files. If I understand correctly, Org-id knows where to look for UUIDs > (generated by org-id-get-create) by looking at the org-id-locations > variable. But what if I move an .org file that I've generated a UUID into > another folder? I know I can run org-id-update-id-locations, and there's = an > org-id-extra-files variable, but is there a way to list all the folders on > the system where Org-id should look for UUIDs? > > Thanks, > Alan After reading the docstring of the function =3Dorg-id-update-id-locations=3D, I found that the files which are scanned are defined by 6 variables. The following was retrieved from the docstring #+begin_quote This will scan all agenda files, all associated archives, and all files currently mentioned in =E2=80=98org-id-locations=E2=80=99. #+end_quote This implies that when that function is executed, the files whose content is searched for IDs (i.e. they are scanned) are + The files mentioned in =3Dorg-agenda-files=3D. + The archives associated to the files in =3Dorg-agenda-files=3D. + The files mentioned in =3Dorg-id-locations=3D. + The files provided as arguments to the =3Dorg-id-update-id-locations=3D. The following are not mentioned in the documentation of =3Dorg-id-update-id-locations=3D, but when looking at the source code, you can see that the value of the following variables is used + =3Dorg-id-extra-files=3D + =3Dorg-id-files=3D As we could see, the files which are scanned are defined by 6 variables. Now, apparently, you want to get a list of the files which are scanned. You can do that by executing what =3Dorg-id-update-id-locations=3D executes in order to get the list of files to scan. The following was retrieved from that function with some modifications #+begin_src elisp :results output (let ((files (delete-dups (mapcar #'file-truename (append (org-agenda-files t org-id-search-archives) (unless (symbolp org-id-extra-files) org-id-extra-files) org-id-files))))) (dolist (file files) (princ (format "%s\n" file)))) #+end_src #+RESULTS: #+begin_example /home/username/my/org/Statistics.org /home/username/my/org/Programming languages/Elisp.org /home/username/my/org/Programming languages/R.org #+end_example Hope that helps. Let me know if that answers your question.