Re: eev-beginner

2022-04-11 Thread Eduardo Ochs
On Mon, 11 Apr 2022 at 22:18, Quiliro Ordóñez  wrote:
>
> Hello Eduardo.
>
> I understand eev more each time I use it.  I find myself reading the
> beginner's intro from the start each time.  That has helped me review
> the basic concepts each time.  But it would also be handy to continue
> automaticaly where I left with each new start. Is there a way I can save
> the place I am at, like the Emac's tutorial does it?

Hi Quiliro,

The most eev-ish way to do what you want is to use `M-h M-h' - a.k.a.
`find-here-links' - to create an elisp hyperlink to the tutorial that
you are reading, and then refine that hyperlink and copy it to your
notes... see:

  (find-eev-quick-intro "4.1. `find-here-links'")
  http://angg.twu.net/eev-intros/find-eev-quick-intro.html#4.1

  (find-refining-intro "2. Refining hyperlinks")
  http://angg.twu.net/eev-intros/find-refining-intro.html#2

You can either refine it by using copy and paste in the standard way
and adding the double quotes by hand, or you can use the advanced
editing keys explained here...

  (find-refining-intro "2. Refining hyperlinks")

If you want to point to the title of the section then you will have to
do a trick to avoid copying the invisible text. This is explained in
this section of an obscure tutorial,

  (find-saving-links-intro "3.3. Invisible text")
  http://angg.twu.net/eev-intros/find-saving-links-intro.html#3.3

and in this video:

  ;; (find-1stclassvideo-links "2021workshop4")

  ;; Title: Invisible text (workshop 2021-dec-04)
  ;; MP4:   http://angg.twu.net/eev-videos/2021-workshop-4.mp4
  ;; YT:http://www.youtube.com/watch?v=lhpHHjBUxv8
  ;; Page:  http://angg.twu.net/2021-workshop.html
  ;; Comment: Very bad - don't watch!!!
  ;; Date:2021dec04
  ;; Length:  5:42
  ;;
  ;; Play:  (find-2021workshop4video "0:00")

Cheers =),
  Eduardo Ochs
  http://angg.twu.net/#eev-blogposts



Re: eev-beginner

2022-04-12 Thread Quiliro Ordóñez
This is that you have posted is very interesting.  I now understand how
you make your links with eev.  It will prove very useful for me once I
get more experience.  I have tested M-h M-h and it looks very promising.
 Tomorow I will test the other information that you have provided in
your response.  Thank you very much, Eduardo.

Nevertheless, I was looking for a way to have Emacs open the file at the
point that I left last time I had opened it without creating a
hyperlink.  This is what the Emacs tutorial does.  Is there a way to do
this?



Re: eev-beginner

2022-04-12 Thread Eduardo Ochs
On Tue, 12 Apr 2022, 23:47 Quiliro Ordóñez,  wrote:

> This is that you have posted is very interesting.  I now understand how
> you make your links with eev.  It will prove very useful for me once I
> get more experience.  I have tested M-h M-h and it looks very promising.
>  Tomorow I will test the other information that you have provided in
> your response.  Thank you very much, Eduardo.
>
> Nevertheless, I was looking for a way to have Emacs open the file at the
> point that I left last time I had opened it without creating a
> hyperlink.  This is what the Emacs tutorial does.  Is there a way to do
> this?
>

Hi Quiliro,
not out of the box...
The feature that you are imagining would have a back-end in which the link
to the right position of the tutorial is generated, saved somewhere, and
executed when the tutorials are started again. Eev implements parts of that
back-end, but I liked the idea of playing with visible sexps so much that I
never tried to implement the part that would hide these sexps and do the
rest automatically...
  [[]], E.


Re: eev-beginner

2022-04-13 Thread Quiliro Ordóñez
El 2022-04-12 22:28, Eduardo Ochs escribió:
> On Tue, 12 Apr 2022, 23:47 Quiliro Ordóñez, 
> wrote:
> 
>> This is that you have posted is very interesting.  I now understand
>> how
>> you make your links with eev.  It will prove very useful for me once
>> I
>> get more experience.  I have tested M-h M-h and it looks very
>> promising.
>> Tomorow I will test the other information that you have provided in
>> your response.  Thank you very much, Eduardo.
>>
>> Nevertheless, I was looking for a way to have Emacs open the file at
>> the
>> point that I left last time I had opened it without creating a
>> hyperlink.  This is what the Emacs tutorial does.  Is there a way to
>> do
>> this?
> 
> Hi Quiliro,
> not out of the box...
> The feature that you are imagining would have a back-end in which the
> link to the right position of the tutorial is generated, saved
> somewhere, and executed when the tutorials are started again. Eev
> implements parts of that back-end, but I liked the idea of playing
> with visible sexps so much that I never tried to implement the part
> that would hide these sexps and do the rest automatically...
>   [[]], E.

