lukechilds/node - node - Gitea: Git with a cup of tea

6937 Commits

131 Branches

446 Tags

325 MiB

Tree: 1867511400

Commit Graph

Author	SHA1	Message	Date
isaacs	e4c9c9f412	readline: Remove event listeners on close Fix #3756	12 years ago
Nathan Rajlich	78eb174ea2	readline: use StringDecoder for decoding "normal" data The fix from #3059 was not handling multi-byte utf8 data properly.	13 years ago
Nathan Friedly	e28f77cbad	readline: buffer data to only emit 'line' on '\n' In "terminal: false" mode. (And fire it multiple times if multiple lines arrive at once.) This is necessary because the Windows telnet client sends every single keystroke as it's typed. See: http://stackoverflow.com/questions/9962197/node-js-readline-not-waiting-for-a-full-line-on-socket-connections Closes #3059.	13 years ago

Author

SHA1

Message

Date

isaacs

e4c9c9f412

readline: Remove event listeners on close

Fix #3756

12 years ago

Nathan Rajlich

78eb174ea2

readline: use StringDecoder for decoding "normal" data

The fix from #3059 was not handling multi-byte utf8 data properly.

13 years ago

Nathan Friedly

e28f77cbad

readline: buffer data to only emit 'line' on '\n'

In "terminal: false" mode.

(And fire it multiple times if multiple lines arrive at once.)

This is necessary because the Windows telnet client sends every single
keystroke as it's typed.

See: http://stackoverflow.com/questions/9962197/node-js-readline-not-waiting-for-a-full-line-on-socket-connections

Closes #3059.

13 years ago

3 Commits (1867511400e895989652af33aa4942b446a90151)