similar to: par$csi

I'm getting a lot of warning having to do with setting graphic parameters. I don't recall actually setting any of these, so I would guess they are being set by something I am calling. Has anyone already figured out where this is happening? Paul Gilbert _____ All dse3 tests ... ok All dse4 tests ...Warning: skipping test 4 (requires stepwise). ok dse2 graphics tests ...completed dse3

I often use something like old.par <- par(set someting) on.exit(par(old.par)) but in R 1.7.0. I now get warnings: > old.par <- par() > par(old.par) Warning messages: 1: parameter "cin" can't be set in: par(args) 2: parameter "cra" can't be set in: par(args) 3: parameter "csi" can't be set in: par(args) 4:

>>>>> "Marc" == Marc Schwartz <mschwartz@medanalytics.com> >>>>> on Wed, 13 Nov 2002 11:01:49 -0600 writes: Marc> Marc Schwartz wrote: >> SNIP >> >> I am guessing that this may be the result of par("ylog") >> and par("xlog") being read only and perhaps impacting the >>

Hi, I am trying to infer the dimension of an opened bitmap (png, jpeg, bitmap device...) from par() parmeters. From the help on par(), I found that: > dim <- c(400, 200) > png("foo.png", width=dim[1], height=dim[2]) > dim2 <- par("din") * par("cra") / par("cin") > dev.off() > dim2 [1] 399.9999 199.9999 I've tried the above on

Dear all, the help of par() claims that cin and cra are c(width, height) but it appears to be rather c(height, width) Best regards Jens Oehlschl?gel > plot.new() > strheight("W", unit="inches") [1] 0.1354167 > par("cin") [1] 0.1354167 0.1875000 > version _ platform i386-pc-mingw32 arch i386 os mingw32

Hi, I seem to have broken the pdf device on my installation. I'm running R 1.6.1 under Apple's X11 on darwin 6.3. Running the following commands straight after starting R (and without touching 'par') gives different results - the png file looks fine but I'm missing axes and labels on the pdf. If I try and print the pdf, axes and labels appear but with text characters as

I use R on linux and I go through exceed from a windows machine. Depending on the amount of plots I do on a screen, sometimes the numbers on the vertical axis of the plots don't show up. I tried infinite of combinations of mar and cex but nothing helps. Yet, if instead of shooting the graphic upto the screen, I send it to a pdf file or a postscript file, the numbers on the vertical axis of

"contour" can't return a list of contours (it would be nice) "arrows" has different options from S-PLUS (no "open" or "rel" options, no "lwd" parameter or graphics parameter pass-through; "size" in S corresponds to "length" in R). [I know we needn't follow S-PLUS syntax slavishly, but it would be nice at least to

On my home (Windows 98) machine I find: > par()$cra [1] 42 16 > par()$csi [1] 0.1666667 > On my work machine I believe I had par()$cra [1] 17 16 So it looks as though R is reading the width wrongly, and that it is the width that is somehow used to determine the plot character size. Incidentally I noted Brian's comment that R had misread his character dimension information wrongly.

ssh already restores all TTY flags on exit: https://github.com/openssh/openssh-portable/blob/V_9_8_P1/sshtty.c#L56-L78 It's possible there are some exit cases that are not hitting the leave_raw_mode(), but if so then they aren't obvious. On Sun, 7 Jul 2024, Johannes Altmanninger wrote: > Some terminals support CSI u style encoding of keystrokes, typically via > the Kitty keyboard

On Mon, 8 Jul 2024 at 11:58, Damien Miller <djm at mindrot.org> wrote: > ssh already restores all TTY flags on exit: This isn't a TTY flag, it's a terminal mode enabled via an escape sequence, there's actually multiple modes involved (CSI u as in the subject), but xterm also supports "modifyOtherKeys" and Vim for example will pick depending what the terminal reports

Some terminals support CSI u style encoding of keystrokes, typically via the Kitty keyboard protocol[1]. Program wishing to receive this encoding need to send a sequence like "CSI > 5 u" to enable it. Imagine a process tree like xterm -> bash -> ssh -> foo where foo is any program that enables CSI u mode (such as a newfangled shell or text editor). If the network

Hi Joe, On Wed, Mar 29, 2023, 12:55 PM Joe Julian <me at joejulian.name> wrote: > I was chatting with Humble about the removed gluster support for > Kubernetes 1.26 and the long deprecated CSI driver. > > I'd like to bring it back from archive and maintain it. If anybody would > like to participate, that'd be great! If I'm just maintaining it for my > own use,

Looking at this code, it's way more than I was looking for, too. I just need a replacement for the in-tree driver. I have a volume. I have about a half dozen pods that use that volume. I just need the same capabilities as the in-tree driver to satisfy that need. I want to use kadalu to replace the hacky thing I'm still doing using hostpath_pv, but last time I checked, it didn't build

I was chatting with Humble about the removed gluster support for Kubernetes 1.26 and the long deprecated CSI driver. I'd like to bring it back from archive and maintain it. If anybody would like to participate, that'd be great! If I'm just maintaining it for my own use, then so be it. ? It has been archived for 4 years, so it's going to need a bit of work. I also don't

hi, im all new to linux. i am running ubuntu as my windows was causing me problems so i decided to go to linux. but i bought csi:dark motives before this happened and now i cant play it. i can install it using wine but when it nears to the end of the installation it says "run-time error '429'. ActiveX component cant't cretae object. please can someone tell me what im doing wrong

Greetings, I am using samba-3.0.1pre3-1, and have noticed that the "force group" and "force user" option no longer seems to work. In spite of the option being set, the files copied are set to the current users user and primary group. Am I missing something with regards to how this is supposed to work or is this a bug? This is one of my share definitions for a team of

width <- 7 height <- 5 # create whatever device type # and have cex=1 before setting par(mai=) windows(width=width, height=height, rescale="R") oldmai <- par("mai") par(cex=1) par(mai=oldmai) plot.new() par(usr=c(0,2,0,2)) par(cex=2) par1 <- par() text(1,1,"there is hardly anything i know for sure\nneither of the future nor of the past\nnor should i know what

I have my DSE library working fairly well now with 0.62.1. It required a few changes because of the changes to R INSTALL and "xxx<-" functions. I would like to tar up a new version soon but 1/ for testing I have been using a kludge in .First.lib to select the first element of section - since I happen to know that is the element I need given the way I have $RLIBS set. This argument

--==_Exmh_1801894504P Content-Type: text/plain; charset=us-ascii Dear R folks, Initially I had a plotting routine using logarithmic y-axes that failed after repeated calls if I tried to restore the graphical parameters (which I wanted to do because I used `layout' within the routine. I tried to isolate the problem and found out that the following code with logarithmic axis is sufficient for