Hacker Newsnew | past | comments | ask | show | jobs | submit | dizhn's commentslogin

Thank you for this!

I used Kate a note taking app synced with syncthing for a while. Using only md files. I had another md based app on Android that worked similarly.

Kate has a decent file browser for hierarchy and it'll stay in place and not return to a weird default path when you close it. And as you said, very fast to open and use.

For one off Notepad like things I like Mousepad especially because it has the Notepad++ feature of being able to save a session without asking you whether it should. Featherpad is also nice for this kind of use.


It's so fascinating how different things people look for in such a simple thing as a text editor. A file browser? Terminal?

Indeed, all I need is something that connect to a running background repl so I can evaluate code, everything else basically bells and whistles. Others seem to run entire OSes as their editor.

I'm glad we have so many options, and it seems like each year we have even more options :)


there's a reason Unix like systems usually ship with 3 or so

Encryption, deduplication, snapshots. Although if the poster has a zfs based system elsewhere zfs based backups would be fantastic.

There are exceptions to this such as Proxmox which can actually be added to an existing Debian install. I must admit that when I first encountered it I didn't expect much more than a glorified toy. However it is so much more than that and they do a really good job with the software and the features. If anybody is on the fence about it I recommend giving it a go. If you do, I recommend using the ISO to install, pick ZFS as the filesystem (much much more flexible), and run pbs (proxmox backup server) somewhere (even on the same box as an lxc host with zfs backed dir).

https://restic.readthedocs.io/en/stable/faq.html

It will resume from where it got interrupted. The only exception is the initial backup where it doesn't have a snapshot yet.


>Ignore feature requests — don't build what users ask for; understand the underlying problem instead

That sounds like good advice on the surface but it should be "understand what the user is asking for" then see if it is a valid thing, after which you can decide how to accomplish it. Users usually come to you with the last bit. They ask you to do it in a particular way.


Then wait for the one person in the org that deals with those documents to come back from their 3 week vacation.

Before opening the comments I made a bet with myself that the top comment would be about how someone made flash games in the 2000s and nothing really replaced it in the coming years. :)

It's not a port of FreeBSD jails ?

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: