Having more than one calender app is very problematic to me. My life maps only to one real calendar. And since my employer is dictating Outlook for my work life, I am stuck with it for the rest also. I would love to use other solutions though (have looked into calcurse and remind so far) but the hassle of importing/exporting/syncing with other calendar implementations is not worth the effort and has never really worked for me.
This looks very interesting. As the original author of khal (another terminal calendar) [1] I love some more competition in this space.<p>[1] <a href="https://github.com/pimutils/khal" rel="nofollow">https://github.com/pimutils/khal</a>
I love to see such a great looking piece and I really want to use it. But then I think about portability, mobility and unify usage across environments and come to the conclusion that I don't want to have two or three tools for the same data.
Not related to this particular tool: It strikes me as extremely odd that nowadays „modern“ has become a desirable software feature. For me, „modern“ is the opposite of „durable“, which seems to be a rather bad thing.
Hey, developer here! Thank you for posting about my app! To answer a few questions:
- At the moment, you can't sync it with other calendars. If anyone has expertise in .ics format and python, please take a look at the issues on github, I've got some questions.
- "Modern" in the app description means that it uses unicode icons and scales to phone screens.
I love how long event titles can stretch across days. This is how I used to use calendars back in the days they were on paper.<p>In fact my ideal calendar software would dynamically grow/shrink dates to fit instead of making them all a uniform grid.
I love TUIs and I'm looking for a TUI calendar. But there's one feature they all lack: sending availability to someone. Using grep or rg would be great. That's where Calendly and Vimcal shine.
> Birthdays of your abook contacts<p>For stuff like this, why not make it scriptable?<p>if this / then that style. Let users define attributes such as "birthday" on day objects, then let them define what to do with it.
It's awesome in visual terms, but please consider a thing: CLI is very effective to combine different simple software together, witch is the classic UNIX paradigm. We know from the history that such paradigm is a FAIL, but it still have some points.<p>The need of visual stuff is UNIX fail. That's why older system, like Xerox Smalltalk workstations, was graphical by default, networked before unix was born. Long story short: we MUST recover such model in FLOSS, since this is a FLOSS game, no proprietary software can last longer in a classic desktop.<p>Witch means we need <i>integrated</i> tools. Emacs so far offer the best integration simply because is the sole living vestige of such classic past, Pharo (Smalltalk recover some visual aspects). That's what we need. Surely it's a hyper-long shot seen actual IT involution, but can be done if taken by a large community and CAN'T be parasited by any corporate move behind chasing to sell open-hardware platforms witch can't happen so quick.<p>That's is.<p>It's a very nice tool, but what if I want contacts merged? What if I want mail merged? Neomutt is another nice MUA, coupled with notmuch to search/access messages, but there is not much room to integrate both. What if I want to link files? ... That's the point of a unique OS-as-a-framework/apps-as-functions-of-such-framework vs UNIX KISS logic or worst modern GUI-as-self-contained-world.