similar to: bug in menu, readline

Dear R developers, I have found the following bug with readline() in R 0.63.3: if you execute the menu-function and then the readline() function, then readline() prompts "Selection:" > a <- readline() hello > a [1] "hallo" > a <- menu(c("a", "b"), title="bitte:") bitte: 1:a 2:b Selection: 2 > a <- readline() Selection:

Hi. WISHLIST: Regardless on console, I'd like to be able to timeout a call to readline()/file("stdin", blocking=TRUE) via setTimeLimit. OBSERVATION: On Windows Rterm as well as plain R on Linux, setTimeLimit() does not momentarily interrupt from stdin, but only after hitting RETURN. A few examples: timeout00 <- function() { setTimeLimit(elapsed=5); Sys.sleep(10); }

I built R-0.60.1 using SGI's cc and f77 compilers, but it dumped core in scan.c: ConsoleGetchar(), so I waited for 0.61. This had the same problem, which appears to be fixed by the following patch: *** scan.c.000 Fri Nov 21 00:06:43 1997 --- scan.c Wed Dec 31 12:11:05 1997 *************** *** 27,33 **** static char ConsoleBuf[CONSOLE_BUFFER_SIZE]; static char *ConsoleBufp; ! static

A few days ago on R-help I asked about a cross-platform timeout version of readline(). Some suggestions, but only partial joy so far. I can get the Gnu bash 'read -t ...' to work in Windows by using the 'bash -c ' construct, but then R's system() function does not seem to allow this to pass through. Similarly a Perl and Free Pascal routine that I tried, the latter being a

On Sat, Oct 17, 2015 at 8:24 PM, Pasi Parviainen via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 14.10.2015 23:36, Chandler Carruth via llvm-dev wrote: > >> * **Be welcoming.** We strive to be a community that welcomes and supports >> people of all backgrounds and identities. This includes, but is not >> limited >> to members of any race,

On Thu, 2015-04-02 at 16:12 -0400, Lamar Owen wrote: > On 04/02/2015 03:55 PM, Always Learning wrote: > > Is there a commercial motive for this 'unwelcome by most' change ? > > Do you have data to prove that it is unwelcome by most? Although most people in the world will privately complain the vast majority do not complain in public. Where is your contrary evidence that

On Feb 17, 2014, at 5:13 AM, Kostya Serebryany <kcc at google.com> wrote: > Then my question: will there be any objection if I disentangle AsanCoverage from ASan and make it a separate LLVM phase with the proper clang driver support? > Or it will be an unwelcome competition with the planned clang coverage? I don’t view it as a competition, but assuming that we both succeed in our

Dear friends - below is a subset of a much larger material showing two ways of generating two "lines". The intention is to have the colour reflect a variable, pH, but the legend is disturbed. The little part marked "3" above the colour scale is unwelcome. Why did it appear? How could I avoid it? I'm on Windows 7, R version 3.4.1 (2017-06-30) -- "Single

Hi, we?re currently seeing trouble with klibc on several architectures, cf. http://www.zytor.com/pipermail/klibc/2012-May/003277.html and armhf is being one of them, when using klibc to compile mksh-static with it. I can look into it (asked zumbi for build-deps in a sid chroot on harris already), but not 100% sure I?ll find it, so more eyes on klibc would not be unwelcome ;-) maks, does klibc

Hi Tanya, > > * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't > > that be llvm-1.9? > > We have always labeled the dir just llvm which is fine. If you build > llvm it will know its version 1.9. I think that's missing the point. Convention is the foo-4.2.tar unpacks to a directory called foo-4.2. It's a unwelcome surprise when it

>>> * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't >>> that be llvm-1.9? >> >> We have always labeled the dir just llvm which is fine. If you build >> llvm it will know its version 1.9. > > I think that's missing the point. Convention is the foo-4.2.tar unpacks > to a directory called foo-4.2. It's a

Hi, when I still had ISDN, I was using Hangup(causecode) to send e.g. "Wrong number" to unwelcome callers. Meanwhile, I am only using SIP providers (no PSTN lines any more) and I would like to do similar, i.e. send specific SIP headers. Besides "wrong number", I would especially like to send 302 temp moved with a specified address to deflect certain calls. Is there any way to

On Thu, April 2, 2015 2:55 pm, Always Learning wrote: > > On Thu, 2015-04-02 at 13:08 -0500, Johnny Hughes wrote: > >> CentOS releases are NOT the same as EUS and have never been .. yet that >> seems to be what people expect. We want there to be no doubt on this >> issue. > > Is there a commercial motive for this 'unwelcome by most' change ? > > If

Good afternoon everyone, hope you all are well. Apologies if this is considered unwelcome -- asking oracle question in centos group -- but a lot of centos Vs oracle is going on here so hoping this will not be shot down. I am unable to access any of the oracle documentation I need, as it keeps on asking for support identifier number, which, as far as I can tell, is only available if I purchase an

Regarding performance, I've made a simple coverage with counters and compared it with AsanCoverage. AsanCoverage produces code like this: mov 0xe86cce(%rip),%al test %al,%al je 48b4a0 # to call __sanitizer_cov ... callq 4715b0 <__sanitizer_cov> A simple counter-based thing (which just increments counters and does nothing else useful) produces this: incq 0xe719c6(%rip) The

Hello, On Thu, 9 May 2019 09:14:13 +0300 Aki Tuomi via dovecot wrote: > On 9.5.2019 9.01, Christian Balzer via dovecot wrote: > > Hello, > > > > Both the examples on the Push Notification wiki page and the XAPS plugin > > docs seem to suggest or state that LMTP/LDA is required. > > It is required. > Thanks for the quick, but unwelcome reply. There's a

It's not just the name of the ISO file. c.f. the VERSION_ID variable in /etc/os-release On Thu, Apr 2, 2015 at 10:52 AM, Always Learning <centos at u64.u22.net> wrote: > > On Wed, 2015-04-01 at 22:54 -0700, John R Pierce wrote: > > > you guys sure get your panties in a bunch over something as silly as the > > iso file name. > > You may wear them, many of us

On 04/02/2015 03:55 PM, Always Learning wrote: > Is there a commercial motive for this 'unwelcome by most' change ? Do you have data to prove that it is unwelcome by most? It is unwelcome by you and a few others I've seen comment; what percentage of the list's subscribers do you suppose that might be? (It is neither welcome nor unwelcome by me, as I've said before.)

On Thu, Apr 2, 2015 at 4:12 PM, Lamar Owen <lowen at pari.edu> wrote: > On 04/02/2015 03:55 PM, Always Learning wrote: > >> Is there a commercial motive for this 'unwelcome by most' change ? >> > > Do you have data to prove that it is unwelcome by most? It is unwelcome > by you and a few others I've seen comment; what percentage of the list's >

On Thu, 4 Feb 2021 12:03:30 +0000 Shamim Shahriar wrote: > Apologies if this is considered unwelcome -- asking oracle question in > centos group -- but a lot of centos Vs oracle is going on here so hoping > this will not be shot down. Speaking for myself only, I have no problem with anyone posting Oracle Linux questions, answers or solutions in this mailing list. I think that as time