News for hackers. Stuff that matters.
Re:Emacs org-mode examples and cookbook by Jtsummers on Thursday March 09, 2017 @09:15AM (#13829359)
I started with simple outlines. Then started using `TODO` and similar states to track tasks and projects, along with checklists. There's a ton that I never use, I'm honestly only using the following 95% of the time:

  * 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
But when I want more, it's there, and I can extend it. I toyed around with, but didn't complete, having rust code snippets exported to temp files that would be compiled with the output pushed back into the buffer, for example. Just stole the org-babel code for handling C and tweaked it. I made custom states for handling my org file which contains my ledger file (ledger-cli user) so it more clearly matches my workflow. Same with links to JIRA entries at work, and creating a task management workflow that matched the way my work hours get billed and tracked by management.

OTOH, if Sublime and markdown works for you, keep using it. Nothing beats a functioning tool, in the end.

Re:Emacs org-mode examples and cookbook by stinkytaco on Thursday March 09, 2017 @08:01PM (#13835429)
> 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.

Re:Emacs org-mode examples and cookbook by baby on Sunday March 12, 2017 @07:26AM (#13850245)
You can extend ST with plugins.