Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First try. #6

Open
Ypot opened this issue Sep 15, 2024 · 7 comments
Open

First try. #6

Ypot opened this issue Sep 15, 2024 · 7 comments

Comments

@Ypot
Copy link

Ypot commented Sep 15, 2024

Hi!!

Some differences with my workflow. Probably yours is quite curated, and this won't be useful.

1.Trees. In a file I have several yanked books each in a tree, where subtrees are chapters. That would be my "references zettelkasten" tree. org-zettel-ref-mode doesn't seem to allow that, just one file for each document, isn't it?
2. Overview buffer: Do you keep an overview file for each book? How do you transform those overviews into a unified zettelkasten?. In my case, I use just a tree for my "ideas zettlekasten", which links to the "references zettelkasten" and to each other.
3. Maybe the only valuable suggestion: for links I love this format:

* Test 1
:PROPERTIES:
:ID:       2024-09-15T004054791309
:END:
[[N20240915T004053.190543][Quick note]]
* Overview
[[id:2024-09-15T004054791309::N20240915T004053.190543][Quick note]]

Now I would like to try your .py to get something better than my copy paste of pdf ;D

@yibie
Copy link
Owner

yibie commented Sep 15, 2024

One package can't be satisfied everyone's need.

1 - Yes, my method is one book, one ref note file. There are org-roam or denote, they can link notes very well. But it isn't strictly. Because some of my notes, are tree any account of notes with a specific topic.

Org-zettel-ref-mode is work for literature notes. And it is follow Lumann's way. You can read the readme, I explain it in detail.

But may be I can set a custom option, or a script, to gather all the literature notes in a org file, and list them like a tree.

2 - I don't understand your suggestion, what's the difference?

I'm very happy to hear that you found something useful to you. This meaning a lot of me. Thanks for your attention.

@Ypot
Copy link
Author

Ypot commented Sep 15, 2024

One package can't be satisfied everyone's need.

1 - Yes, my method is one book, one ref note file. There are org-roam or denote, they can link notes very well. But it isn't strictly. Because some of my notes, are tree any account of notes with a specific topic.

Org-zettel-ref-mode is work for literature notes. And it is follow Lumann's way. You can read the readme, I explain it in detail.

But may be I can set a custom option, or a script, to gather all the literature notes in a org file, and list them like a tree.

2 - I don't understand your suggestion, what's the difference?

I'm very happy to hear that you found something useful to you. This meaning a lot of me. Thanks for your attention.

Yes, I understand, it's nice to see your workflow.

Point 3 in my previous post was a suggestion with the kind of links I am experimenting right now. You can try just by yanking the shared code in an org buffer.

@yibie
Copy link
Owner

yibie commented Sep 15, 2024

I love to hear the news about your experiment. I didn't seem any link-type like this ever.

Could you tell me the detail?

@Ypot
Copy link
Author

Ypot commented Sep 15, 2024

I love to hear the news about your experiment. I didn't seem any link-type like this ever.

Could you tell me the detail?

[[id:2024-09-15T004054791309::N20240915T004053.190543][Quick note]]

It's an id link with seach. It searches in the headline defined with the id, what is after the ::
In this case I generate automatically a unique code, that is: N20240915T004053.190543

It works between different buffers, like normal id links.

It's new in org-mode:

id: links support search options;
https://orgmode.org/Changes.html

And if you use [[N20240915T004053.190543]] for the note, that makes a search by itself inside the buffer, similar to the links of the type <<>>.

This is the code I use to generate the unique Nxxx (it has more code than necessary, because I am trying to integrate it with org-super-links)

(defun my-insert-id-and-run-function ()
  "Genera un ID único usando `org-id-new`, lo inserta en el punto actual con corchetes, y lo copia al portapapeles."
  (interactive)
  ;; Generar un nuevo ID único usando org-id-new
  (let* ((id (org-id-new))   ;; Genera un nuevo ID único sin reutilizar uno existente
         ;; Formato del ID con corchetes para insertar en el buffer
         (id-with-brackets (concat "[[N" id "]]")))
    ;; Inserta el ID con corchetes en el punto actual
    (insert id-with-brackets)
    ;; Copiar el ID (sin corchetes) al portapapeles
    (kill-new id)
    (org-super-links-store-link)))

;; Asignar la función al atajo de teclado
(define-key org-mode-map (kbd "C-c l") 'my-insert-id-and-run-function)

@yibie
Copy link
Owner

yibie commented Sep 15, 2024

Insereting. But org-mode 8.0 is too new to everyone. So let me keep the target link type <<>> for now. Ugly, but everyone can use.

@yibie
Copy link
Owner

yibie commented Nov 12, 2024

Hi, I was update org-zettel-ref-mode to 0.5. Now, it has a new marked and notes system.

@dmitrym0
Copy link

@Ypot take a look at org-noter if you're interested in a similar workflow for PDFs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants