[R] error message for every parenthesis
kerin at usc.edu
Tue Feb 16 20:37:40 CET 2016
Thank you both for your quick reply!
I did install 3.2.3, it appears that was just a typo in my earlier message.
Yes! deleting the workspace and history seems to correct the problem. I
will also not continue the practice of saving my workspace. I have also now
downloaded R studio. Thank you for the tip. The interface is nice, and I
hope this will help my transition over to R. I'll have to send my thanks
to Garrett as well. :)
I appreciate your help with this, and your patience with a R newbie!
On Tue, Feb 16, 2016 at 3:42 AM, Michael Dewey <lists at dewey.myzen.co.uk>
> Dear Tara
> 1 - why did you install 3.2.1 when 3.2.3 is the latest version
> 2 - what happens if you delete .RData and .Rapp.history from your
> 3 - you do have a function try as it is part of R
> On 16/02/2016 02:49, Tara Kerin wrote:
>> I seem to be having the same problem Garrett (below) had in 2009.
>> However, I do not have functions named try written in my active code.
>> In fact, I don't have any of my own functions written at all yet. I
>> did just install version 3.2.1 today, and the errors started after
>> that. Please advise!
>> Thank you,
>> Tara Kerin
>> An example from my GUI is below:
>> [Workspace restored from /Users/tarakerin/.RData]
>> [History restored from /Users/tarakerin/.Rapp.history]
>> Error in try(gsub("\\s+", " ",
>> paste(capture.output(print(args(library))), :
>> unused argument (silent = TRUE)
>> On 7/13/2009 12:35 PM, Garrett Grolemund wrote:
>>> * Whenever I type a parenthesis immediately following a word (as if I'm
>> *>* entering a function) R displays the following error
>> *> >* Error in try(gsub("\\s+", " ",
>> paste(capture.output(print(args(try))), :
>> *>* unused argument(s) (silent = TRUE)
>> *>>* try(
>> *> >* The above is pasted from my R console. The error appears above the
>> *>* because it appears immediately upon typing the parenthesis. It does
>> *>* wait until I try to execute the command. This happens for every
>> *>* I can finish typing the function and execute it. But these error
>> *>* make it difficult to debug my code. In particular, if I have
>> *>* = recover) set, the above crashes R.
>> *> >* I can avoid the error by typing the parentheses first and then
>> moving the
>> *>* cursor back to type in the word. This error displays on the console
>> *>* I'm typing in the console or in an open document window.
>> *> >* I'm using the mac GUI for R. The error only occurs on my Macbook
>> (OS X
>> *>* 10.5.7), which I bought a few months ago. It has occurred every
>> time I use
>> *>* R on this computer. It has happened with R 2.8 and now R 2.91.
>> *> >* Any idea what may be going on?
>> Presumably this has something to do with command completion or argument
>> hints. From the "silent = TRUE" error, and your example, I would guess
>> you have a function named try(), and the GUI is finding yours instead of
>> the one in the base package.
>> The GUI shouldn't do that, it should look in the right place, but as a
>> workaround, you could remove your function named "try", and call it
>> something else.
>> Duncan Murdoch
>> [[alternative HTML version deleted]]
>> R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see
>> PLEASE do read the posting guide
>> and provide commented, minimal, self-contained, reproducible code.
[[alternative HTML version deleted]]
More information about the R-help