Thank you Peter, that sounds pretty reasonable.
Best,
Tom
On Friday, March 29, 2013, peter dalgaard wrote:
>
> On Mar 28, 2013, at 22:27 , Thomas Adams wrote:
>
> > All,
> >
> > Well to my relief and embarrassment, I discovered my problem. About 5
> weeks
> > ago, I shutdown my computer and move
On Mar 28, 2013, at 22:27 , Thomas Adams wrote:
> All,
>
> Well to my relief and embarrassment, I discovered my problem. About 5 weeks
> ago, I shutdown my computer and moved it. When I reconnected everything I
> apparently plugged my HDMI monitor into the 'wrong' output port without
> realizing
All,
Well to my relief and embarrassment, I discovered my problem. About 5 weeks
ago, I shutdown my computer and moved it. When I reconnected everything I
apparently plugged my HDMI monitor into the 'wrong' output port without
realizing it. So, on a whim, just now, I made the switch to the other p
Luca,
Thank you for the suggestion; I do have an Nvidia graphics card and I am
using the Nvida driver; still searching for a solution, quite odd...
Tom
On Thu, Mar 28, 2013 at 12:28 PM, Luca Nanetti wrote:
> Thomas,
> any chance that you could have problems with your graphic driver? For
> insta
Thomas,
any chance that you could have problems with your graphic driver? For
instance, if you have an Nvidia graphic card, I would recommend switching
from the 'nouveau' driver to the official Nvidia one.
Kind regards,
luca
[[alternative HTML version deleted]]
__
On Mar 27, 2013, at 19:26 , Thomas Adams wrote:
> Peter,
>
> Thank you.
>
> When I run: X11(width=7, height=7), I get the same full-screen graphics
> device window.
> Running dev.list() gives me X11cairo
> Running system("xdpyinfo") looks reasonable
>
> I tried running options(device="x11")
ote:
> >>
> >>> Any chance that you made an earlier call to par() resetting cex in your
> >>> session? I just had that happen.
> >>>
> >>> John Kane
> >>> Kingston ON Canada
> >>>
> >>>
> >>>> --
ession? I just had that happen.
>>>
>>> John Kane
>>> Kingston ON Canada
>>>
>>>
>>>> -Original Message-
>>>> From: tea...@gmail.com
>>>> Sent: Tue, 26 Mar 2013 10:15:33 -0400
>>>> To: r-help@r-pr
ssage-----
>>> From: tea...@gmail.com
>>> Sent: Tue, 26 Mar 2013 10:15:33 -0400
>>> To: r-help@r-project.org
>>> Subject: [R] Odd graphic device behavior
>>>
>>> I'm experiencing odd graphics device behavior running R 2.15.3 on Ubuntu.
&g
; -Original Message-
> > From: tea...@gmail.com
> > Sent: Tue, 26 Mar 2013 10:15:33 -0400
> > To: r-help@r-project.org
> > Subject: [R] Odd graphic device behavior
> >
> > I'm experiencing odd graphics device behavior running R 2.15.3 on Ubuntu.
> &
Any chance that you made an earlier call to par() resetting cex in your
session? I just had that happen.
John Kane
Kingston ON Canada
> -Original Message-
> From: tea...@gmail.com
> Sent: Tue, 26 Mar 2013 10:15:33 -0400
> To: r-help@r-project.org
> Subject: [R] Odd
I'm experiencing odd graphics device behavior running R 2.15.3 on Ubuntu.
Regardless of what I try like:
require(stats)
plot(cars)
lines(lowess(cars))
plot(sin, -pi, 2*pi)
for example, the graphics device fills the entire screen with the graphic
and a very large font. When I shrink the graphics d
12 matches
Mail list logo
