James K. Lin writes:
> By default, Org mode does not work well with indirect buffers. You could get
> around this by rolling your own version of functions on your own to ignore
> the base buffer. This is no small feat because the link navigation commands
> are nested.
I understand... thanks for
Igor Sosa Mayor gmail.com> writes:
>
> James K. Lin yahoo.com> writes:
>
> > org-narrow-to-subtree creates a subtree buffer. Your org-return call within
> > that new subtree buffer command operates on the base buffer. Many of Org's
> > link navigation commands operate this way because they use
James K. Lin writes:
> org-narrow-to-subtree creates a subtree buffer. Your org-return call within
> that new subtree buffer command operates on the base buffer. Many of Org's
> link navigation commands operate this way because they use the base buffer
> as their context.
thanks for your answer.
Igor Sosa Mayor gmail.com> writes:
>
> Hi,
>
> maybe this is a small bug or something wrong in my config...
>
> But: if I use org-narrow-to-subtree and then use org-return to open a
> file link the narrowed function get lost and I get the whole buffer
> again. This happens at least if I get a
Hi,
maybe this is a small bug or something wrong in my config...
But: if I use org-narrow-to-subtree and then use org-return to open a
file link the narrowed function get lost and I get the whole buffer
again. This happens at least if I get a question because the file is too
big and I have to dec
