emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Hock <andhock@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Resolving links breaks workflow using org-narrow-to-subtree
Date: Thu, 29 Oct 2015 21:46:35 +0100	[thread overview]
Message-ID: <1446151595.12562.21.camel@gmail.com> (raw)

Hi,

I am using Org-mode version 8.3.2 (8.3.2-10-g00dacd-elpa) to organize
my lecture notes and export them to LaTeX.

The final PDF document is quite large (around 200 pages), so the
corresponding org-file has a decent size as well. To make editing
easier, I often narrow my org buffer down to the chapter I currently
work on with C-x n s (org-narrow-to-subtree).

When I want to quickly check what I've just written and to keep
compilation times down, I export just the currently visible part of the
buffer via C-c C-e l p.

Org-mode then checks if it can resolve all links in the visible part of
the buffer, which often fails, as the link target is in another
(hidden) part of the org-file. This breaks my workflow as I now can't
export my document.

The following minimal case exhibits the problem:

----

#+LATEX_CLASS: article

* Chapter 1
I'm not currently working on this chapter: <<target>>
* Chapter 2
I'm currently working on this chapter and narrow the buffer down to it
[[target]]

----

I'm open for suggestions on how I could change my workflow to work
around this.


Thanks,
Andreas Hock

             reply	other threads:[~2015-10-29 20:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 20:46 Andreas Hock [this message]
2015-11-04 11:39 ` Resolving links breaks workflow using org-narrow-to-subtree Aaron Ecay
2015-11-05  8:58   ` Nicolas Goaziou
2015-11-05 14:29     ` Aaron Ecay
2015-11-06 13:58       ` Andreas Hock

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=1446151595.12562.21.camel@gmail.com \
    --to=andhock@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).