all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Emanuel Berg <moasenwood@zoho.eu>,
	help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Ideas on Hypertext systems in Emacs needed
Date: Mon, 7 Jun 2021 21:31:01 -0300	[thread overview]
Message-ID: <CADs++6h8foepXiTFA3z7+5xUDCB+-JvcStfVzE9ddoXj5GEPAA@mail.gmail.com> (raw)
In-Reply-To: <87lf7lxmpg.fsf@zoho.eu>

On Mon, 7 Jun 2021 at 20:46, Emanuel Berg via Users list for the GNU
Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Jean Louis wrote:
>
> > - The HTML and eww Hypertext is not an option for me, that
> >   could be only good for reporting, but not for dynamically
> >   bound list of functions to specific hyperlinks; One same
> >   link on my side can provide different target depending of
> >   the key or function invoked.
>
> The web has been the king for decades, as for dynamic web
> there are tons of mature, established technologies, e.g.
> PHP (personal home page), Ajax, CGI (Central Gateway
> interface, for example C and MySQL) for old-schoolers,
> JavaScript (has nowadays similarities with Lisp even I've
> heard, isn't the once "shabby-construction web scripting
> language with a C++ syntax" people liked to ridicule), as for
> pure programming Python has faster devel and more resources
> than Perl, you are already familiar with the seekwells, the
> once USENET architecture of distribute-to-many (called
> propagate) is having a renaissance with Mastodon and is there
> called "a federation" (to contrast with P2P which is
> peer-to-peer, but also client-server which is a 1:1
> relationship), you can do whatever with the web, except for
> Gopher maybe. Don't pick some arcane markup which no one else
> uses, use whatever everyone else is using only use it better,
> otherwise you'll become a desert-penguin pretty fast... try
> the Tamagotchi for emotional support.
>
> --
> underground experts united
> https://dataswamp.org/~incal


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.

  [[]], E.
    http://angg.twu.net/#eev
    http://angg.twu.net/LATEX/2019emacsconf.pdf#page=10



  reply	other threads:[~2021-06-08  0:31 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADs++6h8foepXiTFA3z7+5xUDCB+-JvcStfVzE9ddoXj5GEPAA@mail.gmail.com \
    --to=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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.