on Mon, Apr 09, 2001 at 02:06:50AM +0800, csj ([EMAIL PROTECTED]) wrote:
> On Sunday 08 April 2001 08:48, Karsten M. Self wrote:
> > on Sun, Apr 08, 2001 at 07:38:11AM +0800, csj ([EMAIL PROTECTED])
> wrote:
> > > Taking a breath of humid air:
> > >
> > > Let's say I have a file "commands.list" w
On Mon, Apr 09, 2001 at 02:06:50AM +0800, csj wrote:
> On Sunday 08 April 2001 08:48, Karsten M. Self wrote:
> > Command Substitution:
> >
> > $ cat > df
> > ls
> > uptime
> > EOF
> >
> > $ $( grep df cmd.lst )
> >
> > QED.
>
> Not quite QED (tho quite close). Wh
On Sunday 08 April 2001 08:48, Karsten M. Self wrote:
> on Sun, Apr 08, 2001 at 07:38:11AM +0800, csj ([EMAIL PROTECTED])
wrote:
> > On Friday 06 April 2001 03:04, Karsten M. Self wrote:
> > > on Thu, Apr 05, 2001 at 06:47:53AM +0800, csj
> > > ([EMAIL PROTECTED])
> >
> > wrote:
> > > > On Wednesd
On Sun, Apr 08, 2001 at 11:17:28AM +1000, CaT wrote:
> On Sun, Apr 08, 2001 at 07:38:11AM +0800, csj wrote:
> > I would extract the first command (1) from "commands.list" by typing
> >
> > grep "www.foo.org"
> >
> > which would of course print to the default stdout, e.g. the terminal.
> > End of
On Sun, Apr 08, 2001 at 07:38:11AM +0800, csj wrote:
> I would extract the first command (1) from "commands.list" by typing
>
> grep "www.foo.org"
>
> which would of course print to the default stdout, e.g. the terminal.
> End of story. That's all I get. But if there's some way to "pipe" or
> "
on Sun, Apr 08, 2001 at 07:38:11AM +0800, csj ([EMAIL PROTECTED]) wrote:
> On Friday 06 April 2001 03:04, Karsten M. Self wrote:
> > on Thu, Apr 05, 2001 at 06:47:53AM +0800, csj ([EMAIL PROTECTED])
> wrote:
> > > On Wednesday 04 April 2001 09:41, Karsten M. Self wrote:
> > > > csj ([EMAIL PROTECT
On Friday 06 April 2001 03:04, Karsten M. Self wrote:
> on Thu, Apr 05, 2001 at 06:47:53AM +0800, csj ([EMAIL PROTECTED])
wrote:
> > On Wednesday 04 April 2001 09:41, Karsten M. Self wrote:
> > > csj ([EMAIL PROTECTED]) wrote:
> > > > Is there a way to copy or paste text into bash without the
> >
Quoting Karsten M. Self (kmself@ix.netcom.com):
> > > csj ([EMAIL PROTECTED]) wrote:
> > > > Is there a way to copy or paste text into bash without the use of
> > > > a mouse? I'm thinking of a text file "file.txt" which contains
> > > > command sequences which I would like to touch up before runni
on Thu, Apr 05, 2001 at 06:47:53AM +0800, csj ([EMAIL PROTECTED]) wrote:
> On Wednesday 04 April 2001 09:41, Karsten M. Self wrote:
> > csj ([EMAIL PROTECTED]) wrote:
> > > Is there a way to copy or paste text into bash without the use of
> > > a mouse? I'm thinking of a text file "file.txt" which
On Wed, Apr 04, 2001 at 08:40:32PM -0400, Chris Matta wrote:
> ...
> c> Hmm, does this really mean I have to really vi? Actually I was
> c> thinking of something like "cat file.txt > /dev/ttyX" which however
> c> pastes the thing not just on the screen but on the command line
> c> itself. Is the
On Wednesday 04 April 2001 09:41, Karsten M. Self wrote:
> csj ([EMAIL PROTECTED]) wrote:
> > Is there a way to copy or paste text into bash without the use of
> > a mouse? I'm thinking of a text file "file.txt" which contains
> > command sequences which I would like to touch up before running.
> >
on Wed, Apr 04, 2001 at 08:50:56AM +0800, csj ([EMAIL PROTECTED]) wrote:
> Is there a way to copy or paste text into bash without the use of a
> mouse? I'm thinking of a text file "file.txt" which contains command
> sequences which I would like to touch up before running.
>
> I don't want to use
on Wed, Apr 04, 2001 at 08:50:56AM +0800, csj ([EMAIL PROTECTED]) wrote:
> Is there a way to copy or paste text into bash without the use of a
> mouse? I'm thinking of a text file "file.txt" which contains command
> sequences which I would like to touch up before running.
>
> I don't want to use
13 matches
Mail list logo
