From: David Maus <dmaus@ictsoc.de>
To: Samuel Wales <samologist@gmail.com>
Cc: Bastien <bzg@altern.org>,
emacs-orgmode@gnu.org, David Maus <dmaus@ictsoc.de>
Subject: Re: Re: bug: invalid export key in export visible region
Date: Tue, 15 Mar 2011 06:15:53 +0100 [thread overview]
Message-ID: <87lj0h3qwm.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <AANLkTimJr_aCmpD2citpO8c0mfOds73SxS2=G92_GiQq@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
At Sun, 13 Mar 2011 20:11:03 -0700,
Samuel Wales wrote:
>
> On 2011-03-06, Bastien <bzg@altern.org> wrote:
> > David Maus <dmaus@ictsoc.de> writes:
> >> Samuel Wales wrote:
> >>> c-c c-e v H
> >>> c-c c-e v R
> >>>
> >>> Emacs 22, latest org git master.
> >>
> >> Thanks for the report, should be fixed by now.
>
> Thanks, David. Doesn't work for me.
>
I can at least confirm this problem: Limit to visible part of outline
tree and export regions as html does currently not work. Among all
functions that are accesible in `org-export-visible' export html as
region is the only one that (obviously) requires more than the
universal prefix argument to function properly.
I wonder: Does it make sense to combine 'limit to visible part' and
'export region as html'? If you've narrowed the outline and want to
export only a region, the regular export region function (C-c C-e R)
should do the job, shouldn't it? Because the boundaries of the region
are same.
Or am I missing a particular use case?
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2011-03-15 10:04 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 [this message]
2011-03-15 6:01 ` Samuel Wales
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=87lj0h3qwm.wl%dmaus@ictsoc.de \
--to=dmaus@ictsoc.de \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/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).