Bug 16434 - In the R terminal, right-arrow or Ctrl-E locks out further keyboard input
Summary: In the R terminal, right-arrow or Ctrl-E locks out further keyboard input
Status: NEW
Alias: None
Product: R
Classification: Unclassified
Component: I/O (show other bugs)
Version: R 3.2.0
Hardware: x86_64/x64/amd64 (64-bit) OS X Mavericks
: P5 normal
Assignee: R-core
URL:
Depends on:
Blocks:
 
Reported: 2015-06-19 21:02 UTC by Ron Newman
Modified: 2015-06-20 11:31 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Newman 2015-06-19 21:02:04 UTC
I am running R from Terminal.app (from OS X 10.9.5) and have encountered the following issue that happens consistently in two situations:

1) The text cursor is at the end of the line, and I press the right-arrow key
2) The text cursor is in any position, and I press Ctrl-E

Example:
> text[cursor]

Every time I perform either of (1) or (2), the text cursor remains at the end of the line, and further text input from the keyboard is ignored.

Example: After performing (1) or (2) and typing further characters, the new characters don't get added to the line.
> text[cursor]

This 'frozen' state can be resolved by pressing the left-arrow key. After pressing the left-arrow key once, the text cursor remains at the end of the line (does not move back), and further text input from the keyboard is recognized.

After left-arrow:
> text[cursor]
After typing more text:
> textmoretext[cursor]
Comment 1 Peter Dalgaard 2015-06-20 11:31:43 UTC
Hey, thanks. Reproduceable for me on Yosemite.

That had been bugging me for quite a while, but I had written it off to a quirk in Terminal.app. Never occurred to me that it could be an issue in R itself. But other readline-enabled software like bash doesn't do this, so I guess that you're right.

It looks, btw, like xterm on the Mac has the right-arrow-at-eol issue, but not the ctl-E version.