DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3E1053857004
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: Cygwin 3.1.7 - xterm v360.1 - columns pasted from Excel no longer
 separated by tab
Thread-Topic: Cygwin 3.1.7 - xterm v360.1 - columns pasted from Excel no
 longer separated by tab
Thread-Index: AQHW1MjsOcsYIoOgb0aFvayNXiCABan8YuIAgADEms4=
Date: Fri, 18 Dec 2020 18:22:40 +0000
Message-ID: <CY4PR13MB15275B2A68BD9F9036B193CFD8C30@CY4PR13MB1527.namprd13.prod.outlook.com>
References: <be725ca1-ed04-95fb-fa68-d40e3b0db443 AT comcast DOT net>,
 <e41908d7-2e93-2890-ad9e-7227713b39cb AT SystematicSw DOT ab DOT ca>
In-Reply-To: <e41908d7-2e93-2890-ad9e-7227713b39cb@SystematicSw.ab.ca>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [8lBG2fVKCqX6ITiufz/MH6woY8LhT4nN]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 65588f4f-5fa5-457e-f67e-08d8a381e76a
x-ms-traffictypediagnostic: CY4PR1301MB2008:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 8SuuU0oxHzQpw5UnWVheELiSIPO0nf4iy4UBN2pt2S6Cb9DU78WLhRLWhO3BfNzoWNB1rOKcuDgbt8fb7yjyYYU/BQ4BEuC4wacFXpYySq0qRmXDkBihbpHiKEP89DKkqsUKxrLYWGzlvmhvftn9edIqEjlfe9gnPR3zSeMtIlzZZUoJBkhjtIyuNFU4p5HXSoliV/Na8mKIGMJEiAevFLdMsFzmRqYg3G6XwQruHnwVOwmrQ4vyiTtMdWLZZmo18Dt1ygXyH8lryaJlEfDmfCUme1pVu8jIWiTOHE+GDAg=
x-ms-exchange-antispam-messagedata: sfg72N04NLbpS+PjO6nZ/ToLW+pzGxCerj7/v5p8+95BZap9IU7QS6QkpX39JsiafT/tYiDSunpfKHizwBiBusFzdwH7XlzCRS1Eu//ttnLvfYHSY5D25U89X5bhmf2iRhkRFL7YvTlOpdzyrFYAMQ==
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: sct-15-20-3174-8-msonline-outlook-32ef5.templateTenant
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CY4PR13MB1527.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 65588f4f-5fa5-457e-f67e-08d8a381e76a
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Dec 2020 18:22:40.0341 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1301MB2008
X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE,
 RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Bill shaffer via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Bill shaffer <billshaf AT hotmail DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

Thank you for the response!  This got me looking in the right direction.  I agree with what you say that the clipboard contents are determined by the source.  Given that I could paste (from the same buffer) into the console window and get tabs, I had to assume that the copy process was grabbing the tabs as expected.

So looking for editor and window settings, and looking in the xterm(1) man page, I found disallowedPasteControls, which says the default includes ASCII tabs:
...
The default is
BS,HT,DEL,ESC
BS - ASCII backspace
HT - ASCII tab
DEL - ASCII delete
ESC - ASCII escape
...

I put the following line in my .Xdefaults, removing HT:
xterm*disallowedPasteControls: BS,DEL,ESC

and restarted Xwin server, and now my tabs paste as expected.

That entry doesn't even exist in my older installation's man page.  I found a post indicating that it was added in xterm patch 333 in 2018, which would be newer than my previous install.

Thanks for the help!

Bill
________________________________
From: Cygwin <cygwin-bounces AT cygwin DOT com> on behalf of Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Sent: Thursday, December 17, 2020 11:22 PM
To: cygwin AT cygwin DOT com <cygwin AT cygwin DOT com>
Subject: Re: Cygwin 3.1.7 - xterm v360.1 - columns pasted from Excel no longer separated by tab

On 2020-12-17 16:03, Bill Shaffer via Cygwin wrote:
> Hello:
>
> I am using Cygwin 3.1.7 and xterm 360.1 on Windows 10.  I run the X server and
> work in xterm windows.  When I copy a selection from an Excel spreadsheet and
> paste it into a vi session in an xterm window, the spreadsheet columns are
> separated by spaces.  If I paste into a vi session in a cygwin 3.1.7 console, I
> get tabs as separators.  If I run xterm on another host and send the display to
> my X Server, I get tabs.
>
> In my previous version of Cygwin - which was probably about 2-3 years old - when
> I did this the columns were separated by tabs.  I still see tab separators in
> Cygwin 1.7.31 (Windows 8.1).  I can type tabs just fine in the 3.1.7 xterm.  It
> seems to be something in the local xterm that is converting the pasted tabs to
> spaces.  I don't think it's the copy portion of the operation, or I wouldn't get
> tabs in the console.
>
> Did something change at some point that would explain this behavior?  Is there a
> way to get back to having the columns separated by tabs?
>
> I understand that usually copying and pasting implies visible characters and
> that tabs are usually only visible as spaces, and this is the result I would
> expect when copying visible text separated by tabs.  However, when pasting from
> Excel, the columns have always come across separated by tabs - and still do,
> except for in xterm.
>
> My TERM is xterm - I've tried vt100 and vt220 as well.  My TERM is also xterm in
> the working examples above.

The consensus on X is that the characters copied are determined by the source,
and Windows apps often offer their clipboard info in multiple formats, if you
check using an app that allows you to choose the format pasted e.g LibreOffice.

Having said that, editors also have settings that determine how pasted tabs are
treated, and that may depend on the target window settings for the file type
when pasted.
On Cygwin and Linux that probably depends on the vim compatibility settings, and
settings in:

        $ strings -n5 /bin/vi | egrep '^[.~$/].*(ex|vim?)rc' | sort -u
        $HOME/.exrc
        $HOME/.virc
        .exrc
        .virc
        /etc/virc
        ~/.vim/vimrc

whereas BSD systems may still provide original n/vi.

--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple