emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: generic page breaks for export?
Date: Mon, 08 Apr 2013 00:45:25 +0800	[thread overview]
Message-ID: <87ip3ywaqi.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87txniy45q.fsf@gmail.com

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> It seems like enough of org's export formats have the concept of page
>> breaks that a generic syntax might be warranted -- I'm finding myself
>> doing lots of exporting to multiple formats. What do people think of
>> that? Emacs already has a convention of using ascii 12 as a page
>> delimiter (though control characters in the buffer look ugly), or we
>> could introduce something like #+PAGEBREAK, or perhaps both.
>> If this seems desirable, I'll take a stab at a patch.
> Thank you for the offer. Though, I don't think it's worth implementing
> it.
> For navigation, Org has better tools than page break jumping. So, it
> would only be related to export. Even in that case, adding a keyword
> (#+PAGEBREAK, but that would be some irregular syntax since there's no
> value attached) for such a simple thing is hardly a benefit:
>   #+latex: \newline
> Sure, when exporting to multiple formats, it can save a line or two.
> Nothing earth-shaking here.

Fair enough: you're right it's only good for export, and even then only
really useful for multiple formats. On the other hand, the ^L character
is just sitting there, begging to be handled...

      reply	other threads:[~2013-04-07 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07  2:47 generic page breaks for export? Eric Abrahamsen
2013-04-07 11:24 ` Nicolas Goaziou
2013-04-07 16:45   ` Eric Abrahamsen [this message]

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:

  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=87ip3ywaqi.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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).