Oh! Good point.  Seeing the code is important to connect the code with
its functionality.  But, in reality, I do not want the code to be
hidden.  I would just like to configure Emacs to open all files where I
last closed them.  Is there a way to do that, then?



Re: eev-beginner

2022-04-13 Thread Quiliro Ordóñez
El 2022-04-11 20:32, Eduardo Ochs escribió:
> On Mon, 11 Apr 2022 at 22:18, Quiliro Ordóñez  wrote:
>>
>> Hello Eduardo.
>>
>> I understand eev more each time I use it.  I find myself reading the
>> beginner's intro from the start each time.  That has helped me review
>> the basic concepts each time.  But it would also be handy to continue
>> automaticaly where I left with each new start. Is there a way I can save
>> the place I am at, like the Emac's tutorial does it?
> 
> Hi Quiliro,
> 
> The most eev-ish way to do what you want is to use `M-h M-h' - a.k.a.
> `find-here-links' - to create an elisp hyperlink to the tutorial that
> you are reading, and then refine that hyperlink and copy it to your
> notes... see:
> 
>   (find-eev-quick-intro "4.1. `find-here-links'")
>   http://angg.twu.net/eev-intros/find-eev-quick-intro.html#4.1
> 
>   (find-refining-intro "2. Refining hyperlinks")
>   http://angg.twu.net/eev-intros/find-refining-intro.html#2
> 
> You can either refine it by using copy and paste in the standard way
> and adding the double quotes by hand, or you can use the advanced
> editing keys explained here...
> 
>   (find-refining-intro "2. Refining hyperlinks")

Very nice instructions on all the references.  Congratulations.  They
were very helpful for understanding eev better.

I tried C-h f for finding the descriptions of some of your commands. 
But they seem undocumented.  Nevertheless, there is documentation in the
source code.  Is there a reason for this?
 
> If you want to point to the title of the section then you will have to
> do a trick to avoid copying the invisible text. This is explained in
> this section of an obscure tutorial,
> 
>   (find-saving-links-intro "3.3. Invisible text")
>   http://angg.twu.net/eev-intros/find-saving-links-intro.html#3.3

Is this line:
"use `M-w' to copy the region to the kill ring and `M-hy'
to yank it into this sexp"

supposed to be:
"use `M-w' to copy the region to the kill ring and `M-h M-y'
to yank it into this sexp"

?

Later, I see you use this format elsewhere.  Which is the reason to use
`M-hy' as a replacement of `M-h M-y' ?

> 
> and in this video:
> 
>   ;; (find-1stclassvideo-links "2021workshop4")
> 
>   ;; Title: Invisible text (workshop 2021-dec-04)
>   ;; MP4:   http://angg.twu.net/eev-videos/2021-workshop-4.mp4
>   ;; YT:http://www.youtube.com/watch?v=lhpHHjBUxv8
>   ;; Page:  http://angg.twu.net/2021-workshop.html
>   ;; Comment: Very bad - don't watch!!!
>   ;; Date:2021dec04
>   ;; Length:  5:42
>   ;;
>   ;; Play:  (find-2021workshop4video "0:00")

The video was quite explanatory and left everything clear for me.  But
the temporary buffer generated by find-1stclassvideo-links was not so
clear to me.  Please explain the contents.

Thank you very much for your help.  :-)



Re: eev-beginner

2022-04-13 Thread Tomas Hlavaty
On Wed 13 Apr 2022 at 12:34, Quiliro Ordóñez  wrote:
> I would just like to configure Emacs to open all files where I
> last closed them.  Is there a way to do that, then?

such functionality is not part of eev
but you might have luck searching for other emacs packages
for example
https://www.emacswiki.org/emacs?action=browse;oldid=DeskTop;id=Desktop



Re: eev-beginner

