Every time I try to get into org-mode, I just don't get where to start and how to do things. So I end up going back to Sublime text, creating markdown files to take my notes, works well.
* Headline 1 [1/2]
** TODO Headline 2 [2/4] :tag1:tag2:
- [ ] Some incomplete task
- [X] Some other task
- [ ] [[http://example.com][Only this part shows]]
- [X] C-c C-c will toggle the state
** DONE Headline 3
** Some code in this one :code:
#+BEGIN_SRC elisp
(defun some-function (foo)
...)
#+END_SRC
OTOH, if Sublime and markdown works for you, keep using it. Nothing beats a functioning tool, in the end.
I don't understand. You can just use a tool and not fiddle with it constantly? Tell me of this strange way of working.
I used org-mode to help me learn org-mode, using everything I learned prior to help bootstrap learning the next piece. At the same time I integrated the pomodoro technique into my work flow. So my habit item for learning org-mode was to spend one 25 minute period a day learning. Do this for a couple of weeks, making sure to spend some time customizing everything to suit your process and you should be all set.
I need a guide that tells me how to rationally prioritize work, health and family above my never-ending .emacs.d side project.
You don't need 90% of those massively complicated setups that you get when you Google "org mode tutorial".
https://www.youtube.com/watch?v=sQS06Qjnkcc&list=PLVtKhBrRV_...
Recently, I came back to it just to use for code/programming notes and instead of trying to organize all the code into source blocks I went the other way and added in my own comments and questions in blocks that can be toggled on/off around the code that's there. Now the only org syntax I really use from org-mode is `#+BEGIN:` blocks for comments/questions I can quiz myself on and occasionally headlines when I want to organize something because it's in the way of reading the plain text. If I gave advice to someone new to it it would be to start with just plaintext notes and only add what you really need. You can quickly go overboad once you are trying to figure out how to do footnotes, file linking, exporting w/ images, source code execution, etc.
"Distraction free" apps don't work, because I frequently need to switch windows a lot and need some fancy features.
Really, the answer for me is to work on staying focused. (Perhaps a lobotomy would help.) But it isn't a problem with my tools.
Later, I learned Emacs itself, and then learning Org was much easier, because I could look up functions and keys and variables and customizations, etc. from within Emacs. As some other people said, I just learned a little bit at a time as I used Org. Eventually, after customizing it and even making a couple of Org-related packages, it's become my own system that works the way I want it to. And I will probably use it for the rest of my life. That's one of the beautiful things about Emacs and Org.
Don't start with the manual. Emacs manuals are more like reference books.
Find some tutorials and go from there.
The learning curve is shallow - that I can promise.