From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Export Org with Org concept -- Re: Problems with C-c C-e file.org,
Date: Tue, 3 Jan 2023 19:15:17 +0700 [thread overview]
Message-ID: <tp168m$71k$1@ciao.gmane.io> (raw)
In-Reply-To: <CADs++6im8cvXkfoPN-cV8KqYsMoz85WrEvzk1h=NHqeErpV6DQ@mail.gmail.com>
On 03/01/2023 17:01, Eduardo Ochs wrote:
>
> Can you send to me - here to the mailing list - a version of
> `org-export-dispatch', and also of other functions if needed, in which
> the parts that call `read-char-exclusive' are replaced by something
> non-blocking?
Eduardo, I am sorry, but from my opinion it is too much. Perhaps you are
just not realizing that resources of developers are rather limited.
Getting rid of `read-char-exclusive' in Org menus requires significant
amount of work. Nobody argues that it would be a great improvement, but
it is necessary to make changes that are not obvious at first glance. It
would lead to confusing behavior otherwise.
Jean might be happy with the posted mock-up. Unfortunately that code is
too far from been ready to be used for all users. E.g. it does not use
`org-export-registered-backends', not to mention that all menus in the
package should be consistent. It is OK to have a bunch of repetitive
code for a demo, but it can not be taken as is.
Ihor dedicates a lot of time for development and maintaining of Org.
Other developers are significantly less active last months. Often
authors of code are not participating in discussions because several
years have been passed since that time and they are busy with other
projects. So your questions may noticeable efforts from other persons
unfamiliar with some code to "read" it for you. Org code is not ideal,
but it is rarely too obscure. Nobody intentionally adds obstacles that
hamper readability. Sometimes it is necessary to make decisions not
realizing actual consequences just to move forward. If you need code
friendly for beginners then find a friend who can rewrite the code in
the style you like (of course, it should be maintainable as well).
At first I believed that on your own way you are just avoiding reading
comments and docstring in ox.el that are helpful to discover actual
functions in export backends that do the job. E.g. docstring of
`org-export-define-backend' and its usage in other files is rather
informative.
I am lost what is your actual needs after your request to rewrite the
export dispatcher for you.
After all, if you can not figure out which function is called by the
dispatcher, instrument for debugging some transcoder function and export
some file. You will get call stack.
Be realistic, time and experience are limited resources, not all code
deserves blog posts. Source code is a communication channel as well.
next prev parent reply other threads:[~2023-01-03 12:21 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 20:57 Problems with C-c C-e file.org andre duarte bueno
2022-12-18 14:55 ` Ihor Radchenko
2022-12-19 21:10 ` Export Org with Org concept -- Re: Problems with C-c C-e file.org, Jean Louis
2022-12-25 12:06 ` Ihor Radchenko
2022-12-25 15:43 ` Jean Louis
2022-12-26 10:04 ` Ihor Radchenko
2022-12-26 15:58 ` Jean Louis
2022-12-27 10:46 ` Ihor Radchenko
2022-12-31 1:08 ` Eduardo Ochs
2022-12-31 6:19 ` Jean Louis
2023-01-01 14:02 ` Ihor Radchenko
2023-01-02 5:58 ` Eduardo Ochs
2023-01-02 11:07 ` Jean Louis
2023-01-03 9:48 ` Ihor Radchenko
2023-01-03 10:01 ` Eduardo Ochs
2023-01-03 12:15 ` Max Nikulin [this message]
2023-01-03 12:36 ` Eduardo Ochs
2023-01-05 11:07 ` Ihor Radchenko
2023-01-05 14:41 ` Alain.Cochard
2023-01-05 15:00 ` Max Nikulin
2023-01-05 15:18 ` Alain.Cochard
2023-01-05 20:37 ` Eduardo Ochs
2023-01-05 18:50 ` Jean Louis
2023-01-05 15:43 ` Eduardo Ochs
2023-01-04 11:08 ` Jean Louis
2023-01-05 11:16 ` Ihor Radchenko
2023-01-05 19:19 ` Jean Louis
2023-01-06 3:51 ` Max Nikulin
2023-01-07 9:04 ` Ihor Radchenko
2023-01-07 18:34 ` Jean Louis
2023-01-07 19:12 ` Jean Louis
2023-01-12 15:43 ` Max Nikulin
2023-01-13 9:41 ` Ihor Radchenko
2023-01-04 18:03 ` Jean Louis
2023-01-05 11:17 ` Ihor Radchenko
2023-01-05 19:37 ` Jean Louis
2023-01-06 3:24 ` Max Nikulin
2023-01-07 20:07 ` Jean Louis
2023-01-08 16:42 ` Max Nikulin
2023-01-07 9:09 ` Ihor Radchenko
2023-01-04 17:51 ` Jean Louis
2023-01-04 16:53 ` Jean Louis
2022-12-20 16:56 ` Problems with C-c C-e file.org Jean Louis
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='tp168m$71k$1@ciao.gmane.io' \
--to=manikulin@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).