foodogsquared/wiki
1
0
Fork 0
mirror of https://github.com/foo-dogsquared/wiki.git synced 2025-01-31 04:58:21 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
4d0a707891
wiki/notebook/2020-04-17-21-41-30.org

25 lines
1.2 KiB
Org Mode
Raw Normal View History

Migrate notes to org-roam v2
2021-05-04 16:07:40 +00:00
:PROPERTIES:
:ID: 5569a49f-c387-4da2-8f68-d8452e35ee5b
:END:
Create GNU Guix-related notes
2021-04-21 11:38:28 +00:00
#+title: Org mode: Babel
Update the files for convention Apparently, the convention (at least starting from 2018) is to make the keywords and block names to be in lowercase as stated from one of the following discussions at https://orgmode.org/list/87tuuw3n15.fsf@nicolasgoaziou.fr/. The files was updated with a one liner of shell. However, this is Emacs and org-mode does have an API to let you do stuff in your config and interact with the documents internally so it is not an elegant solution in any way.
2021-04-01 16:08:15 +00:00
#+date: "2020-04-17 21:41:30 +08:00"
Update wiki on various topics This update is too large, I made too many notes on stuff. Nonetheless, it is very nice to see progress. I've made note revisions on the following topics: - Learning - Writing - Various Linux-related stuff I've yet to start learning illustration but I'll be starting tomorrow for an update how do I keep in mind with those writings. There are still a lot of things to be processed from the backlog with yet more notes on learning but I keep having those perspectives whenever I practice so ehhh... Better have those than nothing? Furthermore, I've also updated the timestamp format. It is pretty simple to update all of the notes with a couple of `sed` calls. Aaaand, I've also changed the way how the assets stored with the folders only leaving it up for the generated files instead of enforcing it on every note. I create more visual aids and managing them is a pain for each note. This restructuring frees me of that burden.
2021-07-20 11:52:43 +00:00
#+date_modified: "2021-07-17 19:03:50 +08:00"
Update the files for convention Apparently, the convention (at least starting from 2018) is to make the keywords and block names to be in lowercase as stated from one of the following discussions at https://orgmode.org/list/87tuuw3n15.fsf@nicolasgoaziou.fr/. The files was updated with a one liner of shell. However, this is Emacs and org-mode does have an API to let you do stuff in your config and interact with the documents internally so it is not an elegant solution in any way.
2021-04-01 16:08:15 +00:00
#+language: en
Update the tags to be more consistent I will now use hierarchical tags similar to tildes. I think it's pretty cool. The tags are also primarily more explicit to make the tags more skimmable.
2021-04-05 12:03:26 +00:00
#+tags: research.reproducibility
Init commit of my wiki
2020-06-23 18:29:05 +00:00
Migrate notes to org-roam v2
2021-05-04 16:07:40 +00:00
Babel is the framework that enables [[id:c422175a-5b65-4311-8cc6-11efd55364e8][Org mode]] to be a [[id:6eeb7a24-b662-46d6-9ece-00a5028ff4d8][Reproducible research]] tool.
Make revisions on the skill-related notes In this case, it's mostly about the additional perspectives on how learning works from the act of managing your information through various note-taking methods. I also restructured the note on org-babel and moved as its own note on the hierarchical notebook. I think summarizing a tool and giving my own comments about it is a nicer way of describing it. Plus, I can freely link between any other types of note so I figured it would be better. That said, I should be picky on how to make org-roam entries. And also org-roam v2 is better, after all. :)
2021-05-19 16:13:41 +00:00
It is comparable to Jupyter and R Markdown that other computational scientists use it.
Init commit of my wiki
2020-06-23 18:29:05 +00:00
Make revisions on the skill-related notes In this case, it's mostly about the additional perspectives on how learning works from the act of managing your information through various note-taking methods. I also restructured the note on org-babel and moved as its own note on the hierarchical notebook. I think summarizing a tool and giving my own comments about it is a nicer way of describing it. Plus, I can freely link between any other types of note so I figured it would be better. That said, I should be picky on how to make org-roam entries. And also org-roam v2 is better, after all. :)
2021-05-19 16:13:41 +00:00
Among other features, it can do the following.
Init commit of my wiki
2020-06-23 18:29:05 +00:00
Make revisions on the skill-related notes In this case, it's mostly about the additional perspectives on how learning works from the act of managing your information through various note-taking methods. I also restructured the note on org-babel and moved as its own note on the hierarchical notebook. I think summarizing a tool and giving my own comments about it is a nicer way of describing it. Plus, I can freely link between any other types of note so I figured it would be better. That said, I should be picky on how to make org-roam entries. And also org-roam v2 is better, after all. :)
2021-05-19 16:13:41 +00:00
- Prints the results from code blocks.
- Create files from a single document, making it possible to create entire computational reports.
- Pass values from one code block to another, even with different programming languages.
- Create graphics similarly to Jupyter and R Markdown notebooks.
- Call code blocks either inline, as a block, or inside of another code block, thereby enabling metaprogramming and dynamic contents.
Init commit of my wiki
2020-06-23 18:29:05 +00:00
Update wiki on various topics This update is too large, I made too many notes on stuff. Nonetheless, it is very nice to see progress. I've made note revisions on the following topics: - Learning - Writing - Various Linux-related stuff I've yet to start learning illustration but I'll be starting tomorrow for an update how do I keep in mind with those writings. There are still a lot of things to be processed from the backlog with yet more notes on learning but I keep having those perspectives whenever I practice so ehhh... Better have those than nothing? Furthermore, I've also updated the timestamp format. It is pretty simple to update all of the notes with a couple of `sed` calls. Aaaand, I've also changed the way how the assets stored with the folders only leaving it up for the generated files instead of enforcing it on every note. I create more visual aids and managing them is a pain for each note. This restructuring frees me of that burden.
2021-07-20 11:52:43 +00:00
The unfortunate thing is most of these features are only available when using with [[id:ce6ab58e-b295-4fdb-8af7-fc89c63ec208][GNU Emacs]].
Init commit of my wiki
2020-06-23 18:29:05 +00:00
Make revisions on the skill-related notes In this case, it's mostly about the additional perspectives on how learning works from the act of managing your information through various note-taking methods. I also restructured the note on org-babel and moved as its own note on the hierarchical notebook. I think summarizing a tool and giving my own comments about it is a nicer way of describing it. Plus, I can freely link between any other types of note so I figured it would be better. That said, I should be picky on how to make org-roam entries. And also org-roam v2 is better, after all. :)
2021-05-19 16:13:41 +00:00
For more details, you can see [[id:4abb9be8-4414-4045-8827-5a68632fd2a4][The basics of org-babel]].
Reference in New Issue Copy Permalink