From: Ihor Radchenko <yantar92@gmail.com>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Org for non-users, part 2: `C-c C-e', a.k.a. `org-export-dispatch'
Date: Tue, 08 Feb 2022 21:40:06 +0800 [thread overview]
Message-ID: <87zgn1sci1.fsf@localhost> (raw)
In-Reply-To: <CADs++6gAPiT06OgF6eLZcYxpkZmEywara1kN+q-DxDoP2JgBTA@mail.gmail.com>
Eduardo Ochs <eduardoochs@gmail.com> writes:
> On Mon, 7 Feb 2022 at 10:55, Ihor Radchenko <yantar92@gmail.com> wrote:
>
>> > What are the recommended ways to abort org-export-dispatch without
>> > letting it destroy the "*Org Export Dispatcher*" window and its
>> > buffer?
>>
>> You cannot. That window acts similarly to transient, but simpler. You
>> can think of *Org Export Disipatcher* as an extended help for
>> read-char-exclusive.
> What do you mean by "you cannot"?
Sorry if I was not clear. I was answering specifically the question you
asking. Elaborating: you cannot abort org-export-dispatch without
letting it destroy the "*Org Export Dispatcher*" buffer. This is because
"*Org Export Dispatcher*" is created inside unwind-protect form like:
(unwind-protect
<call to org-export--dispatch-ui that creates the buffer and
reads user input directly intercepting Emacs even loop via
read-char-exclusive>
(and (get-buffer "*Org Export Dispatcher*")
(kill-buffer "*Org Export Dispatcher*")))
Any time you abort org-export-dispatch, the unwind-protect is going to
kill the buffer.
> I was expecting an answer like this:
>
> That's difficult to do, but the temporary buffer is generated by the
> function `org-foo-bar'... you can try to make a copy of
> `org-foo-bar' called `org-foo-bar-hacked-version', add your own
> debugging functions to that copy - suggestion: the lines 42 and 99
> are good places for that - and then you can change the function
> `org-plic-ploc', that is called by `org-export-dispatch', to make it
> call `org-foo-bar-hacked-version' instead of `org-foo-bar'...
If your question is about debugging, feel free to M-x debug-on-entry
org-export--dispatch-action. That will suspend execution of
org-export--dispatch-ui called by org-export-dispatch right after the
buffer is created but before Emacs even loop is blocked to read user
input. Reading the source code of org-export--dispatch-ui might also
help.
> One possible meaning of "you cannot" is:
>
> Org is NOT MEANT to be explored in that way, and this "is not meant
> to" is in a very strong sense. The last time that a person gave
> technical information of that kind in the mailing list was 4 or 5
> years ago, and we banished her from the community and excommunicated
> her. Her name shall not be mentioned.
In my reply, "you cannot" referred to you cannot because of technical
reasons, as I tried to explain above. You appear to interpret the
wording in a strongly negative sense. Note that I was not trying to attack
you in any way and I am always trying my best to follow GNU Kind
Communication Guidelines [1] in my emails. Also note that my wording
might not be ideal. Either because English is not my native language or
because I may misinterpret the message I am replying to.
[1] https://www.gnu.org/philosophy/kind-communication.html
Best,
Ihor
prev parent reply other threads:[~2022-02-08 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 19:35 Org for non-users, part 2: `C-c C-e', a.k.a. `org-export-dispatch' Eduardo Ochs
2022-02-07 14:00 ` Ihor Radchenko
2022-02-07 19:27 ` Eduardo Ochs
2022-02-08 13:40 ` Ihor Radchenko [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:
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=87zgn1sci1.fsf@localhost \
--to=yantar92@gmail.com \
--cc=eduardoochs@gmail.com \
--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).