Hi!
I'm happy to announce you all the very minor, yet important, release of
schain 2.1.1. This is a revision release that makes our code safer when
treating user input! Yay for safety!

Release notes:
* Code improvements to avoid possible buffer overflows.

Cheers!
Ari

-- 
Ariadna Vigo
(she/her)

Hi there!
I'm happy to announce the new cras 1.4.3 revision release. This new
version includes two important bugfixes related to user input. I
recommend you update to avoid accidental file corruption with long
entries.

Release notes:
* Bugfix: cras no longer asks for input when using -e on an invalid
  entry.
* Bugfix: fixed overflow issues corrupting task files.
* Several code improvements.

xoxo,
Ari

Hi there!
First, Happy Easter! It's sunny here in Pamplona and I'm indoors doing
some *important coding* lol

OK, jokes aside, I've been thinking about how cras outputs things on
screen and I must say, it's very very improvable.

One of the things that has annoyed me the most in these last months is
how (and where) we show the expiry date for a given task file. 

	$ cras some-task-file
	Due date: Sun Apr  4 23:56:38 2021
	
	#01 [TODO] Some task

Hi Drew!

Your post comes in perfect timing... at least in my side of things!
It's a lovely read, as usual!

Thing is that I've been loosely trying out some Go software these days
and I've become increasingly curious about the language itself. I've
played a bit with it (I can't say I built anything, not even anything
trivial) and it looks really, really nice to me except for one thing...

The whole modules distribution thing.

It's something I dislike in all modern programming languages: be it 
PyPI, Ruby gems, npm, and even older ones like CTAN, CPAN, ASDF,

Hi everyone!
I'm happy to announce that a new, great smelling, very shiny new point
release of schain is available for you all: schain 2.1.0! The best
new feature is the new -K flag, which allows you for more flexibility
when cheking in a tracker file!

Release notes:
* Fixed several bugs related to negative values being unchecked both
  at CLI options and in tracker files. Now all values are always
  checked if they're >= 0.
* New -K flag for adding an arbitrary number of days when checking in
  a tracker file.

Hope you like it!

Hi!
Ariadna here :) I'm inaugurating this mailing list with a very loose
idea of where this project seems to be going to. I usually start things
following an intuition, trying out things, until things start to get
more and more solid as time (and commits) pass.

So, it appears that at least in the short term, scalc will remain an
RPN-based calculator. I do have a bit of the temptation to make this
a mathematic language somehow, by adding an addressing/jump system and 
some sort of memory storage... but if that ever happens, it'll be in a
distant future.

For now, I think some memory registers like all pocket calculators seem
to have would be great as "milestone" for releasing a 0.1 version of

Hi!
[OK, I think this time I sent this right... neomutt is hell 
sometimes... Sorry for the mess]

> I just sent in 5 patches with proposed fixes for any POSIX issues, and copied you on said patches.
> I'd appreciate it if you could take a look :)
> 
> No rush though, feel free to take a look whenever you have the time!

I did have the time! :) I applied them locally and everything looks
awesome!

In fact, look at this ;)

Hi again Ari! Thanks for all the tips!

I just sent in 5 patches with proposed fixes for any POSIX issues, and copied you on said patches.
I'd appreciate it if you could take a look :)

No rush though, feel free to take a look whenever you have the time!

I did include an introductory message in the patchset via the `--compose` flag that didn't seem to appear, so I'll include it here just in case:

> I've sent 5 patches that fix all POSIX compliance issues I could find
> in tday-sh via `checkbashisms` and `shellcheck`.
> 
> The patches also contain fixes for other issues reported by
> `shellcheck`, and as such they should make the script more robust

Hi!
So, I just released schain 2.0.4... please update now, because, well,
2.0.3 will be remembered as the worst schain release ever. It suffered
from a very nasty bug that prevented it from opening any file. This is
what happens when you release software a bit too hastely. Sorry for the
inconveniences... :( I promise this one does work...

Release notes:
* Bugfix: Fixed critical bug that prevented schain from opening any
  file.

xoxo,
Ari

Hi there!
I'm here to announce you all that a small bigfix release of schain is 
already here! These are the release notes for schain 2.0.3:

Release notes:
* Bug fix: schain segfaulted when passed a directory as argument.
* Improved error handling and messages.

xoxo,
Ari

-- 
Ariadna Vigo
(she/her)