From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id bVOUFJr7tV90fgAA0tVLHw (envelope-from ) for ; Thu, 19 Nov 2020 04:59:06 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id OLLiD5r7tV/KDQAA1q6Kng (envelope-from ) for ; Thu, 19 Nov 2020 04:59:06 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id A175B9402A7 for ; Thu, 19 Nov 2020 04:59:05 +0000 (UTC) Received: from localhost ([::1]:44022 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kfc2C-0001mb-Jp for larch@yhetil.org; Wed, 18 Nov 2020 23:59:04 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:53800) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfc1g-0001l4-EQ for emacs-orgmode@gnu.org; Wed, 18 Nov 2020 23:58:32 -0500 Received: from mail-pl1-x62c.google.com ([2607:f8b0:4864:20::62c]:39210) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kfc1e-0003zL-Iw for emacs-orgmode@gnu.org; Wed, 18 Nov 2020 23:58:32 -0500 Received: by mail-pl1-x62c.google.com with SMTP id y22so2289952plr.6 for ; Wed, 18 Nov 2020 20:58:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:subject:in-reply-to:message-id:date :mime-version; bh=roEWRNCG6hPXjMAKITJxxKZqSlcp7cjXQQy6jS5w2bw=; b=gP55STIRgAJ5i7k89PBA5DjXOiKpZek0QQAEaLSPzUmXE7r26wj1/sMAG3EhZntKv0 UZzufpKGo936v4H1sIu6hbiA0YH6e0dAY9mlSh/wDanY+CdSSn1yD6oBlpTqcjpzrQn7 q9b1ALcxyH1NarwXIMzHo+OwtBY3578SB01TaM8bUhfrtnslthRTORajhf0G15RE36Sh aC9U7argS8JGrmw8EMv9BH9WduA0g2dSRRS4Vo/ZENESW2svxPEzsH9AGHDs+W2ybfb9 lafJxndX8xjsyrwqe7MYc9fEriiSa0/2DJW4WbqKfpMH+7yeju5hYWeXueOD4Nhdg94n BuKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:subject :in-reply-to:message-id:date:mime-version; bh=roEWRNCG6hPXjMAKITJxxKZqSlcp7cjXQQy6jS5w2bw=; b=byhhHyZH4edi+qg0ovfNO+7h123FfP61P22E4JfyjA4BbvC/eK/S+lYiDbiNlWuMLz uevp+Y2GE1Sgb2320Y9ULF7JQhcppIKejKpUZ/Ee/8NIqOf2wHDRY5L27iPaay8f/BbS mxc99LwaDstt9hbPi2yuc1PorY3x6h3AK4xbziT6Rut+2Dy17IOtpQuh66zKeSBReuSN gRhbbc5UCTeWukjZgEMtM0cszwB7VHfdVxoAZh+JUHTh5rbLeoQskr8xgLde/G/gRbZS kcfEkLgzIRce8TFKDmN2EBrPW26Ln02eg++cj27/QqzO7+qaBe5VNq15XrMVauKNcdJV pc8Q== X-Gm-Message-State: AOAM530CfKoo3X9HucX/4twJmygOojZWUzwV1B4OO+Va2JgK8smaJZ+6 W5L7AOC2n0aVHSc9enEP4MUcpX7do8kFvg== X-Google-Smtp-Source: ABdhPJwgjAyd8Jn6SbLAZcDwr6WjhhhKa3YtY8WSyy3oqQSYBM4ITbsnqEMGYwSKd3kp58uPMejfhg== X-Received: by 2002:a17:902:eb4b:b029:d6:a26a:17ba with SMTP id i11-20020a170902eb4bb02900d6a26a17bamr7575988pli.16.1605761908393; Wed, 18 Nov 2020 20:58:28 -0800 (PST) Received: from tim-desktop (106-69-105-159.dyn.iinet.net.au. [106.69.105.159]) by smtp.gmail.com with ESMTPSA id f6sm22115431pgi.70.2020.11.18.20.58.26 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 Nov 2020 20:58:27 -0800 (PST) References: <87sgpow94z.fsf@nicolasgoaziou.fr> User-agent: mu4e 1.5.7; emacs 27.1.50 From: Tim Cross To: emacs-orgmode@gnu.org Subject: Re: [bug] Export to latex truncates long subsections (WE attached) In-reply-to: Message-ID: <87sg96ymbz.fsf@gmail.com> Date: Thu, 19 Nov 2020 15:58:24 +1100 MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::62c; envelope-from=theophilusx@gmail.com; helo=mail-pl1-x62c.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=gP55STIR; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.71 X-TUID: j0FWfDZA+p/b Vladimir Nikishkin writes: > So what is the status of this story? > > I believe that if one exports an org file with sufficiently many empty > TODO headings (to me, it seems a perfectly valid use case of org, > printing lists of TODOs), they won't fit on a single page, and latex > will drop them. Would the latex snippet in this thread be a good > candidate for inclusion into org as a canned trick? > > On Tue, 27 Aug 2019 at 14:57, Vladimir Nikishkin wrote: >> >> I have indeed investigated the issue, and this is the link: >> https://latex.org/forum/viewtopic.php?f=47&t=32788 >> >> To make the long story short, the folowing trick is needed to allow >> page breaks after headings (which is a completely standard case in >> -org). >> >> #+begin_src latex >> \usepackage{xpatch} >> \makeatletter >> % This is not recommended, because it can break several things >> \xpatchcmd{\@afterheading}{\@nobreaktrue}{\@nobreakfalse}{% >> \typeout{WARNING: \string\@afterheading\space broken}% >> }{% >> \@latexerr{ERROR: Cannot patch \string\@afterheading}\@ehd% >> } >> \makeatother >> #+end_src >> >> Shall this trick be considered for inclusion in 'org' officially? >> I mean, having lists of empty headings is a perfectly standard use case for org. >> What are the implications of doing this? In particular, the comment >> % This is not recommended, because it can break several things Many people have quite complex environments for generating Latex and we would need to be certain that adding this package doesn't 'break several things'. At the very least, something should probably be put on worg so that anyone who is running into the page breaking issue can add the snippet using file header lines. -- Tim Cross