|
From: | Max Nikulin |
Subject: | Re: Export Org with Org concept -- Re: Problems with C-c C-e file.org, |
Date: | Fri, 6 Jan 2023 10:24:45 +0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 |
On 06/01/2023 02:37, Jean Louis wrote:
* Ihor Radchenko [2023-01-05 14:17]:Could you please elaborate what is bad about the design and maybe provide some ideas how it can be improved?There was choice back in time, before 10 years, to provide to user few keys to run some functions, like Org export.
Sorry, but your response just repeats complains concerning blocking menu that you posted earlier many times. I do not see anything related to your original statement:
After looking into it, into `org-export-registered-backends', I will not use it, neither follow the chain of poor design.
Could you, please, concentrate on your vision of proper `org-export-registered-backends' design? Personally, I see no major issues, the approach is usual for enabling third-party plugins. From my point of view, the structure is organized well enough to allow alternative implementations of export menu. That is why I am surprised that such statement appeared in a topic dedicated to UI.
Do not repeat that blocking menu is not convenient enough sometimes. Say what should be used instead of `org-export-registered-backends'.
[Prev in Thread] | Current Thread | [Next in Thread] |