eev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On "write function for each reference"


From: Eduardo Ochs
Subject: On "write function for each reference"
Date: Sat, 7 Jan 2023 22:36:02 -0300

Hi Jean,

In this post to the mailing list

  https://lists.gnu.org/archive/html/eev/2023-01/msg00012.html

you also said:

> After watching video, which is understandable, I can see:
>
> - that you move to some buffer, or file
> - come back to your notes buffer or file
> - insert and write functions which refer to other buffers or file or 
> information
>
> My understanding raised.
>
> There is also surprise moment. Do you wish to know about it?
> ------------------------------------------------------------
>
> It is not easy believable that you have to write function for each
> reference. Why waste time when you already use keys.
>
> What you do, how I understand is, you are capturing bookmarks that
> lead to information. But you capture such bookmarks by using marking,
> region, then writing the eev functions in notes buffer. Am I right so
> far?


My `find-here-links' suppports many kinds of "here"s - the current
list is here:

  (find-eev "eev-hlinks.el" "ee-fhl-main-program")

and for many of these kinds of "here"s I didn't have reasons to
optimize the generation of links _yet_... for example, now I have this
to generate links to files and anchors in files very quickly,

  (find-kla-intro)
  (find-eev "eev-kla.el")

but if I want to save a link to something that someone has said in
Telegram I still have to run `M-h M-h' on a Telega chat buffer and
choose the most readable link by hand. I don't save links to Telegram
messages often, so I didn't optimize that _yet_, and I treat this

  (find-eev "eev-tlinks.el" "find-telegachat-links")

as a prototype that may be enhanced in the future.


A bit more on bookmarks
=======================
I use "registers" a bit - this thing here:

  (find-enode "Position Registers")

but I as soon as I use more than two registers I start to forget which
is which... so I started to use functions with very short names
instead, and I put the ones that I'm "using" in the end on my ~/.emacs
- this makes the list very easy to check. Here is a partial list:

  (defun ki  () (interactive) (find-kla-intro))
  (defun rsi () (interactive) (find-rstdoc-intro))
  (defun kle () (interactive) (find-eev "eev-kla.el"))
  (defun rse () (interactive) (find-eev "eev-rstdoc.el"))
  (defun tes () (interactive) (find-fline "~/elisp/test.el"))
  (defun ke  () (interactive) (find-es "emacsconf2022"))
  (defun me  () (interactive) (find-es "maxima"))
  (defun ee  () (interactive) (find-es "emacs"))
  (defun ev  () (interactive) (find-fline "~/TH/eev-videos.blogme"))

  (defun ge () (interactive) (find-es "tex" "geometry"))
  (defun rp () (interactive) (find-angg "elisp/rcd-paps.el"))
  (defun lo () (interactive) (find-fline
"~/TH/eev-for-longtime-EMACS-users.blogme"))

They were all generated by producing a hyperlink with `M-h M-h', i.e.,
find-here-links, removing the initial comment sign, putting a short
name in its place, and then running `M-J', that is explained here:

  (find-eev-quick-intro "7.1. `eejump'" "meta-uppercase-j")

I have experimented with many ways of sending either the hyperlink in
the current line or the region to my "current file with notes"... in
many of these experiments I would make `M-9 M-j' open the "current
file with notes", so that it would be very easy to change the "current
file with notes" to another one, but all these experiments only
yielded functions that I used for a few minutes and abandoned later...

  Cheers,
    E.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]