From: Jean Louis <bugs@gnu.support>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Export Org with Org concept -- Re: Problems with C-c C-e file.org,
Date: Wed, 4 Jan 2023 14:08:44 +0300 [thread overview]
Message-ID: <Y7VePMOfM0hL+yZ1@protected.localdomain> (raw)
In-Reply-To: <tp168m$71k$1@ciao.gmane.io>
* Max Nikulin <manikulin@gmail.com> [2023-01-03 15:18]:
> 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.
Yeah, right, I have spent few hours to make
GNU Emacs package: rcd-org-export.el -- use Org to export Org:
2022-12-25 18:16:06.397296+03
https://gnu.support/gnu-emacs/packages/GNU-Emacs-package-rcd-org-export-el-use-Org-to-export-Org-76272.html
And from there I developed RCD Dashboard on
2022-12-25 17:44:11.336142+03
GNU Emacs package: rcd-dashboard.el -- Tool to build Emacs dashboards:
https://gnu.support/gnu-emacs/packages/GNU-Emacs-package-rcd-dashboard-el-Tool-to-build-Emacs-dashboards-76668.html
And now I have full set of dashboards with people being assigned to
tasks, plans, programs, projects, agenda, etc.
Because I can't agree to your statements, that is why I use the user
friendly Org mode based RCD Org Export Dashboard instead of standard
Org blocking, user-unfriendly one.
> 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.
Nothing is obvious when it is not obvious. I got it.
> Jean might be happy with the posted mock-up.
The posted mock-up is not any more mock-up but daily used dashboard to
export Org.
> Unfortunately that code is too far from been ready to be used for
> all users.
So how far? Like few hours?
> E.g. it does not use `org-export-registered-backends', not to
> mention that all menus in the package should be consistent.
I am aware of it, thanks.
Feel free to make it.
Do you really need it?
Though, we speak here of non-blicking Org Export, and there are many
ways to do it, we speak of decisions that are not user friendly, made
before more than 10 years.
There was enough time to use whatever one wish. I can't wait for
somebody in mainstream Org to make it user friendly, mouse clickable,
and so there is enough of it for you to adapt it to your own needs as
in main stream.
If you people wish.
If you look at the RCD Dashboard, then how "menus" should look like
may be left to user to decide. So far nobody uses my package that I
know, and in that case, I will not keep improving what is not so far
found as interesting for users.
It works for me so well. That is why I use it.
Feel free to bend your fingers with C-c C-e C-a C-f C-s, and I will
keep using the mouse device to export Org.
> It is OK to have a bunch of repetitive code for a demo, but it can
> not be taken as is.
You have not say that you like the functionality. Underlying
repetitive stuff is not important.
And I rather like that repetitive style than the Gordian knot of the
Org code.
> I am lost what is your actual needs after your request to rewrite
> the export dispatcher for you.
It can be rewritten in simple text, actually in Org mode alone it can
work. That is up to those who are interested.
Why develop something when there is no interest?
I guess it must be 5-6 years that I was talking about sharing headings
by e-mail, XMPP, SMS, etc. and since then I have received bunch of
dollars because of those features. None of it was implemented in Org,
because sharing is not part of it, or decisions, or developers
burdens, etc.
That is example of "why develop features when there is no interest for
it".
Good that Emacs is extensible by every user, otherwise it would be one
way road with Org.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-01-04 11:10 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
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 [this message]
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=Y7VePMOfM0hL+yZ1@protected.localdomain \
--to=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/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).