Philip Olson
bc35f28f51
Fix issue where non-windows OS terminals don't paste newlines correctly into misbehaving programs. As noted in JetBrains/jediterm#136, the most practical solution is for terminals to handle this in their paste logic. In a perfect world, all terminal programs would implement bracketed paste mode properly, but that's a lot to ask. - translate newlines to \r which is what terminal programs expect
34 lines
1.1 KiB
TypeScript
34 lines
1.1 KiB
TypeScript
/**
|
|
* Copyright (c) 2016 The xterm.js authors. All rights reserved.
|
|
* @license MIT
|
|
*/
|
|
|
|
import { assert } from 'chai';
|
|
import * as Terminal from '../Terminal';
|
|
import * as Clipboard from './Clipboard';
|
|
|
|
describe('evaluatePastedTextProcessing', () => {
|
|
it('should replace carriage return and/or line feed with carriage return', () => {
|
|
const pastedText = {
|
|
unix: 'foo\nbar\n',
|
|
windows: 'foo\r\nbar\r\n'
|
|
};
|
|
|
|
const processedText = {
|
|
unix: Clipboard.prepareTextForTerminal(pastedText.unix),
|
|
windows: Clipboard.prepareTextForTerminal(pastedText.windows)
|
|
};
|
|
|
|
assert.equal(processedText.unix, 'foo\rbar\r');
|
|
assert.equal(processedText.windows, 'foo\rbar\r');
|
|
});
|
|
it('should bracket pasted text in bracketedPasteMode', () => {
|
|
const pastedText = 'foo bar';
|
|
const unbracketedText = Clipboard.bracketTextForPaste(pastedText, false);
|
|
const bracketedText = Clipboard.bracketTextForPaste(pastedText, true);
|
|
|
|
assert.equal(unbracketedText, 'foo bar');
|
|
assert.equal(bracketedText, '\x1b[200~foo bar\x1b[201~');
|
|
});
|
|
});
|