Crazy canto-next behavior: always overwrite my config file with default version configs. about canto-next HOT 4 CLOSED

Canto can't separate feeds into a separate file, but there should be no reason whatsoever you should be hand-editing your config.

Either canto-remote addfeed without canto-curses or the :add command inside canto-curses is the only supported way to add single feeds. See http://codezen.org/canto-ng/manual/#Adding-feeds

What I think is likely happening is that some section in the config file is bad JSON and the section is then being replaced, which shouldn't ever happen if you're managing the config through the interface instead of an editor.

If you're not hand-editing, or the problem doesn't stop, or you think I'm in error, I'd suggest running canto-daemon -v (you may have to kill it first with canto-remote kill ) and canto-curses -v and attaching the logfiles in ~/.canto-ng

from canto-next.

wow, really bad news, manually add lot of feeds through interface is really painful. Like on shit Windows, click, click, click ..... damn. Anyway, I decide to use old version Canto. (No way to export old version Canto feeds, then import to Canto-next is really painful.)

from canto-next.

You mean like

(old) canto -o > feeds.opml

and

canto-remote import feeds.opml

Bad news... it's trivial.

from canto-next.

Good, this is what I want. thanks

from canto-next.