Re: Bidirectional links with eev

[Erich Ruff]

Hi Eduardo,

its a long time since we were talking about 'tla'

In the meentime I began writing my book and using this technique very
intensely and habe more than 100 books to which I can jump with short
expressions like

(ga101p ( + 16 127))

which will open Akademieausgabe of Fichtes Werken, Abt. I , Band 1,
Seite 127 with an offset of 16, thus excluding the forword of the
editors

Thank you for your good work done.

---------------------------------------

I read your new feature on double links.

This new feature was understandable for me only after finding out:

You have to create the eev-vars for the 2 docs first:

so you have to execute first:

doc1:  (code-c-d "sw2" "/mnt/fichte/" :anchor)
doc2:  (code-c-d "fall" "/home/er/fo/denote/" :anchor)

after having these two VARs set and the code executed the bidirectional
link-creation works --

but only if the cursors are positioned after the «anchor1»  in doc 1 and
«anchor2»  in doc 2 which should be connected to oneanother.

Perhaps this help some other user?

And then, there are 2 feature-requests:

1) Could you add an automatically inserted comment for LaTeX-files too? -> %%
double %%  to easly disguish added links

This would be very helpful for me.

2) In your example you have the 2 docs in a splitted frame with two
windows side by side in emacs

if I jump via link from doc 2 to doc 1 then doc 1  is opened in window-2
so I have the same file opened in 2 windows and the doc 2 is gone.

Could it be possible to keep both windws as they are and jump with the link to
the other window to the requested anchor without opening the doc a
second tim2??

Or is is my emacs-config which is  the culprit?

-------------------

Question:

In your tutorial you write:
3. Converting `c's to `d's
;; ==========================
;; Remember that the arguments for a `code-c-d' are called "c" (for
;; "code") and "d" (for "directory"),
;;              ^            ^
;;              |            |
;; ....
;;
;; and then we will see that there are two ways to convert the `c'
;; "foo" to its corresponding `d', "/tmp/FOO/":
;;
;;   ee-foodir
;;   ;; --> "/tmp/FOO/"
;;   (ee-foofile "BAR/PLIC/bletch")
;;   ;; --> "/tmp/FOO/BAR/PLIC/bletch"
;;

but the jump-address in case 1 is  a dir
and the jump-address in case 3 is  a file


Hope you get not angry about my long mail

Best

Erich



On Sa 24 Sep 2022 at 02:27, Eduardo Ochs <eduardoochs@gmail.com> wrote:

> Hi all,
>
> one of my submissions to the EmacsConf2022 is this one:
>
>   "Bidirectional links with eev"
>   http://angg.twu.net/emacsconf2022-kla.html
>
> Most people who use eev know that _using_ elisp hyperlinks to anchors
> is easy, but the standard method for _creating_ elisp hyperlinks to
> anchor needs lots of keys...
>
> I've been experimenting with a more practical way to create those
> hyperlinks to anchors. We need to set up the variable `ee-preferred-c'
> correctly - and this is tricky - but after that we can type `M-x kla',
> or `M-x ee-kla' (mnemonic: <K>ill <L>ink to <A>nchor), and ta-da, the
> link will be pushed into the kill ring.
>
> There is a tutorial here:
>
>   http://angg.twu.net/eev-current/eev-kla.el.html#intro
>   (find-eev "eev-kla.el" "intro")
>
> I've been using `M-x kla' and its variants `M-x klas', `M-x klf', and
> `M-x klfs' a LOT, and I'm quite happy with them. The tutorial ends
> with a long explanation of the thing that creates "bidirectional
> links" - `M-x kla2' - that is very impressive, but that I don't know
> yet if it's practical.
>
> The version of eev with these new things is already on github, and it
> should enter ELPA in a few hours. Hint: try `M-x eev-version' - it
> should show 20220924.
>
> All feedback would be extremely welcome - including questions and
> complaints!
>
>   Cheers,
>     Eduardo Ochs
>     http://angg.twu.net/#eev