emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Ihor Radchenko <yantar92@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: Mon, 7 Feb 2022 16:27:46 -0300	[thread overview]
Message-ID: <CADs++6gAPiT06OgF6eLZcYxpkZmEywara1kN+q-DxDoP2JgBTA@mail.gmail.com> (raw)
In-Reply-To: <87leym3hg1.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]

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.
> Best,
> Ihor

 Hi Ihor,

What do you mean by "you cannot"?
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'...

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.

Frustrated cheers =(,
  Eduardo Ochs

[-- Attachment #2: Type: text/html, Size: 1936 bytes --]

  reply	other threads:[~2022-02-07 19:29 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 [this message]
2022-02-08 13:40     ` Ihor Radchenko

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=CADs++6gAPiT06OgF6eLZcYxpkZmEywara1kN+q-DxDoP2JgBTA@mail.gmail.com \
    --to=eduardoochs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* 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).