Cannot display todo.yml #1486
-
Hi Team, Thanks for the great application. I hope I'm at the right place to ask my question. I'm setting up my wtfutil but the only thing that I could not display is my todo.yml. Here is the snip from my config.yml file:
It does not make a difference whether I use absolute or relative paths in "filename". Here is my todo.yml:
And here is how my dashboard looks like: Any ideas why my todo.yml is not being displayed? I attached my config.yml file (I changed the extension to txt as GitHub does not allow me to upload files with yml extension.) Many thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
So, digging into this, the reason is that we are already assuming that we are in the configuration directory. So specifying '/home/tolga/.config/wtf/todo.yml' comes out as '/home/tolga/.config/wtf/home/tolga/.config/wtf/todo.yml' |
Beta Was this translation helpful? Give feedback.
-
Sean, thanks for the update.
todo.yml is:
Still the "Todo" section in the dashboard is blank. |
Beta Was this translation helpful? Give feedback.
-
Doh!
or
|
Beta Was this translation helpful? Give feedback.
-
We are using yaml for a specific reason (ease of parsing vs writing our own custom parser), but you are right that we probably are over saving items. I created an issue to investigate. |
Beta Was this translation helpful? Give feedback.
-
Hey all, thanks first for wtfutil, absolutely love it! I do have another usecase here: Set an absolute path to the todo.yml so it can sit anywhere and (e.g.) be included in another git repo. My specific case is, that I have a markdown based wiki under ~/notes and would like to have the todo file there too so it can be included in the git repo and shared across systems. Now, I can reach this using a relative path, but that seems... less than elegant... to me. Why not just accept absolute paths here? EDIT: sure, symlinking works also. maybe it's a moot point. |
Beta Was this translation helpful? Give feedback.
We are using yaml for a specific reason (ease of parsing vs writing our own custom parser), but you are right that we probably are over saving items. I created an issue to investigate.