unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: "[Video links:]" blocks
Date: Thu, 13 May 2021 00:06:46 -0300	[thread overview]
Message-ID: <CADs++6iQdjfeqrv4y5QPXq+5XYbJz646=BWgv=BtGu+PaMESgg@mail.gmail.com> (raw)

Hi list,

I've been experimenting with ways to use links to positions in videos
for some years, and I think that I finally found a syntax that is good
enough. Now the sandboxed tutorials of eev have lots of blocks like
this one:

[Video links:]
  (find-eevnavvideo "10:36" "if I type <f8> six times here")
  (find-eevnavvideo "10:50" "a shell running inside Emacs")
  (find-eev2019video "15:11" "Demo: the eepitch block (in red star lines)")
  (find-eev2019video "15:48" "Demo: eepitch on non-red star lines")
  (find-eev2019video "15:56" "Demo: eepitch in action")
  (find-eevtestblsvideo "2:33" "if I run f8 here I start a new Lua interpreter")

and they are htmlized in a nice way - see:

  http://angg.twu.net/eev-intros/find-eev-quick-intro.html#6

Also, I've made a video about this, at:

  http://angg.twu.net/2021-video-links.html
  http://angg.twu.net/eev-videos/2021-video-links.mp4
  http://www.youtube.com/watch?v=xQqWufQgzVY

I've tried to make everything as friendly as possible to people with
very short attention spans.

I think that some of these ideas can be ported to Org and Hyperbole.
I am not the right person to implement them, but if anyone would like
to chat about the details of the current implementation - that are
quite simple - or, more important, about what I felt that was ugly in
my other (20?) implementations of video links, please get in touch!

  Cheers,
    Eduardo Ochs
    http://angg.twu.net/#eev
    edrx at Freenode



                 reply	other threads:[~2021-05-13  3:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CADs++6iQdjfeqrv4y5QPXq+5XYbJz646=BWgv=BtGu+PaMESgg@mail.gmail.com' \
    --to=eduardoochs@gmail.com \
    --cc=emacs-devel@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.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).