emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: David Maus <dmaus@ictsoc.de>
Cc: Bastien <bzg@altern.org>, emacs-orgmode@gnu.org
Subject: Re: Re: bug: invalid export key in export visible region
Date: Mon, 14 Mar 2011 23:01:00 -0700	[thread overview]
Message-ID: <AANLkTimcH+a9y51sV1VUHtPnVUXtkDyKd1ac=R_aCrVH@mail.gmail.com> (raw)
In-Reply-To: <87lj0h3qwm.wl%dmaus@ictsoc.de>

Hi David,

Right now all of the export commands that I use are broken.

My needs are visible region to HTML, ASCII region, ASCII subtree, HTML
region, and HTML subtree.  All not to file but to temporary buffer.  I
never export a whole file.  I have the variable set, but it does not
seem to work for ASCII.  Ideally, there would be a command for each
backend that would export to region-or-subtree depending on whether
the region is active.  Having issues with export of <<...>> in
headlines.  Etc.

I can't make proper bug reports now.

The visible region to HTML is the least important.  I wanted to use it
to work around the fact that there is no way to insert TOC in HTML
region-or-subtree export.  So I wanted to fold with text hidden, then
run that command.  I don't think that is emulable with simple region
export, if I understand your meaning correctly.

It's OK, however, to just use keep-lines or something, so it's not important.

Again, the various issues with ASCII and HTML export are more
important, but I can't make bug reports on those now.


AIDS 2.0 is here now:
I support the Whittemore-Peterson Institute (WPI)
I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MRV paper.

      reply	other threads:[~2011-03-15  6:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 18:17 bug: invalid export key in export visible region Samuel Wales
2011-03-06 18:09 ` David Maus
2011-03-06 18:34   ` Bastien
2011-03-14  3:11     ` Samuel Wales
2011-03-15  5:15       ` David Maus
2011-03-15  6:01         ` Samuel Wales [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='AANLkTimcH+a9y51sV1VUHtPnVUXtkDyKd1ac=R_aCrVH@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=bzg@altern.org \
    --cc=dmaus@ictsoc.de \
    --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).