VS Code Org Mode (opens in new tab)

I would not call it a must have as the default configuration doesn't indent the body. I don't have the option set and I would wager the majority of orgmode users don't either.

With VSCode there doesn't seem to be such a technical limit. See: https://marketplace.visualstudio.com/items?itemName=sean10.m...

I think that Emacs does print two asterisks for the Bar heading, but all save the last are coloured the same colour as the background. And a single space is used for indentation for every heading asterisk - so a four-asterisk heading is indented four spaces.

I'm also a VIM user suffering Emacs just for org-mode. Evil makes it livable.

I see why some might like it, and it does improve readability, but I actually turn off org-ident-mode. I use a text editor because I like to see the syntax; brutalist by design, keep the magic hat tricks for Office.

Org Mode is large enough for different people to value different subsets.

What's important for me is the tree structure, tags, states (like TODO, but I use many custom variants in different files), links, archiving, quoting (including code blocks, but I don't need to run them in place), easy per-file properties, easy export to many formats. I barely use time tracking, and never use agenda though.

Anyway, a subset of features implemented is a good foundation for further development.

You could use the Agenda from EasyOrg [0] in combination with VS Code or Sublime to get the Agenda functionality. EasyOrg has its own editor just in case.

[0] https://easyorgmode.com

The maintainer of org-mode seems interested in this project, which I thought was cool.

Org mode actually uses both square and angle brackets for timestamps [1], but the square-ones are inactive, i.e. they don't show up in the agenda view. I guess the angle ones are the most useful, though.

[1] https://orgmode.org/manual/Timestamps.html

Not until it gets something akin to helm/ivy/consult.

I like emacs and have been using it for like 8 years, and doom makes my additional configuration small and manageable, but I’d switch to vscode in a heartbeat if it was possible to replicate basic features of an extended emacs. I just want a good editor at the end of the day.

* wgrep is hugely useful.

* Fuzzy searching with orderless is unmatched in any other editor. Being able to resume is hugely useful. Being able to plop the results into a saved buffer is hugely useful.

* magit is the only way to do complicated rebases.

I really want to move on but until vscode fixes their search, I’m stuck. I can live without a good git interface, I can’t live without navigating projects in a grep-oriented way.

Vim doesn’t have this either, by the way.

The most annoying thing to me about VS Code is it cannot be extended in a way that doesn't require developing a plugin. In short there is no ~/.vscode.ts. Instead you have to create a plugin to add custom commands.

I say this a a former emacs user now using VS Code.

You sure? I don't think VS Code is open-source (happy to be proven wrong) and that's an important part of Emacs.

Arguably not without a Lisp-based implementation and extension language.

That said, as a multi-decade Emacs (and Lisp) user, I do like VS Code and its JavaScript/TypeScript basis.

On the surface that appears to make no sense at all. Do you mind being a little more descriptive?

Org mode started as an Emacs only thing. Over time it has evolved into a much more capable thing than markdown format. One can do almost anything in the org mode format: literate programming with code blocks which can be executed (org babel), plain text spreadsheets, scheduling and summarizing scheduled events in an agenda view, time tracking, thesis writing (it has the necessary syntax for element one needs when writing a thesis, unlike normal markdown), inter-document linking, and probably many other things.

Some time ago people started slowly bringing things to VS Code. Org mode syntax has also been separated out as "orgdown". Now finally other editors are catching up to what has been possible in Emacs for a long time using org mode. They still got a long way to go, because integration of org mode things in Emacs is very far ahead, but at least work is being done.

Kinda difficult to explain as I dropped emacs due to issues with it on Windows despite enjoying org-mode.

The key thing is, org-mode treats data/text as a tree graph programmatically, you move through headings, and properties can be attached to those.

So a property for a deadline time can be added, and parsed, so you can get a list of todos/schedule showing the headline, and being able to jump to it.

Your api access targets these "nodes", so you are adding under "journal" rather than line 674 when using the template feature to quickly add entries.

emacs has ridiculous levels of customisation that let this data structure do basically what you want or need with some scripting.

It is an extension of Emacs outline mode. Outliners are hierarchical text formats. Org added many useful things to outline mode: keywords, tags, timestamps, footnotes, links, tables...

What makes Org unique is the presence of interpreters, including user-defined ones, that take Org files as input and do things on them.

A famous interpreter is org-agenda which harvests TODO keywords, timestamp deadlines, etc. from different Org files to generate a weekly agenda. Another one is Babel which runs embedded code in Org files, i.e. a literate programming system.

To sum up, Org is a plain text format analogous to Markdown, but with many more features and also interpreters that define certain operations on them.

It's markdown with Excel's ease of creating buttons (in org-mode's case ascii buttons) to execute arbitrary callbacks, e.g., cross referencing, summarizing, sorting, etc.

It primarily appeals to weekly status jockeys (project managers) whose rudimentary programming skills are just good enough to hack some emacs lisp. As someone who doesn't mind grepping an omnibus "notes.txt" file and thinks "literate programming" is a waste of time, I've never found a use for org-mode.

Org-mode is to Markdown what JavaScript is to HTML

Explaining org-mode at this point is almost akin to explaining emacs itself.

What is Emacs? Is it a text editor, for editing config files?

Is it an IDE for development? An email reader?

Org-Mode is a mode for Emacs that provides structure to documents in such a way that it allows documents to be used for many things- authorship (web sites, books, etc.) but its primary use for most of us who is it is to integrate into our todo management systems- allowing us to manage our tasks in a way that's integrated into our work. It provides flexible, queryable and programmable todo lists, document generation, literate programming, spreadsheets, living documents that can execute code, time tracking, and more.

It can also integrate with other tools, like org-roam, to provide backlinks and other features, or work with tools like mu4e to integrate email and todo lists in both directions.

In other words, it's a system for working with data/life.

Short version: an text file based note taker, an outline editor, a calendar and an operating system disguised as a text editor came together to make an incredibly handy personal information manager. The file format looks like markdown, but is not markdown (and existed before markdown).

My one-sentence take on it is: A personal Atlassian Confluence that doesn't suck.

There's more to it than that, but I think that that's the killer use case that gets most people hooked on it in the first place.

This doesn't have note templating, schemas, back links, note links, wiki links, it's nowhere near as close as Dendron is feature wise.