Plaintasks seems to also require that the path has a trailing /. When you drag and drop a path onto TaskPaper it will automatically create a link. We get support for both relative and absolute paths. So with that in mind paths look pretty much how they look in the terminal. If your path does have a space use \ to escape it.The path continues until a space is encountered.Here’s the regex that I’m using right now and it seems to work well in my files: /(?:^|\s)(\.?\/(?:\\\s|)+)/gi
Instead I think I’m going to follow original advice and follow Plaintasks lead with a few less constraints (until I guess I learn why the constrains where there in the first place). It’s used for all sorts of URL links, not just file system paths. I’ve just started implementing this… but have come to the conclusion that href is to loaded a term. Has anyone ever hard of href being used as a URL scheme? Unless there’s some good reason not to… I’m thinking we could solve relative paths in TaskPaper like this: That got me thinking about how web pages use href for relative paths. But I’d like to avoid specialized syntax if possible. PlainTasks has a special syntax for this, and that’s one solution.
TASKPAPER NVALT HOW TO
It also leaves the problem of how to link to files from TaskPaper with a relative path. That makes them less useful, but more predictable. I think I probably need change this and make file:// URLs absolute to the current file system. But of course that’s problematic too, because currently there’s no way to link to an absolute path on your file system. The problem with file URLs is they are always supposed to be absolute which I think we don’t want in most cases for TaskPaper files.īecause of this I’m interpreting them as always relative (consider the TaskPaper file in which they are embedded as in root folder of file system that they refer to). The current TaskPaper preview should support file:// URLs.
0 kommentar(er)
