Hi Jeff - thanks. I forgot to add originally that I use putty as a terminal for the old version of R I mentioned as well as the new, and also I can see the same issue with the new version of R when run in xterm. I?ve messed with some of the options putty offers and it doesnt change the new R behavior. Also this behavior does not occur at the shell prompt, or in other prompts, like interactive python. So while I agree that it doesnt seem like an R issue on the surface, it only happens in R as far as I can tell! On Mon, Nov 5, 2018 at 2:44 PM Jeff Newmiller <jdnewmil at dcn.davis.ca.us> wrote:> I am pretty sure this is not an R issue (so it is off-topic here)... it > sounds like the kind of misconfiguration that was common back when there > were dozens of competing terminal manufacturers and the solution was to > configure your Linux TERM variable and/or terminfo database to match up > with your terminal emulator program (e.g. [1]). With modem autocofiguration > on the OS side it may be as simple as changing your terminal emulator > settings and logging in again... or not. > > [1] https://www.tldp.org/HOWTO/Text-Terminal-HOWTO-7.html > > On November 5, 2018 1:53:42 PM PST, Ben <bfcrap at gmail.com> wrote: > >Hi all - > > > >I?m seeing a weird issue. I?m running R v3.3.2 on CentOS 7 Linux. The > >behavior of the command prompt when entering very long commands on a > >single > >line is strange compared to my use in older versions. Specifically, > >after > >hitting enter, the prompt continues on the line immediately after the > >previous prompt. In other words, it skips back up past all of the > >previous > >input on that one wrapped line. > > > >One way to see it clearly is to force it to display many newline > >characters > >with ctrl-v ctrl-j and then hit enter. In bash and my earlier R > >console, > >the new prompt is right at the end of the newline sequence, but in the > >new > >versions the prompt jumps back up to the line after the previous > >prompt. > > > >If anyone has ideas on whats going on, I?d love to hear them! Thanks, > > > >Ben > > > > [[alternative HTML version deleted]] > > > >______________________________________________ > >R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > >https://stat.ethz.ch/mailman/listinfo/r-help > >PLEASE do read the posting guide > >http://www.R-project.org/posting-guide.html > >and provide commented, minimal, self-contained, reproducible code. > > -- > Sent from my phone. Please excuse my brevity. >[[alternative HTML version deleted]]
Well, you may or may not have ruled out the Putty settings (your hand waving is a bit hard for me to interpret), and there may still be host side terminal settings involved, or if you compiled R yourself you may have setup something wrong. However, in either case the R-sig-fedora mailing list would be more appropriate than R-help for discussing configure options under Red Hat-derived distributions. On November 5, 2018 3:12:59 PM PST, Ben <bfcrap at gmail.com> wrote:>Hi Jeff - thanks. I forgot to add originally that I use putty as a >terminal for the old version of R I mentioned as well as the new, and >also >I can see the same issue with the new version of R when run in xterm. >I?ve >messed with some of the options putty offers and it doesnt change the >new R >behavior. Also this behavior does not occur at the shell prompt, or in >other prompts, like interactive python. So while I agree that it doesnt >seem like an R issue on the surface, it only happens in R as far as I >can >tell! > > >On Mon, Nov 5, 2018 at 2:44 PM Jeff Newmiller ><jdnewmil at dcn.davis.ca.us> >wrote: > >> I am pretty sure this is not an R issue (so it is off-topic here)... >it >> sounds like the kind of misconfiguration that was common back when >there >> were dozens of competing terminal manufacturers and the solution was >to >> configure your Linux TERM variable and/or terminfo database to match >up >> with your terminal emulator program (e.g. [1]). With modem >autocofiguration >> on the OS side it may be as simple as changing your terminal emulator >> settings and logging in again... or not. >> >> [1] https://www.tldp.org/HOWTO/Text-Terminal-HOWTO-7.html >> >> On November 5, 2018 1:53:42 PM PST, Ben <bfcrap at gmail.com> wrote: >> >Hi all - >> > >> >I?m seeing a weird issue. I?m running R v3.3.2 on CentOS 7 Linux. >The >> >behavior of the command prompt when entering very long commands on a >> >single >> >line is strange compared to my use in older versions. Specifically, >> >after >> >hitting enter, the prompt continues on the line immediately after >the >> >previous prompt. In other words, it skips back up past all of the >> >previous >> >input on that one wrapped line. >> > >> >One way to see it clearly is to force it to display many newline >> >characters >> >with ctrl-v ctrl-j and then hit enter. In bash and my earlier R >> >console, >> >the new prompt is right at the end of the newline sequence, but in >the >> >new >> >versions the prompt jumps back up to the line after the previous >> >prompt. >> > >> >If anyone has ideas on whats going on, I?d love to hear them! >Thanks, >> > >> >Ben >> > >> > [[alternative HTML version deleted]] >> > >> >______________________________________________ >> >R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see >> >https://stat.ethz.ch/mailman/listinfo/r-help >> >PLEASE do read the posting guide >> >http://www.R-project.org/posting-guide.html >> >and provide commented, minimal, self-contained, reproducible code. >> >> -- >> Sent from my phone. Please excuse my brevity. >>-- Sent from my phone. Please excuse my brevity.
>>>>> Jeff Newmiller >>>>> on Mon, 5 Nov 2018 18:47:00 -0800 writes:> Well, you may or may not have ruled out the Putty settings > (your hand waving is a bit hard for me to interpret), and > there may still be host side terminal settings involved, > or if you compiled R yourself you may have setup something > wrong. However, in either case the R-sig-fedora mailing > list would be more appropriate than R-help for discussing > configure options under Red Hat-derived distributions. Also, why are you using R 3.3.2 when current R is 3.5.1 ? Even if there might have been problematic behavior of R's "console" in that version of R, we will not be able to improve that version retrospectively... but rather the next version of R. So please update your R to 3.5.1 (or even "R-devel" ideally, for checking about potential bugs). > On November 5, 2018 3:12:59 PM PST, Ben <bfcrap at gmail.com> > wrote: >> Hi Jeff - thanks. I forgot to add originally that I use >> putty as a terminal for the old version of R I mentioned >> as well as the new, and also I can see the same issue >> with the new version of R when run in xterm. I?ve messed >> with some of the options putty offers and it doesnt >> change the new R behavior. Also this behavior does not >> occur at the shell prompt, or in other prompts, like >> interactive python. So while I agree that it doesnt seem >> like an R issue on the surface, it only happens in R as >> far as I can tell! >> >> >> On Mon, Nov 5, 2018 at 2:44 PM Jeff Newmiller >> <jdnewmil at dcn.davis.ca.us> wrote: >> >>> I am pretty sure this is not an R issue (so it is >>> off-topic here)... >> it >>> sounds like the kind of misconfiguration that was common >>> back when >> there >>> were dozens of competing terminal manufacturers and the >>> solution was >> to >>> configure your Linux TERM variable and/or terminfo >>> database to match >> up >>> with your terminal emulator program (e.g. [1]). With >>> modem >> autocofiguration >>> on the OS side it may be as simple as changing your >>> terminal emulator settings and logging in again... or >>> not. >>> >>> [1] >>> https://www.tldp.org/HOWTO/Text-Terminal-HOWTO-7.html >>> >>> On November 5, 2018 1:53:42 PM PST, Ben >>> <bfcrap at gmail.com> wrote: >Hi all - >>> > >>> >I?m seeing a weird issue. I?m running R v3.3.2 on >>> CentOS 7 Linux. >> The >>> >behavior of the command prompt when entering very long >>> commands on a >single >line is strange compared to my >>> use in older versions. Specifically, >after >hitting >>> enter, the prompt continues on the line immediately >>> after >> the >>> >previous prompt. In other words, it skips back up past >>> all of the >previous >input on that one wrapped line. >>> > >>> >One way to see it clearly is to force it to display >>> many newline >characters >with ctrl-v ctrl-j and then >>> hit enter. In bash and my earlier R >console, >the new >>> prompt is right at the end of the newline sequence, but >>> in >> the >>> >new >versions the prompt jumps back up to the line >>> after the previous >prompt. >>> > >>> >If anyone has ideas on whats going on, I?d love to hear >>> them! >> Thanks, >>> > >>> >Ben >>> > >>> > [[alternative HTML version deleted]] >>> > >>> >______________________________________________ >>> >R-help at r-project.org mailing list -- To UNSUBSCRIBE and >>> more, see >https://stat.ethz.ch/mailman/listinfo/r-help >>> >PLEASE do read the posting guide >>> >http://www.R-project.org/posting-guide.html >and >>> provide commented, minimal, self-contained, reproducible >>> code. >>> >>> -- >>> Sent from my phone. Please excuse my brevity. >>> > -- > Sent from my phone. Please excuse my brevity. > ______________________________________________ > R-help at r-project.org mailing list -- To UNSUBSCRIBE and > more, see https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide > http://www.R-project.org/posting-guide.html and provide > commented, minimal, self-contained, reproducible code.