Your rating: None Average: 5 (1 vote)

Memo is a command line, Unix-style note-taking software written in C99. It's very flexible and works well with standard Unix tools. Memo is developed by Nico Rosvall. I have just packaged it.

Application versions: 
File memo-1.0-10.40.1.jolla_.armv7hl.rpm9.12 KB28/10/2014 - 04:29
File memo-1.2-10.14.1.jolla_.armv7hl.rpm9.48 KB01/11/2014 - 03:29
File memo-1.3-10.7.1.jolla_.armv7hl.rpm9.82 KB16/11/2014 - 04:12
File memo-1.4-10.4.1.jolla_.armv7hl.rpm10.57 KB30/12/2014 - 05:57
File memo-1.5-10.7.1.jolla_.armv7hl.rpm11.9 KB10/01/2015 - 09:52

Version 1.5 released.

Memo can now export notes to a CSV file.

In ~/.memorc a property MARK_AS_DONE can be set. The property takes a valid date(yyyy-MM-dd) as a value. When set Memo will automatically mark notes older than the date as done.

New command line flag -O added. With -O Memo reorders note id codes. For example if there's notes with id codes 1,4 and 5 they will become 1,2 and 3.

Search is no longer case sensitive.

On Windows Memo now uses _ as a file prefix instead of a dot. So on Windows .memorc is _memorc and .memo is _memo. However, Windows is not officially supported. Use Cygwin instead if on Windows.

This release includes multiple bug fixes and to avoid code duplication several helper functions where added.

As this version had increasing number of contributors I'm not going to list all the people here. Thanks for all the contributors for bug fixes and feature suggestions.


shellkr's picture

I am not sure if it's only me but I had to manually creat ~/.memo before it worked properly. If someone else confirms this I will add a post-install to fix it. It should be created automatically.

lassekoo's picture

I can confirm this. Didn't work until I created the ~/.memo file manually.

shellkr's picture

Hmm... somehow on Jolla it doesn't work. I am investigating why. I have narrowing it down to the creation of the file (open(path, O_RDWR | O_CREAT)). I might be able to patch it in someway. This doesn't happen on my desktop machine... anyway... thanks for letting me know. Now I know it is not just me. 

Adding a post-install is a very hacky solution and I hope that will not be necessary...

shellkr's picture

Latest release seems to have fixed it