Message-ID: <CABSksF-YwhK80kDpe2en-6X_vZ37Luz3k+t6BoO5+HSzvg5ENA@mail.gmail.com>
Date: 2015-04-20T15:04:23Z
From: Paul Bivand
Subject: Smart detection of wrap width?
In-Reply-To: <D15A5E1D.125F59%macqueen1@llnl.gov>
On Mon, Apr 20, 2015 at 10:59 AM, MacQueen, Don <macqueen1 at llnl.gov>
wrote:
> I'm glad it's helpful!
>
> Defining it and then invoking it in ~/.Rprofile would work, but then
> you will need to be careful about managing both ./.Rprofile and
> ~/.Rprofile files. If you have one of the former, then the latter
> does not get sourced at startup (see ?Startup). Of course, you can
> put source('~/.Rprofile') in a local ./.Rprofile to take care of
> that if you want.
>
> But in the long run, it would be a better practice to put personal
> helper functions like this in a package and then load it in your
> .Rprofile file(s). Most of my ./.Rprofile files have
>
> require(rmacq)
> setwid()
>
> in them (along with whatever other directory-specific startup
> actions I want). The more personal helper functions you have, the
> more valuable it will be to put them in a package instead of
> defining them in ~/.Rprofile.
Thanks, I'll keep it in mind, Don. I'm sort of careening at breakneck
speed into time series and R, so I know I'll be rough around the edges
for a while, with the more refined aspects such as sensible
organization of customizations following in the rear. Not ideal, I
know, but 'tis what it is...