Dear Sebastian,

I think your mail and my last one were sent almost at the same time. 

You are right about the limitations of org-id-update-id-locations. My last point about fixing .org-id-locations is that this is not feasible if you are working in a team (syncing via a code repository) on several loosely coupled org files that constitute parts of a web site: keeping .org-id-locations up-to-date is just too complex in that case (and this is not such an excentric scenario).

To make org ids more robust, I suggested to: 

> - expand the use of ids, so that, in analogy to other links, the inserted link can also contain a file name if it refers to another org file, maybe like this: 
> file-id:some-file.org#8329AEF0-4885-486A-A1B6-BB82B3E9218


Most of the time, this would work (provided one uses relativ path names).

Warm regards,
 Stefan


On 18.08.2010, at 23:55, Sebastian Rose wrote:

> Bernt Hansen <bernt@norang.ca> writes:
>> I think you can just regenerate the file with a call to
>> 
>> M-x org-id-update-id-locations
> 
> 
> This works for agenda files only, as well as files mentioned in
> the variable `org-id-locations'.
> 
> Thus you need to rename the element in the list in your id-locations
> file. E.G.:
> 
> Change ~/.emacs.d/.org-id-locations:
> (("~/emacs/org/notes/index.org" "org:1234...") ...
> 
> sh$ mv ~/emacs/org/notes/index.org ~/emacs/org/notes/Linux/index.org
> 
> 
> Change ~/.emacs.d/.org-id-locations accordingly:
> 
> (("~/emacs/org/notes/Linux/index.org" "org:1234...") ...
> 
> 
> 
> Shouldn't we have a command `org-move-file' or `org-rename-file' that takes
> care of id-locations?
> 
> 
> 
> Best wishes
> 
>   Sebastian

-- 
Dr. Stefan Vollmar, Dipl.-Phys.
Head of IT group
Max-Planck-Institut für neurologische Forschung
Gleuelerstr. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213  FAX +49-221-4726-298
Tel.: +49-221-478-5713  Mobile: 0160-93874279
Email: vollmar@nf.mpg.de   http://www.nf.mpg.de