2022-04-13 Thread Quiliro Ordóñez
El 2022-04-13 17:48, Tomas Hlavaty escribió:
> On Wed 13 Apr 2022 at 12:34, Quiliro Ordóñez  wrote:
>> I would just like to configure Emacs to open all files where I
>> last closed them.  Is there a way to do that, then?
> 
> such functionality is not part of eev
> but you might have luck searching for other emacs packages
> for example
> https://www.emacswiki.org/emacs?action=browse;oldid=DeskTop;id=Desktop

Thanks.  It has given me some ideas.  

"Desktop will load, at startup, the buffers you were editing when you
last quit Emacs."

I do not need to open the same files as were open in the previous
session.  I need to open files at the same point that they had when I
opened them last time, even if they were not opened a long time ago.



Re: eev-beginner

2022-04-13 Thread Quiliro Ordóñez
El 2022-04-13 19:57, Quiliro Ordóñez escribió:
> El 2022-04-13 17:48, Tomas Hlavaty escribió:
>> On Wed 13 Apr 2022 at 12:34, Quiliro Ordóñez  wrote:
>>> I would just like to configure Emacs to open all files where I
>>> last closed them.  Is there a way to do that, then?
>>
>> such functionality is not part of eev
>> but you might have luck searching for other emacs packages
>> for example
>> https://www.emacswiki.org/emacs?action=browse;oldid=DeskTop;id=Desktop
> 
> Thanks.  It has given me some ideas.  
> 
> "Desktop will load, at startup, the buffers you were editing when you
> last quit Emacs."
> 
> I do not need to open the same files as were open in the previous
> session.  I need to open files at the same point that they had when I
> opened them last time, even if they were not opened a long time ago.

(save-place-mode 1) 



Re: eev-beginner

2022-04-13 Thread Eduardo Ochs
On Wed, 13 Apr 2022 at 17:52, Quiliro Ordóñez  wrote:
> (...)

Hi Quiliro!

> Very nice instructions on all the references.  Congratulations.  They
> were very helpful for understanding eev better.

Thanks! =)

> I tried C-h f for finding the descriptions of some of your commands.
> But they seem undocumented.  Nevertheless, there is documentation in the
> source code.  Is there a reason for this?

Eev has lots of functions that are just one or two lines long, and
that are "documented" by tests in comments in the source. I
experimented with lots of styles of writing docstrings over the years,
and I found that it was usually better to keep the examples and tests
outside of the docstrings - i.e., in the comments - and always
encourage people to always look at the source.

The "source" is not always in a .el file, though. Eev has many
functions that are generated dynamically, and people need to use
`find-efunctionpp' to inspect them. See:

  (find-eev-quick-intro "9. Shorter hyperlinks")
  (find-eev-quick-intro "9.1. `code-c-d'")
  (find-elisp-intro "11. Byte-compiled functions")
  (find-eev-quick-intro "7.1. `eejump'")
  (find-eev-quick-intro "7.1. `eejump'" "meta-uppercase-j")
  (find-eev-quick-intro "7.3. Defining eejump targets")
  (find-eev-quick-intro "7.4. Commands with very short names")
  (find-eev2020video "19:03" "commands with very short names")
  (find-eev2020video "21:07" "commands with very short numbers")

> Later, I see you use this format elsewhere.  Which is the reason to use
> `M-hy' as a replacement of `M-h M-y' ?

I use that format a lot in this tutorial

  (find-saving-links-intro)

to remind people that these keys sequences are intended to be typed
with the meta key being hold down, as explained here,

  (find-eev-quick-intro "7.1. `eejump'")
  (find-eev-quick-intro "7.1. `eejump'" "hold the meta key")

and because I wanted to show the tricks that I use to make these key
sequences take little mental space: I have a way to pronounce these
key sequences in which I only say "meta" once, and I have a compact
way to write them. If people learn these tricks then they _may_ be
able to learn - I mean, without much pain - the workflows for saving
links that I describe in `(find-saving-links-intro)'... I don't know
if these ideas work well, though - AFAIK very few people have tried to
follow that tutorial.

> The video was quite explanatory and left everything clear for me.  But
> the temporary buffer generated by find-1stclassvideo-links was not so
> clear to me.  Please explain the contents.

Can you run the first test in

  (find-efunction 'find-1stclassvideo-links)

and tell me which of the links in the generated buffer don't make
sense to you?

  Cheers,
E. =)