Skip to content

non-interactive error in .First function

4 messages · Brian Chalfant, Jeff Newmiller

#
Suggestions:
a) Don't post in HTML format... your code appears corrupt.
b) Don't do this. Read the Note in ?.First
On Tue, 24 Jun 2014, Brian Chalfant wrote:

            
---------------------------------------------------------------------------
Jeff Newmiller                        The     .....       .....  Go Live...
DCN:<jdnewmil at dcn.davis.ca.us>        Basics: ##.#.       ##.#.  Live Go...
                                       Live:   OO#.. Dead: OO#..  Playing
Research Engineer (Solar/Batteries            O.O#.       #.O#.  with
/Software/Embedded Controllers)               .OO#.       .OO#.  rocks...1k
#
(a) Sorry, that was my first post.? I'll be sure to plain text from here on.

(b) Hmm.? "It is not intended that there be interaction with the user during startup code.? Attempting to do so can crash the R process, especially so prior to R 3.0.2."? I had been using this with <3.0.1. with no problems or error messages at all.? What changed?? If I want to risk crashing, is there a workaround?

Thanks much -
Brian


Brian Alexander Chalfant
Research Assistant & PhD student
University of Pittsburgh
www.pitt.edu/~bac84
bac84 at pitt.edu
724.984.7758
#
Howdy -

I'm wondering if there is a way to force an R dialog window to "the front" in a Windows OS.? In particular, I defined a .Last function in my Rprofile.site file that consists only of the updateR() function so as to check for R updates on close.? However, the dialog window for this pops up behind the RStudio window, which I don't like.

Any advice would be much appreciated.

Thanks -
Brian


Brian Alexander Chalfant
Research Assistant & PhD student
University of Pittsburgh
www.pitt.edu/~bac84
bac84 at pitt.edu
724.984.7758