Hi,
Of course we all want better error messages. What's the point of trying
to make a case against that?
Even the cd Unix command (a shell built-in in that case) -- and Unix
commands are known for their lack of verbosity and minimalist error
messages -- manages to report something informative:
On Fri, Jan 11, 2013 at 10:40 PM, Prof Brian Ripley
wrote:
> On 11/01/2013 20:22, Henrik Bengtsson wrote:
>>
>> Below is a patch for setwd() to show path in error message. Current
>> it just gives error messages such as:
>>
>> Error in setwd(libdir) : cannot change working directory
>>
>> with th
On 11/01/2013 20:22, Henrik Bengtsson wrote:
Below is a patch for setwd() to show path in error message. Current
it just gives error messages such as:
Error in setwd(libdir) : cannot change working directory
with the patch it should (read untested) give:
Error in setwd(libdir) : cannot change
Below is a patch for setwd() to show path in error message. Current
it just gives error messages such as:
Error in setwd(libdir) : cannot change working directory
with the patch it should (read untested) give:
Error in setwd(libdir) : cannot change working directory to 'path/that/fails/'
PATC
