Max Nikulin writes:
> On 07/01/2023 16:04, Ihor Radchenko wrote:
>>
>> As I said, the requirement to get it into the core is re-creating
>> previous layout and bindings. The layout and bindings may be
>> customizable, but they must be available.
>
> I would say, a layout that is not worse than
On 07/01/2023 16:04, Ihor Radchenko wrote:
As I said, the requirement to get it into the core is re-creating
previous layout and bindings. The layout and bindings may be
customizable, but they must be available.
I would say, a layout that is not worse than the current one. Org menus
may have
On 08/01/2023 03:07, Jean Louis wrote:
* Max Nikulin [2023-01-06 06:30]:
Could you, please, concentrate on your vision of proper
`org-export-registered-backends' design?
I leave that to Org developers. That variable is not described well,
neither mentioned in Org manual.
Org has user
* Max Nikulin [2023-01-06 06:30]:
> Could you, please, concentrate on your vision of proper
> `org-export-registered-backends' design?
I leave that to Org developers. That variable is not described well,
neither mentioned in Org manual.
I can only reiterate my point which you did not
* Ihor Radchenko [2023-01-07 12:04]:
> As I said, the requirement to get it into the core is re-creating
> previous layout and bindings. The layout and bindings may be
> customizable, but they must be available.
You have got the concept, you may implement it.
> > The Concept and More Ideas:
> >
* Ihor Radchenko [2023-01-07 12:04]:
> > The Concept and More Ideas:
> > ---
> >
> > 1. You can create derived mode, for example Org derived mode.
>
> This has pros and cons. Org derived mode means that personal
> customization, including key bindings and themes, may
Jean Louis writes:
> * 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?
>
> ...
> The ideas have been sent as concept to you, then as full package,
> which I now use daily, so it is to derive
Jean Louis writes:
>> I was hoping that you might be interested to provide a patch for Org
>> upstream.
>
> Question is: did you try it out?
>
> Once you try it out, then let me know to continue.
I did try it. I am in favour of the non-blocking menu. Other people
participating in this
On 06/01/2023 02:19, Jean Louis wrote:
The Concept and More Ideas:
---
Was there any messages with arguments that Org should stick to blocking
menu?
It is not about UI ideas, it is not about counting people who agrees
that menu should be non-blocking (I do not
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
On Thu, 5 Jan 2023 at 12:19, wrote:
>
> Max Nikulin writes on Thu 5 Jan 2023 22:00:
>
> > Sometimes I start emacs in a terminal application to copy some
> > "special" text (holding [Shift]).
>
> Great! It worked for the *Org Select* buffer.
>
> I did not know that trick.
Hi Alain,
here is
* alain.coch...@unistra.fr [2023-01-05 17:46]:
> Ihor Radchenko writes on Thu 5 Jan 2023 11:07:
>
> > However, I doubt that you can make much use of the buffer itself -
> > it is nothing but text.
>
> Without my suggesting that anything at all should be done, I am
> commenting that sometimes
* 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. That itself is not bad,
but
* Ihor Radchenko [2023-01-05 14:16]:
> Jean Louis writes:
>
> > 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
On Thu, 5 Jan 2023 at 08:06, Ihor Radchenko wrote:
>
> Eduardo Ochs writes:
>
> > sorry, I thought that that would be something like a 5-line change... =(
> >
> > A few messages again I mentioned that one of my plans for these holidays
> > was to learn several techniques for debugging elisp that
Max Nikulin writes on Thu 5 Jan 2023 22:00:
> Sometimes I start emacs in a terminal application to copy some
> "special" text (holding [Shift]).
Great! It worked for the *Org Select* buffer.
I did not know that trick.
Thanks.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE
On 05/01/2023 21:41, Alain.Cochard wrote:
I am
commenting that sometimes one might need that text, if only for
personal notes, and it would be convenient if one could access all
buffers just like we can for (say) the *Messages* buffer. For example,
I recently needed what is seen in the *Org
Ihor Radchenko writes on Thu 5 Jan 2023 11:07:
> However, I doubt that you can make much use of the buffer itself -
> it is nothing but text.
Without my suggesting that anything at all should be done, I am
commenting that sometimes one might need that text, if only for
personal notes, and it
Jean Louis writes:
> * Max Nikulin [2023-01-03 15:18]:
>> 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
Jean Louis writes:
> 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
Eduardo Ochs writes:
> sorry, I thought that that would be something like a 5-line change... =(
>
> A few messages again I mentioned that one of my plans for these holidays
> was to learn several techniques for debugging elisp that I've postponing
> learning for ages. I'll do that and then I'll
> 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?
There is no Org version of menu that does not block. That it is there
is
* Max Nikulin [2023-01-03 15:18]:
> 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
Pointers for you Eduardo:
(find-efunction 'org-export-dispatch)
(find-efunction 'org-export--dispatch-ui)
(progn (find-efunction 'org-export--dispatch-ui) (forward-line 48))
(progn (find-efunction 'org-export--dispatch-ui) (search-forward "Export
scope"))
(find-efunction
* Max Nikulin [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
On Tue, 3 Jan 2023, 09:23 Max Nikulin, wrote:
> 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
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
On Tue, 3 Jan 2023 at 06:47, Ihor Radchenko wrote:
>
> Eduardo Ochs writes:
>
> > (3) _is_ my experience with the Org mailing list.
> >
> > What I meant by "the developers like your questions" was roughly:
> > "recognizing that that person deserves help, and giving him tools that
> > would let
Eduardo Ochs writes:
> (3) _is_ my experience with the Org mailing list.
>
> What I meant by "the developers like your questions" was roughly:
> "recognizing that that person deserves help, and giving him tools that
> would let him solve his problems in hours instead of in months or
> years".
>
I was reading about Orgdown, Karl, please keep the name, and don't
mind the group.
* Eduardo Ochs [2023-01-02 09:01]:
> (3) _is_ my experience with the Org mailing list.
>
> What I meant by "the developers like your questions" was roughly:
> "recognizing that that person deserves help, and
On Sun, 1 Jan 2023 at 11:02, Ihor Radchenko wrote:
>
> Eduardo Ochs writes:
>
> > My conclusion was that Org is much harder to learn than I thought.
> > It's easy to learn if:
> >
> > 1) you're a "user", or
> > 2) you know a lot about debugging Emacs, or
> > 3) the developers like your
Eduardo Ochs writes:
> My conclusion was that Org is much harder to learn than I thought.
> It's easy to learn if:
>
> 1) you're a "user", or
> 2) you know a lot about debugging Emacs, or
> 3) the developers like your questions.
I hope that (3) is not your experience with Org ML. If it
* Eduardo Ochs [2022-12-31 04:11]:
> Hi Jean Louis,
>
> did you solve your problem? Did you find a way to replace the
> blocking code by something else?
Of course, for me personally, I have fully solved it, you can see
video here:
On Mon, 19 Dec 2022 at 18:13, Jean Louis wrote:
>
> * Ihor Radchenko [2022-12-18 17:57]:
> > andre duarte bueno writes:
> >
> > > When I try to export file.org using C-c C-e the window with the list of
> > > possibilities appears. But it appears incomplete(visualization), so I try
> > > to use
Jean Louis writes:
> If you mean formatting of the text, how it looks like, then retain
> formatting of text. That is choice. That is not part of the offered
> concept.
Yes, that's what I was referring to. I am not against non-blocking
interface per se.
> QUESTION: Should I now add the
* Ihor Radchenko [2022-12-26 13:05]:
> In any case, breaking the way existing menu works is not something we
> can do without proposing a fallback.
> https://bzg.fr/en/the-software-maintainers-pledge/
I have never said anything about "breaking the way existing menu
works".
The concept offered
Jean Louis writes:
>> > That is not first complaint, right? I would say it is obvious that
>> > such interface is not user friendly.
>>
>> Yes and no. Some users do not like it. Some users prefer the existing
>> one. Conclusion: even if we implement something better, it should be
>> backwards
* Ihor Radchenko [2022-12-25 15:07]:
> Jean Louis writes:
>
> >> > Apparently C-c C-e is capturing all events and not just keyboard
> >> > events!
> >
> > That is not first complaint, right? I would say it is obvious that
> > such interface is not user friendly.
>
> Yes and no. Some users do
Jean Louis writes:
>> > Apparently C-c C-e is capturing all events and not just keyboard
>> > events!
>
> That is not first complaint, right? I would say it is obvious that
> such interface is not user friendly.
Yes and no. Some users do not like it. Some users prefer the existing
one.
39 matches
Mail list logo
