On 23.02.15 21:58, Joao S. O. Bueno wrote: > That happens all the time, and is this use case that should possibly > be addressed here - maybe > something as simple as adding a couple of paragraphs to different places > in the documentation could mitigate the issue. (in contrast to make a > tons of otherwise valid code > to become deprecated in a couple releases). The problem is that the user don't know that he should read the documentation. It just find that his script works with "C:\sample.txt", but doesn't work with "D:\test.txt". He has no ideas what happen.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4