From: Eduardo Ochs <eduardoochs@gmail.com>
To: Eduardo Ochs <eduardoochs@gmail.com>,
help-gnu-emacs <help-gnu-emacs@gnu.org>,
Jean Louis <bugs@gnu.support>
Subject: Re: Integrating eev and org-capture/org-capture-set-target-location
Date: Fri, 4 Jun 2021 13:09:10 -0300 [thread overview]
Message-ID: <CADs++6jrbUhDVCNwTXJNKwFivgnTcJTas+jebvFFWzzNou6Hpg@mail.gmail.com> (raw)
In-Reply-To: <YLnBk5cZS1rOFGoJ@protected.localdomain>
On Fri, 4 Jun 2021 at 03:02, Jean Louis <bugs@gnu.support> wrote:
>
> > (find-orgnode "Capture templates" "file+headline")
> > (find-orgnode "Template elements" "\ntarget")
>
> Those must be new eev functions.
Hi Jean-Louis,
`find-orgnode' is almost 20 years old, actually...
It is defined with `code-c-d', that is from 1995 (!!!) =P.
The idea is explained here:
(find-eev-quick-intro "9.1. `code-c-d'")
(find-eev-quick-intro "9.2. Extra arguments to `code-c-d'")
and here:
(find-eev2020video "8:20" "`code-c-d' defines several new functions")
(find-eev2020video "8:34" "the result is the name of one of the functions")
(find-eev2020video "8:45" "`find-orggitfile'")
(find-eev2020video "9:09" "prepends this string")
(find-eev2020video "9:40" "`find-orggitnode'")
(find-eev2020video "17:20" "find-code-c-d shows the code")
Are the sexp hyperlinks to videos working well for you?
By the way, if you would like to experiment with putting your own
videos online you can create a variant of this function,
(find-eev "eev-tlinks.el" "find-eevvideo-links")
http://angg.twu.net/eev-current/eev-tlinks.el.html#find-eevvideo-links
called, say, find-jeanlouisvideo-links, by replacing the
"http://angg.twu.net/eev-videos/%s.mp4" in find-eevvideo-links by
something else.
I'll answer the rest in other e-mails!
Cheers, =)
Eduardo Ochs
http://angg.twu.net/#eev
http://angg.twu.net/2021-video-links.html
next prev parent reply other threads:[~2021-06-04 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 3:41 Integrating eev and org-capture/org-capture-set-target-location Eduardo Ochs
2021-06-04 6:00 ` Jean Louis
2021-06-04 16:09 ` Eduardo Ochs [this message]
2021-06-04 18:14 ` Jean Louis
2021-06-04 22:28 ` Eduardo Ochs
2021-06-04 23:33 ` 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=CADs++6jrbUhDVCNwTXJNKwFivgnTcJTas+jebvFFWzzNou6Hpg@mail.gmail.com \
--to=eduardoochs@gmail.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@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.
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).