From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Hock Subject: Resolving links breaks workflow using org-narrow-to-subtree Date: Thu, 29 Oct 2015 21:46:35 +0100 Message-ID: <1446151595.12562.21.camel@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44501) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zru5r-0000iT-3G for emacs-orgmode@gnu.org; Thu, 29 Oct 2015 16:46:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zru5n-0001jp-26 for emacs-orgmode@gnu.org; Thu, 29 Oct 2015 16:46:42 -0400 Received: from mail-wi0-x229.google.com ([2a00:1450:400c:c05::229]:34070) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zru5m-0001jZ-Sp for emacs-orgmode@gnu.org; Thu, 29 Oct 2015 16:46:39 -0400 Received: by wikq8 with SMTP id q8so295439110wik.1 for ; Thu, 29 Oct 2015 13:46:38 -0700 (PDT) Received: from modulo ([2.173.54.1]) by smtp.gmail.com with ESMTPSA id gh9sm3569502wjb.27.2015.10.29.13.46.36 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Oct 2015 13:46:36 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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: <> * 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