Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 30 13:47
    codingthat commented #8
  • Mar 31 06:21
    YodaEmbedding edited #62
  • Mar 31 06:21
    YodaEmbedding edited #62
  • Mar 31 06:20
    YodaEmbedding closed #62
  • Mar 31 06:20
    YodaEmbedding edited #62
  • Mar 31 06:20
    YodaEmbedding opened #62
  • Mar 31 04:05
    karbassi locked #60
  • Mar 22 13:33
    Tobida closed #60
  • Mar 22 13:32
    Tobida commented #60
  • Mar 21 21:17
    bobwhitelock commented #60
  • Mar 21 08:11
    Tobida opened #60
  • Mar 17 09:28
    ermats commented #59
  • Mar 16 18:12
    karbassi closed #59
  • Mar 16 18:12
    karbassi commented #59
  • Mar 16 09:37
    ermats opened #59
  • Mar 15 22:44
    arcturus140 commented #6
  • Mar 15 19:22
    farvardin commented #8
  • Mar 12 00:23
    arcturus140 closed #58
  • Mar 11 09:53
    arcturus140 opened #58
  • Mar 03 19:46
    Rudy96 closed #57
Ingo Karkat
@inkarkat
No, as _listrenders the task numbers based on the passed lines, that does not work; the numbering would be off. However, because completely empty lines are suppressed, blanking out those lines that you don't want (but keeping the newline to maintain the right numbering) will do what you want.
Silas
@silasdb
Thanks for the tips. My two add-ons are almost complete. One is just a clone of the "due" add-on, but it is written in pure bash (the original one is written in python). It is nice give it a different name, right?
Ingo Karkat
@inkarkat
If your due add-on has (more or less) the same functionality as the original Python one, I would keep the name; in the end, what's most important is how you best remember the add-on name. The add-on directory also lists several alternatives with the same name.
Silas
@silasdb
All right. Thanks!
Silas
@silasdb

No, as _listrenders the task numbers based on the passed lines, that does not work; the numbering would be off. However, because completely empty lines are suppressed, blanking out those lines that you don't want (but keeping the newline to maintain the right numbering) will do what you want.

I was wondering how I can use that. I cannot pass lines to _lines via stdin. Should I have to create a temporary files with the lines I want to output via _list?

Silas
@silasdb
_format '' ''?
Silas
@silasdb
this works :-) thanks :-)
Ingo Karkat
@inkarkat
Yes, _format() is invoked by _list(), too; just the summary footer is missing. You should be able to avoid using a temporary file (though that certainly is not too bad, neither). Todo files aren't that large; it should comfortably fit into memory, so holding the (filtered) contents in a Bash variable (and then echoing that into _list() should be possible.
Robin
@ransome1
Hi there. A couple of month ago I switched to Linux and just couldn't find a todo.txt app that I liked. So I sat down and tried to build my own and after putting quite some work into it I think it would be a waste not to share it with the community. Please feel free to try it out: https://github.com/ransome1/sleek
Maciej Łoziński
@loziniak
It's kinda ironic that it's made in electron :-)
Btw nice interface!
Robin
@ransome1
I guess you're referring to the duality between the overhead of electron to the minimal concept of todo.txt? Then yes, you're right, but Javascript, HTML and CSS are the only languages I speak :D
Robin
@ransome1
but as for my defence: My code is just a couple of kilobyte and the app runs fluently even on my good ole entry level laptop from 2007
jason-mehmel
@jason-mehmel
@ransome1 Really elegant app! I've got a few feature ideas, do you want them here or on the github?
Robin
@ransome1
@jason-mehmel would love to hear your idea. post it whereever it suits you best
jason-mehmel
@jason-mehmel
I posted it as an issue on the github but I'll also say it here: stacking filters? Currently it seems like I can only filter by one context or tag at a time, but I'd love to be able to stack them. (@ 1_inbox and +car for example)
Robin
@ransome1
You can stack filters already, but the addition of filters will add new items, there is no exclusion. And I think that is what you're looking for. As I understand you want to select a filter to limit the todos to all items that include that one filter. And in a next step you want to add second or third filter that will break those items already filtered further down.
Which makes sense to me
right now those multiple filters are connected with OR and you basically need the connection to be and AND one, right?
jason-mehmel
@jason-mehmel
Correct. I'm looking for multiple filters to narrow, not add. I do see now that adding multiple filters shows the content that corresponds to at least one of the multiple filters, not just the ones that correspond to both.
In other words, yes. ;)
Also, another issue request which I'll also add to github: sorting filters in the filter tray either by amount of tasks using those contexts/projects, or sorting them alphanumerically. (In the other systems I've used, they sort them alphanumerically, so I've got some 'top level' contexts like [at]1_inbox because then it's the first thing I see on Simpletask Android or on some of the other apps I've used.
Robin
@ransome1
@jason-mehmel ok I figured it out. Would you like to test it? Also: I wasn't sure on if or how the filters should shrink the more you narrow down the amount of visible todos. What's your opinion on that?
jason-mehmel
@jason-mehmel

