Hi John, On Sat, Oct 24, 2015 at 5:03 PM, John Kitchin <jkitc...@andrew.cmu.edu> wrote: > > Maybe I am missing something here. I would expect org-id-goto to actually > get to the id entry when it is used independent of narrowing. When used in a > program, I would expect this behavior to be wrapped in save-restriction type > macros, so it wouldn't change your restriction. But when used interactively, > e.g. when I click on a link, I expect the point to end up on the id entry, > with the buffer open in front of me, even if that means widening. Is there > some other expectation that makes sense? I feel like it is up to me to > decide if breaking the restriction is worth visiting the link, and only by > clicking on the link or running an interactive command makes that happen.
Thanks for spelling it out so clearly. I wasn't thinking clearly, before. I completely agree with you that the user should be the one deciding if its "worth breaking the restriction". Any calling code would be saving restriction, if that is the intent. +1 on simply widening the buffer, with an optional warning/error that can be turned on or off with a variable. -- Puneeth
