From: Samuel Wales <samologist@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Uwe Brauer <oub@mat.ucm.es>, William Denton <wtd@pobox.com>,
emacs-orgmode@gnu.org
Subject: Re: export regions of a org files to other formats (most likely only to a buffer).
Date: Thu, 26 May 2022 16:08:23 -0700 [thread overview]
Message-ID: <CAJcAo8sG1aNdaL3qXcSHMQqWejop6KN4NkE04T=kF8ebDBjBsQ@mail.gmail.com> (raw)
In-Reply-To: <87czg06c9z.fsf@localhost>
i would say that respecting narrowing is expected in emacs, as a kind
of pseudo-buffer bob/eob, so it would be surprising to find that it
might not be so in a part of org. lack of it should be mentioned, but
might be a bug.
On 5/25/22, Ihor Radchenko <yantar92@gmail.com> wrote:
> Uwe Brauer <oub@mat.ucm.es> writes:
>
>>> Could you please clarify which part of the function docstring was not
>>> clear?
>>
>> Well
>> | org-export-dispatch is an interactive compiled Lisp function in
>> | ‘ox.el’.
>> |
>> | (org-export-dispatch &optional ARG)
>> ...
>>
>> Does not mention, that a selected region gets exported.
>
> Fair enough.
> Ironically, it is not even wrong. Looking at the source code, respecting
> region is merely a convention coming from most of backends calling
> `org-export-as'.
>
> As one possibility, we can add something like the following to the
> docstring:
>
> "Usually, exporting respects current narrowing and active region, though
> individual export backends might not follow the convention. See
> `org-export-as' for more details."
>
> Alternatively, we can modify `org-export-define-backend' to change the
> docstring with links to individual backend exporters.
>
> Or we may modify the dispatcher menu to indicate active region. Though
> it is not guaranteed to be obeyed by the backends.
>
> Best,
> Ihor
>
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2022-05-26 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 14:35 export regions of a org files to other formats (most likely only to a buffer) Uwe Brauer
2022-05-25 15:19 ` William Denton
2022-05-25 15:36 ` Uwe Brauer
2022-05-26 2:32 ` Ihor Radchenko
2022-05-26 5:48 ` Uwe Brauer
2022-05-26 6:25 ` Ihor Radchenko
2022-05-26 20:00 ` Uwe Brauer
2022-05-26 23:08 ` Samuel Wales [this message]
2022-05-26 23:28 ` Samuel Wales
2022-05-27 4:26 ` Ihor Radchenko
2022-05-25 15:21 ` Kaushal Modi
2022-05-25 15:26 ` Eric S Fraga
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='CAJcAo8sG1aNdaL3qXcSHMQqWejop6KN4NkE04T=kF8ebDBjBsQ@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
--cc=wtd@pobox.com \
--cc=yantar92@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).