From: Scott Otterson <scotto@u.washington.edu>
To: emacs-orgmode@gnu.org
Subject: fancier and less fancy export
Date: Mon, 08 May 2006 09:43:24 -0700 [thread overview]
Message-ID: <445F752C.20909@u.washington.edu> (raw)
My biggest use of org-mode export is spitting out simple ASCII lists
that I paste into emails. Even so, I have picky export enhancement
requests:
1.) Add org-export-visible-as-ascii: org-export-copy-visible creates a
new org file containing the visible text. The problem for me is that
it's still an org-file, with all the leading *'s, linking text and so
on. So, I'd like to clean it up by running org-export-as-ascii over the
export-visible file but
- this is an extra step
- when I try to do this, I get the error message:
Wrong type argument: stringp, nil
2.) Export with simple leading characters instead of section numbers.
Maybe there's already a way to do this, but I'd like to see an option
for exporting headlines with leading '*' ,'o', '-'' and so on, instead
of with long section numbers like 3.4.2.1. For html export, this could
be just the standard itemized list characters; for ascii, it could be
something similar. This could be done with a customization variable, a
prefix, or very long commands like org-export-visible-as-ascii-simple...
Also, a general question: There's been discussion of adapting muse-mode
so that org-mode can eventually make use of its many export
capabilities. At that same time, we've got very interesting xoxo
export capability and the nice new code written by David O'Toole. This
is great stuff but to a new user, these multiple and somewhat
overlapping choices are bound to be confusing. Will all this good code
eventually get merged into a unified org-mode exporting system?
Thanks,
Scott
next reply other threads:[~2006-05-08 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 16:43 Scott Otterson [this message]
2006-05-08 17:07 ` fancier and less fancy export Nic
2006-05-08 19:33 ` David O'Toole
2006-05-08 21:00 ` Carsten Dominik
2006-05-08 21:13 ` Nic
2006-05-12 7:57 ` Carsten Dominik
2006-05-12 17:08 ` Scott Otterson
2006-05-12 22:03 ` Carsten Dominik
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=445F752C.20909@u.washington.edu \
--to=scotto@u.washington.edu \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).