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

Support for custom naming schemas #95

Open
inem opened this issue Nov 10, 2019 · 2 comments
Open

Support for custom naming schemas #95

inem opened this issue Nov 10, 2019 · 2 comments

Comments

@inem
Copy link

inem commented Nov 10, 2019

I've recently learned about Zettelkasten, but I was upset that no single digital implementation of Zk has support for notes sequences like 1a1 → 1a2

I mean something like this:

1 note
1a subnote
1b subnote
1b1 subsubnote
2 another note

Instead it looks like everyone just stick to timestamps, and create overview notes to group related notes.

I don't like this approach. What I do is that I treat timestamped notes as unordered ones. Once I collected a bunch of unordered notes, I rename them manually to the following schema:

1 note  201911100816
1a subnote 201911092018
1b subnote 201911101155
1b1 subsubnote 201911101155
2 another note 201911100738

This allows me to have ability to define sequences of notes.
I also keep timestamps, because some of them might have already been linked to others, and I don't what to go through all the notes renaming them.

I think not so complex changes needed to support such flow:

  1. Support custom naming schemas like "2a1b another note 201911100738" (right now it says I have no notes at all)
  2. [[1a1]] should be recognized as proper link
  3. Detect timestamps if they are in the end of the string (this is needed when I click on a link which only contains timestamp, but the note has been already renamed to the new schema)
@inem
Copy link
Author

inem commented Nov 10, 2019

In the meanwhile trying to find a workaround. Figured out that the plugin recognizes "1.201911101050" as link, but unfortunately doesn't recognize "1a.201911101053".

If it would, then it would be an okayish compromise. I'd probably just stick to that schema.

@inem
Copy link
Author

inem commented Nov 10, 2019

I made an attempt to change the regexp, but it is not enough.

@renerocksai it would be great if you could point out at places in the code where changes needed to be made in order to support custom schema like "1a.201911101053" for notes IDs.

(I am new to both Python and Sublime Text extensions, but I'll figure it out if I know where to look at)

Thanks!

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

1 participant