From: Lee Revell <rlrevell@joe-job.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Paul Jackson <pj@sgi.com>, Andrew Morton <akpm@osdl.org>,
achew@nvidia.com, linux-kernel <linux-kernel@vger.kernel.org>,
jgarzik@pobox.com
Subject: Re: [PATCH 2.6.8-rc2] intel8x0.c to include CK804 audio support
Date: Tue, 27 Jul 2004 18:05:18 -0400 [thread overview]
Message-ID: <1090965918.1094.122.camel@mindpipe> (raw)
In-Reply-To: <200407270943.23292.vda@port.imtp.ilyichevsk.odessa.ua>
On Tue, 2004-07-27 at 02:43, Denis Vlasenko wrote:
> On Tuesday 27 July 2004 07:57, Paul Jackson wrote:
> > > For now the only fix for people using an X environment ... insert file
> > > ...
> >
> > Another fix is to copy from a non-brain damaged window, such as a gui
> > text editor window (nedit, for example).
> >
> > I'm guessing that the tabs are lost in the cut or copy operation, not in
> > the paste operation.
>
> because 'cut' in a xterm cannot know that those eight spaces
> once were a tab. xterm is probably storing screen as a char+attr
> two-dimensional array. There are no tabs, only spaces.
>
> > But file insertion is, in general, a sufficiently winning choice that I
> > think it's better just to get in the habit of always inserting patches
> > that way, at least on email clients that support it.
>
> I do it all the time.
The easiest suggestion I have seen so far is:
diff foo bar | xclip
Much easier than 'insert file', works perfectly. This is not installed
on Debian by default for some reason.
Might be a useful FAQ addition.
Lee
next prev parent reply other threads:[~2004-07-27 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 2:08 [PATCH 2.6.8-rc2] intel8x0.c to include CK804 audio support Andrew Chew
2004-07-27 0:38 ` Andrew Morton
2004-07-27 4:27 ` Lee Revell
2004-07-27 4:57 ` Paul Jackson
2004-07-27 6:43 ` Denis Vlasenko
2004-07-27 17:41 ` Lee Revell
2004-07-27 22:05 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-27 0:46 Andrew Chew
2004-07-27 1:06 ` Andrew Morton
2004-07-27 2:09 ` Jeff Garzik
2004-07-28 17:30 ` Takashi Iwai
2004-07-29 0:13 Andrew Chew
2004-07-29 13:31 ` Takashi Iwai
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=1090965918.1094.122.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=achew@nvidia.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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