From: Jean Louis <bugs@gnu.support>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
Emanuel Berg <moasenwood@zoho.eu>
Subject: Re: Ideas on Hypertext systems in Emacs needed
Date: Tue, 8 Jun 2021 10:08:35 +0300 [thread overview]
Message-ID: <YL8Xc7lEGQB+1P7t@protected.localdomain> (raw)
In-Reply-To: <CADs++6h8foepXiTFA3z7+5xUDCB+-JvcStfVzE9ddoXj5GEPAA@mail.gmail.com>
* Eduardo Ochs <eduardoochs@gmail.com> [2021-06-08 03:43]:
> English is not my first language, but to me "use whatever everyone
> else is using" seems to imply "don't use niche tools that are used by
> small groups of very enthusiastic hackers that love them very much".
>
> I have the impression that Jean Louis is looking for things that are
> nice to use AND to hack.
WWW is good informational hypertext system though it is passive, it is
not dynamic. Users can see information, cannot build upon it (unless
allowed like in Wikipedia).
GNU Hyperbole and eev, Org, HTML, Texinfo are hypertext systems if
text is created with it. They are not as integrated.
Major facility that I need in each of those in Emacs is recognition or
indexing of available hyperlinks in a document and relational
hyperlink inserting:
- indexing of available hyperlinks in documents would mean to captures
and record relations between the document and the hyperlink. That
would require system of regular expression harvesting of all
hyperlinks in a document so that such can be listed in separate
piece of information. As this quickly separates the referenced links
and provide ability for bidirectional link. A referenced document
can know other documents referencing to it. Indexing functions would
solve the proble that such information is not available. In similar
way WWW search engines ind
- Relational hyperlink inserting would keep track of hyperlinks at
moment they are inserted. Because of the nature of systems we have
that requires users' attention. Would we build from beginning
structural lists of available hyperlinks that would not need users'
attention. Practically it would or should be "hooked" so that when
user wish to insert a hyperlink the facility must be there to first:
verify that hyperlink is indexed beforehand, and to remember that
hyperlink is inserted into which document. Document A would have
hyperlink to document B, but document B would know that document A
has a hyperlink to it. Jumping from A to B is possible as usual, but
jumping from B to A would be enabled as well.
--
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:[~2021-06-08 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 17:15 Ideas on Hypertext systems in Emacs needed Jean Louis
2021-06-07 23:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-08 0:31 ` Eduardo Ochs
2021-06-08 1:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-08 7:17 ` Jean Louis
2021-06-08 7:08 ` Jean Louis [this message]
2021-06-08 5:59 ` Jean Louis
2021-08-30 9:37 ` Ihor Radchenko
2021-09-02 17:39 ` 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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YL8Xc7lEGQB+1P7t@protected.localdomain \
--to=bugs@gnu.support \
--cc=eduardoochs@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.
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).