From: Uwe Brauer <oub@mat.ucm.es>
To: 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 22:00:05 +0200 [thread overview]
Message-ID: <87pmk0njy2.fsf@mat.ucm.es> (raw)
In-Reply-To: 87czg06c9z.fsf@localhost
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
>>> "IR" == Ihor Radchenko <yantar92@gmail.com> writes:
> 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."
I think this is fine, at least for me. Not sure what others think.
--
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-05-26 20:01 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 [this message]
2022-05-26 23:08 ` Samuel Wales
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmk0njy2.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.