@ransome1 I went into more detail on the Github issues section, but the short answer is yes, I think the listed filters should shrink based on the amount of visible todos.

Here's my answer! ransome1/sleek#4

Robin
@ransome1
@jason-mehmel Your ideas from both Github topics have been included in https://github.com/ransome1/sleek/releases/tag/v0.2.3. Feel free to try it out
jason-mehmel
@jason-mehmel

@ransome1 Works great! I've also got it via snap on Ubuntu 20.04 so it updated automatically there this morning!

Thank you for this app! I like the fact that it's multi-platform as well; I've been looking to share a todo.txt process with some folks using different OS's. I'll let you know if we discover anything in that process!

jason-mehmel
@jason-mehmel
I'll keep using it, flag any bugs I find, and if I think of more features I'll let you know. Also, please ping me if you want some specific testing.
Robin
@ransome1
@jason-mehmel thanks for your support, Jason. I appreciate it.
jason-mehmel
@jason-mehmel

No problem!

@ransome1 Had another functionality idea, this one around suggested or autocompleted contexts and projects when making new tasks or editing old ones.

Robin
@ransome1
Hi @jason-mehmel, sorry I didn't see your latest comment. But anyway feel free to check a little prototype and let me know if this goes into the right direction: https://github.com/ransome1/sleek/issues/7#issuecomment-736516170
jason-mehmel
@jason-mehmel
It worked great!
If anyone else is reading this, I encourage you to try out @ransome1's Sleek. Particularly with what he's added, it's basically doing all the things I need from a todo.txt app!
jab
@_JuanAlcantara__twitter
Hello everyone here! Just wanted to say @ransome1 I’m really enjoying Sleek. I read the message from @jason-mehmel and decided to try it. Congrats for your work.
👌
Silas
@silasdb
Hi. @inkarkat I finally finished the add-ons I told you about weeks (months?) ago: https://github.com/silasdb/d ; https://github.com/silasdb/due
thanks for the help!
not sure if you (or someone else?) want to add them to todotxt.org add-ons page
Ingo Karkat
@inkarkat

Hey @silasdb; great work, and thank you for publishing the results so that others can reuse them! As a wiki page, the todotxt.org add-ons page should be editable by everyone, so go ahead and add links to your work.

For my own configuration, I've achieved something similar, but I chose a different approach; I have a dateex extension of the date command, and I'm injecting this into all of todo.txt via a shell date() { dateex "$@"; }; export -f date function in todo.cfg. So I don't need a custom add-on like your d (but I think the way you've implement that as a wrapper is quite elegant), but I'm limited to generic dates (due:tomorrow) and cannot use shortcuts like due:+1.

Ingo Karkat
@inkarkat
The obvious thing that I forgot to mention here (but I think had mentioned earlier already) is that for those date expansions to work, I override the built-in add action, and process any m:marker or m:(marker with spaces) syntax by expanding human-readable or relative dates (and also relative task references), via this script. I could directly use my custom dateex there, but by overriding the original date command, it automatically also gets used in other add-ons (for example, I use a schedule command for tasks due in the future).
Silas
@silasdb
@inkarkat this is nice! Didn't you publish it? I was looking for something like that but I don't recall to have seen it in the add-ons page. I'll take a look at that before publishing d. Thanks!
BTW, d is such a small name that is easy to write but difficult to reason about. Do you see any problem with that?
Ingo Karkat
@inkarkat
@silasdb If there's a more descriptive longer name, that would be better. Though it should be trivial to rename, anyway. That's also the problem with my own setup; many of those commands are connected and dependent on each other, so it's hard to use just a few of them without adopting the whole setup. The code has been out there on GitHub for several years; I haven't received much feedback on it yet.
Kevin D. McKibben
@kvnmck1986_twitter
Trying to resolve the following: creation of todo.txt.bak file. I have been using Todo.txt for some time and just started using CLI on Linux Mint XFCE. Since then, the todo.txt.bak get created and IFTTT recurring "appends" are posted to that file and not todo.txt. I am using Dropbox for file location. All other devices, Android, Windows 10 (work), Chrome Extension are then not updated. Is there something to change with the CLI? Thanks in advance!
Robin
@ransome1

Hello everyone here! Just wanted to say @ransome1 I’m really enjoying Sleek. I read the message from @jason-mehmel and decided to try it. Congrats for your work.

thanks for the kind words. If you find any bugs or if you miss an important function, let me know: https://github.com/ransome1/sleek

Ingo Karkat
@inkarkat
@kvnmck1986_twitter Have a look at https://github.com/todotxt/todo.txt-cli/discussions/327; there's a link to a workaround in there. And please comment if you think that such a feature should be built-in.
Arcturus
@arcturus140
is it allowed to have whitespace at the beginning of the line, before the format rules?
Ciarán
@bubonicfred
does anyone know the syntax for exporting to ical using topydo?
matrixbot
@matrixbot
pablito1755 Ciarán (Gitter): I'm not familiar with the ical format, but topydo doesn't appear to have any built in commands to "export" per se. Could something be done with the -F option of the "ls" command to format the output?