I have a configuration goal in mind, and I'd love to have some canto gurus (power users accepted if fit :p ) tell me if it is easy to achieve this goal with existing 0.7.10 canto, or if I would best wait for the next major release, or switch to another tool. I also have a few questions about canto's design.
So, here we go for the description of what conf I'd like: 1. No story should ever be deleted without a being manualy marked deletable. For that, I might add a tag for every story and never_discard("notmarkeddeletable") 2. I should be able to sort stories in three categories, or to leave them untouched until I sort them (I might need new categories overtime). For that, I had a look at tags, but it seems to me the tag flagging is done everytime canto reads stories from disk, hence are not persistant. Did I read correct? 3. I should have some tweaked views, but if done with tag (or something of similar use), it should not be a problem to play with
On Sun, Dec 26, 2010 at 11:20 AM, jhioanez <jhioa...@gmail.com> wrote: > Hi all, mery christmas to the sames.
> I have a configuration goal in mind, and I'd love to have some canto > gurus (power users accepted if fit :p ) tell me if it is easy to > achieve this goal with existing 0.7.10 canto, or if I would best wait > for the next major release, or switch to another tool. I also have a > few questions about canto's design.
> So, here we go for the description of what conf I'd like: > 1. No story should ever be deleted without a being manualy marked deletable. > For that, I might add a tag for every story and > never_discard("notmarkeddeletable") > 2. I should be able to sort stories in three categories, or to leave > them untouched until I sort them (I might need new categories > overtime). > For that, I had a look at tags, but it seems to me the tag flagging is > done everytime canto reads stories from disk, hence are not > persistant. Did I read correct? > 3. I should have some tweaked views, but if done with tag (or > something of similar use), it should not be a problem to play with
Sorry, don't know how this mail gone, so I finish it here: it should not be a problem to play with filters and drawing format codes. 4. I'd like to have all stories mainly sorted according to their provenance feeds (though, filters are looking like to do that).
Now, two questions about canto's behaviour: 1. In a case i have canto-fetch in a cron running it every 10 minutes, and canto left running with the default (5 mins IIRC), will the feeds be fetched 3 times in 30 minutes (so canto-fetch is alone to fetch), or 9 times (canto-fetch+canto process itself?), or whatever? 2. In what case, in normal workflow, are stories deleted? Only when keep limit is reached and then it takes the oldest(s) it can that is not concerned by never_discard()?
Thank you for having read this pieced message (sorry about the partial send), and thank you very much for everyone who participate in canto's development and support, it seems a really great software to me.
