I see you don't use termcap/ncurses anymore. Do you perform terminal handling yourself directly?
Thanks again!
340 karma · joined August 1, 2019
I see you don't use termcap/ncurses anymore. Do you perform terminal handling yourself directly?
Thanks again!
At a first glance, I only see advantages with this approach. What would be the caveats of using Austral instead of Rust (disregarding the ecosystem and toolchain factors)?
[1] https://github.com/spantaleev/matrix-docker-ansible-deploy
Second: making a change without tests is like walking in the dark without a flashlight. Having tests is a very important thing.
Read Working Effectively With Legacy Code", by "Michael Feathers, one of the best books I've read that really can help in situations like that. In summary, it boils down to having tests to aid your changes you need to make.
I'm a bit surprised nobody mentioned Spacemacs (https://www.spacemacs.org) as a very good alternative for vim users that want to learn Emacs. I'm very satisfied with it, although it is slow to start, but I'm going to try Emacs server/client that I just heard about in this discussion.
Have anybody tried Spacemacs?
For calendars, the problem is a bit more problematic, though. Yes, there are things like calendar[1] and remind[2], but nobody seems to use them nowadays and in the mobile world there is no app to process them. Do you know of any existing solutions for calendars that work like todotxt?
Also, the self-hosting capabilities in a few MB binary are astonishing and you just don't pay for what you don't use. In my own repositories, I don't use chat nor wiki pages, but I do use forum, the ticket system and technotes.
The community and developers are very nice to answer questions too, and are open for suggestions. There is room for even further improvement and it is more a matter of someone showing up willing to develop the specific feature of the project.
BTW, do you know if TUI programs (using curses/ncurses or related) are usable for blind users?
First, I think the intention is very good. There are some problems with email that I don't know if they are possible to fix. Yes, JMAP [1] try to fix some of these problems for clients, but other flaws cannot be fixed without breaking backwards compatibility. Even unsuccesful, audacious experiments like that bring about discussions about what are the limits of current technology, what alternatives we have and what alternatives we can build.
Anyway, the best solution for asynchronous communication is still email. An incompatible solution would have to provide a compatibility layer for that. People refer Matrix here but I've always thought that, although many teams have adopted Matrix as a solution for general communication, it is a chat platform and not a replacement for asynchronous communication.
I just glanced over the site so I may sound repetitive: as a suggestion, I'd recommend adding some screenshots of client applications, diagrams explaning how mnm works, an explanation about federation and something that highlights differences to email.
[1] https://jmap.io
When I first started this doc, it was just personal writing, because of that some links are scattered and there are TODO entries laying around. I'll fix that one day :-)
I soon got tired of drawing circles and numbers and decided to write a quick Gimp plugin that does just that:
https://github.com/silasdb/mark-number-circles/blob/master/m...
I new nothing about Scheme at the time (the script is written in an imperative style) but I still think it is one of the smallest and most useful pieces of code I've ever written and from time to time I get an email from a random person from the world thanking for this small script :-)
EDIT: fix English