From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
'Ralf Gans' <Ralf.Gans@NSG-GmbH.de>
Subject: RE: Copy converts tabs to spaces ?
Date: Mon, 02 Feb 2009 20:16:00 -0000 [thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A2182F4DC2@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <A45AE599-B6AC-41DA-A230-CD3C1C7A4F67@NSG-GmbH.de>
Ralf Gans wrote on Monday, February 02, 2009 8:57 AM:
> On 02.02.2009, at 11:05, xerces8 wrote:
>> I noticed that when copying text from a the Cygwin Bash window and
>> then pasting it somewhere (like WordPad), tabulator characters are
>> converted to spaces.
>>
>> The same happens with RXVT too.
>>
>> Details:
>> - print the content of some text file that has tabs (like a C
>> program source) : cat foo.c
>> - select and copy the text with the mouse
>> - paste (ctrl-V) into WordPad
>>
>> The text in Wordpad has no more tabs.
>>
>> Is there a way around this ?
>
> copy an paste from window to window takes what's printed, not what
> you have written.
>
> So, if the terminal prints spaces to represent the tabs, as a
> terminal usually does, you CAN only copy spaces.
>
> All else is an exception, U*X ist NOT wysiwyg!
Think about using putclip instead.
$ cat foo.c | putclip -d
$ putclip -d < foo.c
$ putclip --help
putclip version 0.2.0
Copy stdin to the Windows Clipboard
Usage: putclip [OPTION...]
General options
-d, --dos Clipboard text will have DOS line endings.
-u, --unix Clipboard text will have UNIX line endings.
-n, --no-conv Do not translate line endings.
Help options
-?, --help Show this help message
--usage Display brief usage message
--version Display version information
--license Display licensing information
NOTE: by default, no line ending conversion is performed.
You also might want to familiarize yourself with getclip.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2009-02-02 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 10:06 xerces8
2009-02-02 10:27 ` Sisyphus
2009-02-02 10:42 ` Sisyphus
2009-02-02 13:57 ` Ralf Gans
2009-02-02 20:16 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
[not found] ` <B7021E1A-156E-4F9B-ADFC-B6DE58D5E14D@NSG-GmbH.de>
2009-02-07 13:25 ` Buchbinder, Barry (NIH/NIAID) [E]
2009-02-07 17:24 ` Paul McFerrin
2009-02-08 16:30 ` tmcd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0105D5C1E0353146B1B222348B0411A2182F4DC2@NIHMLBX02.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--cc=Ralf.Gans@NSG-GmbH.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).