From: Jean Louis <bugs@gnu.support>
To: emacs-orgmode@gnu.org
Subject: Re: Org, Hyperbole, and eev
Date: Thu, 29 Sep 2022 09:42:59 +0000 [thread overview]
Message-ID: <272F7335-6432-400D-BFA3-44BB81F31645@gnu.support> (raw)
In-Reply-To: <CADs++6hMf-iLfTCk79wQRaNE4FkweF9wUj0W=+VEe8zWWh-WuA@mail.gmail.com>
On September 28, 2022 10:15:06 AM UTC, Eduardo Ochs <eduardoochs@gmail.com> wrote:
>> I would like to have non-Org links so that my function for links
>> interpolates into a button. It works now in the presentation mode. I
>> would like to make links descriptive or non descriptive just as in
>> Org, so that it works in editing mode.
>
>You're hiding the technical details, and I don't know how to think in
>these terms, sorry! =(
Not hiding at all. If I would know technical details I would not need it. I have you examples with your links and wrapping then with name for link.
>For me your "non-Org link" is a string composed of a few substrings
>concatenated, and each of these substrings is either without text
>properties or is built using "propertize" or "buttonize". In this
>message
I don't think that way, that would make links specific just as they are specific in Org mode.
To make links not specific, but to liberate then from any mode, one would need to forget how link looks like inside some brackets and leave it to whatever function to interpolate itself into a button or anything else.
Did you try my interpolation package? It can already do that. But how can I read from properties and get back what was the link before? That is what I don't know how. And my way of doing links it is totally out of any frame I have seen before.
https://lists.gnu.org/archive/html/emacs-orgmode/2022-09/msg00725.html
There shall be no parsing of the link as that would make the link specific again.
If we make generic package than anybody else later will benefit. Generic links package is not tied to how link looks like, not tied to any function.
On the link above I my example.
Imagine (ln "name" (eev-funct do)) that would Interpolate to "name", but also {{{ name link }}} to to interpolate to something, and what does interpolation should be left to programmer.
Imagine having X+ of documents, and your link name is "New Yrk" mistakenly, by using generic approach one can keep the name outside of the document, correct it and in all documents it get corrected upon invocation or opening of it.
I use that system to inject my contact details, no matter if contact details change, I need not correct theđ one by one.
>I am trying to factor your problem into several small functions in a
>way that makes each of these small functions easy to test - with
>one-liners if possible, like I do in the eev source code - and if we
>do that factoring then the function that builds the "string composed
>of a few substrings concatenated" that I mentioned above will not call
>your rcd-template-eval and will not depend on the major mode...
I don't think that parsing strings make it generic.
Template Interpolation system makes it generic.
What has to be solved is how to insert the button so that it may be reversed into what it was before.
>I have the impression that the hard part _now_ is to write that
>function that produces that string with text properties.
I have used insert button function.
> Once we have
>that we will have a clearer notion of what are the "non-Org links"
>that we are dealing with, and it will be easier to think on the other
>functions.
Those generic links can as well become Org like links as there is no limitations.
Jean
next prev parent reply other threads:[~2022-09-29 9:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 15:56 Org, Hyperbole, and eev Eduardo Ochs
2022-06-26 16:28 ` Robert Weiner
2022-06-26 17:51 ` Eduardo Ochs
2022-06-26 18:23 ` Robert Weiner
2022-06-26 19:45 ` Eduardo Ochs
2022-06-26 20:23 ` Robert Weiner
2022-06-26 23:25 ` Eduardo Ochs
2022-06-27 0:49 ` Robert Weiner
2022-06-27 3:48 ` Eduardo Ochs
2022-06-27 4:11 ` Robert Weiner
2022-06-28 4:43 ` Eduardo Ochs
2022-09-27 15:10 ` Jean Louis
2022-09-27 16:22 ` Eduardo Ochs
2022-09-27 21:16 ` Jean Louis
2022-09-27 21:58 ` Jean Louis
2022-09-28 0:52 ` Eduardo Ochs
2022-09-28 6:04 ` Jean Louis
2022-09-28 10:15 ` Eduardo Ochs
2022-09-29 9:22 ` Jean Louis
2022-10-08 0:28 ` Eduardo Ochs
2022-10-08 1:25 ` Jean Louis
2022-10-11 2:42 ` Robert Weiner
2022-10-11 4:59 ` Jean Louis
2022-09-29 9:42 ` Jean Louis [this message]
2022-09-29 11:55 ` Quiliro Ordóñez
2022-09-28 3:52 ` Ihor Radchenko
2022-09-28 9:16 ` Jean Louis
2022-09-29 4:07 ` Ihor Radchenko
2022-09-29 9:59 ` Jean Louis
2022-06-28 4:48 ` Eduardo Ochs
2022-06-28 6:26 ` Robert Weiner
2022-09-27 14:43 ` Jean Louis
2022-09-27 14:16 ` 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=272F7335-6432-400D-BFA3-44BB81F31645@gnu.support \
--to=bugs@gnu.support \
--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).