From: Samuel Wales <firstname.lastname@example.org>
To: Miguel Guedes <email@example.com>
Subject: Re: Export as ASCII whilst respecting current fill column
Date: Sun, 7 Dec 2014 14:33:06 -0700 [thread overview]
Message-ID: <CAJcAo8s4MVmAjNm+Zw1WKjME1T5ac3Xxa-uP-3oH0HkEuo9_eA@mail.gmail.com> (raw)
interesting that it worked for you. i am using 8.2.10 and ascii
export does not fill. it seems to wrap single lines but not fill
On 5/1/14, Miguel Guedes <firstname.lastname@example.org> wrote:
> Thanks very much for the tips -- they certainly helped!
> On 02/05/14 00:56, Charles Berry wrote:
>> Miguel Guedes <miguel.a.guedes <at> gmail.com> writes:
>>> Using org-mode version 7.93f, when exporting to ASCII it doesn't respect
>>> the current fill column. Can this be enforced?
>> Upgrade to current org-mode (version 8.2.6) before you do anything else.
>> Then modify `org-ascii-text-width' to suit your needs.
>> | org-ascii-text-width is a variable defined in `ox-ascii.el'.
>> | Its value is 72
>> | Automatically becomes buffer-local when set.
>> | Documentation:
>> | Maximum width of exported text.
>> | This number includes margin size, as set in
>> | `org-ascii-global-margin'.
>> | You can customize this variable.
>>> Also, I've noticed that org doesn't remove verbatim tags (=verbatim=)
>>> but removes BEGIN_EXAMPLE blocks and presumably other BEGIN_xxx blocks;
>>> is this by design?
>> Same deal - upgrade. Then =xyz= becomes `xyz' on export.
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. And
ANYBODY can get it.
Denmark: free Karina Hansen NOW.
prev parent reply other threads:[~2014-12-07 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 17:40 Export as ASCII whilst respecting current fill column Miguel Guedes
2014-05-01 23:56 ` Charles Berry
2014-05-02 3:00 ` Miguel Guedes
2014-12-07 21:33 ` Samuel Wales [this message]
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 \
* 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).