latex-snippets VS github-orgmode-tests

My ~/.vimrc configuration is just copied from this website https://github.com/gillescastel/latex-snippets

I was trying to use some of Gilles Castel's LaTeX snippets for my own notetaking, which I do on nvim with markdown, using pandoc to convert to pdf. The problem with this is that the tex snippets are designed to be activated only when in LaTeX math, but there's no function to directly check this in the plugin I'm using for pandoc markdown.

1) There's a different plugin based approach for LaTeX if you don't grow to like latex-suite (as I did): vimtex can be used to do the compiling, syntax highlighting, completion, navigating to the right spot in the code or pdf ect, and you can take care of the snippets yourself, either by simply not doing anything and typing everything out (completion aided), using :h :ab or using a snippet plugin (in the case of UltiSnips, a careful review of this would be a boost) 2) "just installing" vim plugins without reading about their features doesn't really add to anything other than the learning curve, because many vim plugins change the way vim works and can only be made useful by knowing about their features. If you just let them sit, many of them won't do anything other than slowing down the program. This might very well be different than in VSC

tex.snippet file i use

Each code block could be evaluated in place, with results appearing inline. Want to test JSON parsing? Write a block, execute it, see the output. Need to try different data structures? Compare approaches side-by-side with immediate feedback. This resembles the classic Lisp REPL workflow but with all the organizational benefits of org-mode. The development document became a living laboratory.

I'm a fan of Org Mode with Emacs [0] and using the app BeOrg [1] on my iPhone.

I have 3 main task files:

- todo.org for things I need to do

- backlog.org for things that I don't have to do now but should do in the future

- inbox.org for any random ideas or notes

The concept of an Inbox was taken straight from Getting Things Done [2].

I have different searches set up in BeOrg so that it is easy to view tasks from each different file.

This is definitely more complicated than a single file, but I like it mainly because it keeps my main task file (todo.org) organized. I also don't go through organizing my files that much either.

inbox.org is just a great place to dump anything, so I usually do a quick scan and either delete everything or refine it to the backlog.org.

For backlog.org, I'll usually just let things sit there and build up. After a while I'll realize that if something has been there for a long time, it probably isn't worth doing - or I already did it, so I delete it.

[0]: https://orgmode.org/

[1]: https://www.beorgapp.com/

[2]: https://hamberg.no/gtd

TIP: When asking for advice in relation to knowledge management, note-taking, etc., be sure to ask for precise details regarding commenters' solutions. There are many people who participate in these discussions who don't seem to take a lot of notes (e.g., one file or paper notepad for all of their notes!).

I have a personal knowledge base that currently includes almost 7,000 files in which I store my notes. I take notes on everything. Every technology. Every product. Every meeting. EVERYTHING.

My notes are stored in Org files that I edit with Emacs and Org mode[1]. Org files are written using a feature-rich lightweight markup language[2] that is much more powerful than Markdown (which is used by alternative note-taking tools like Obsidian). For example, Org supports plain text spreadsheets[3], a feature I love.

Too many people will disqualify Org and say, "I don't use Emacs," while assuming that Emacs users choose Org because we already use Emacs. But I started using Emacs specifically to use Org, not for programming.

But regardless of which tool you end up using, consider organizing your note files using hierarchical tagging. I started using hierarchical tagging for my notes right after Wikipedia was first launched and I saw how effectively hierarchical tagging was being used there. Each Wikipedia article can belong to multiple categories, and each category can belong to multiple categories. This is hierarchical tagging, and it's worked great for my notes. At the bottom of every one of my Org files, there is a list of "parent topics", and each parent topic has a list of parent topics (excluding the "main topics", which have no parents).

[1] https://orgmode.org/

[2] https://orgmode.org/features.html

[3] https://orgmode.org/manual/The-Spreadsheet.html

My favorite static site generator is Org mode[1] for Emacs. Org files are written using a feature-rich lightweight markup language[2] that is much more powerful than Markdown (e.g., plain text spreadsheets). Org files can be exported to HTML[3].

The reason I prefer Org for static site generation is not because I already use Emacs. I actually started using Emacs about 20 years ago specifically to use Org mode.

[1] https://orgmode.org/

[2] https://orgmode.org/features.html

[3] https://orgmode.org/manual/HTML-Export.html

"until recently, Jupyter notebooks were the only programming environment that let you see your data while you worked on it."

This is false. Org-mode has had this functionality for over two decades.

https://orgmode.org/

Work - I use org-mode heavily for my personal project management and note keeping.

While embracing analog tools, I've also refined my digital organization using ORG mode in Emacs. The system has evolved to become more structured and efficient.

Org mode. Org mode is just great for taking notes and organizing tasks. I might write a post on it one day. If you're interested, check out Org Mode in the mean time.

orgmode seems to be a big change after using Notion. However, I fell in love with Emacs, so I wanted to use all the best things. It was easy to set up org-agenda, org-roam, etc. Unfortunately, after a while, I noticed that using a non-standard system(not Markdown) could impact my note-sharing capabilities, as well my ~work~ docs were mostly built with Markdown. So, a note system that uses Markdown. Also, I switched to VIM :)