Using org-mode version 7.93f, when exporting to ASCII it doesn't respect the current fill column. Can this be enforced? 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?
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? > Miguel, 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. HTH, Chuck
Charles,
Thanks very much for the tips -- they certainly helped!
Miguel
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?
>>
>
> Miguel,
>
> 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.
>
> HTH,
>
> Chuck
>
>
>
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 entire paragraphs. On 5/1/14, Miguel Guedes <miguel.a.guedes@gmail.com> wrote: > Charles, > > Thanks very much for the tips -- they certainly helped! > > Miguel > > > 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? >>> >> >> Miguel, >> >> 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. >> >> HTH, >> >> Chuck >> >> >> > > > > -- 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.