date2name VS leo-editor

Not automatic but this worst very well https://github.com/novoid/date2name

It sorts by file name and alphabet. My guess-filename and date2name generate date- and timestamps quite cleverly as long as your meta-data is not broken.

Hi, I plan to add this to https://github.com/novoid/date2name which is a command line tool. I have not found out how to integrate command line tools on macOS to the context menu of the finder in a sane way like this tool provides for Windows File Explorer and probably GNU/Linux geeqie in future. It would be peachy if somebody has input on that. (I don't have access to macOS.)

Another thing I do see differently: I don't like version numbers since I prefer dates instead of numbers. There are different ways to use version numbers (one being proposed in the linked document). However, as the linked document also shows is that those versions are often accompanied with things like "draft" or "final" which introduces some kind of redundancy. I personally prefer date prefixes and filetags for "draft final submitted" for example. This is unambiguous so that version numbers do not add any value in my opinion.

The same tagging method could be used for a general controlled vocabulary (CV) such as: bills, contracts, NDAs, and so forth. I'd also go with semantic tags like draft, submitted and final (or submitted) in combination with date-stamps instead of version numbers that are useless to humans most of the time.

What are your experiences with literate programming for handover of code?

I am thinking of tools like noweb (https://en.wikipedia.org/wiki/Noweb), LEO (http://leoeditor.com/) org-mode (http://cachestocaches.com/2018/6/org-literate-programming/), scribble/lp2 (https://docs.racket-lang.org/scribble/lp.html#%28part._scribble_lp2_.Language%29),

My experience so far is that it can be a fantastic tool for documenting and handing over complex algorithms to successor developers. I use extensively use ersonal wikis (sometimes MoinMoin, sometimes Zim Wiki, in the last time often a combination of github with reStructuredText) for work. That might also be sufficient when handing over boring code.

I know what folding is, that's just not what I want. I want to completely hide everything that is not related to the current function. For a while, I used http://leoeditor.com/ where I could have every function/method as a node in a tree, with the node body containing just that. Looking for a way to achieve the same in vim if possible.

The lack of good node/graph based APIs for Org Mode is my beef as well. When you compare it with the APIs of the Leo Editor[1], Org pales in comparison. Manipulation that is trivial in the Leo Editor can be quite a pain in Org mode.

[1] https://leoeditor.com/

> What outliners do you know which allow end-users to feed their data into formulas for processing it without using general-purpose programming languages?

Bit of a pointless constraint, the talk is about outliners, not no-code-datamangment. Which tool today does this even offer on a useful level?

But you can look at leo editor (https://leoeditor.com), which is active for 20+ years, fully scriptable and extendable. Though, it's a hot piece of garbage for laymen. It's offers a bunch of features and plugins even for non-coders, but I'm not sure it would satisfy you for this area, if you can't code.

But I'm not sure if there ever is a tool which will satisfy everyone with just a no-code-approach.

Hmm maybe you mean:

- Programming based on fragments, not documents (e.g. LEO https://leoeditor.com/)

- Live programming (e.g. smalltalk environments)

- ... where certain actions are not available, e.g. a PL geared towards speech recognition may not support "hover"

There's also https://leoeditor.com/ where you can have a tree of nodes and execute any of them.

I had this problem until I found an editor that had outlining as it's core design paradigm. Now, with the outline always visible, it's _really_ easy to navigate any length file.

Unfortunately, at one point I got so used to navigating with the outline that I ended up making a 1500 line function in C (I was an even worse C programmer then than I am now). Because of the outline, I could read and follow it easily, but anyone with a different editor was royally screwed :-(

If you're interested, the editor is LEO (http://leoeditor.com/) it's been mentioned on HN a few times