I don't think either of these should be falderal's responsibility.
Cat's Eye Technologies
11 years ago
| 177 | 177 | colourization anyway, on the tty check. So maybe look at how `cdiff` allows |
| 178 | 178 | colourized text to be paged, first. |
| 179 | 179 | |
| 180 | ### Support cd'ing to directory containing Falderal file before running tests | |
| 181 | ||
| 182 | 2011-12-01 | |
| 183 | ||
| 184 | For Falderal files which specify implementations of functionalities by shell | |
| 185 | commands, it is useful for them to be able to locate the shell command | |
| 186 | they want to run. If it is not on the search path, the directory in which | |
| 187 | `falderal` is invoked is used as the directory on which relative paths are | |
| 188 | based. | |
| 189 | ||
| 190 | This is less useful than using the directory that the Falderal file is in, | |
| 191 | as the directory on which relative paths are based. So, it would be useful | |
| 192 | to `cd` into that directory before running the tests. Add an option to | |
| 193 | `falderal` to do this automatically, or maybe by default. This would let | |
| 194 | the user invoke `falderal` from any location they like, so long as the | |
| 195 | Falderal document is in the right place. | |
| 196 | ||
| 197 | (This was written against Test.Falderal but similar considerations could | |
| 198 | be made for py-falderal.) | |
| 199 | ||
| 200 | ### Show filenames and implementations in standard failure report | |
| 201 | ||
| 202 | 2011-12-11 | |
| 203 | ||
| 204 | To make the standard failure report more useful, it should show the source | |
| 205 | Falderal document filename(s) in the summary. | |
| 206 | ||
| 207 | 180 | ### Flag invalid sequences of lines as errors |
| 208 | 181 | |
| 209 | 182 | 2011-08-05 |