public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Brent Harding <bharding@doorpi.net>
To: blinux-list@redhat.com
Subject: Re: joining a bunch of files
Date: Fri, 07 Dec 2001 13:07:21 -0600	[thread overview]
Message-ID: <3.0.6.32.20011207130721.008d3a70@mail.doorpi.net> (raw)
In-Reply-To: <Pine.BSF.4.43.0112070250210.85814-100000@server1.shellworl d.net>

Wouldn't for do it some how?
The little I knew about hyperlogo, one would think of something like
for numbers=1-99
cat file.a$numbers > file
At 02:50 AM 12/7/01 -0500, you wrote:
>That's exactly what the awk command I posted (using eval), and the xargs
>commands posted by others, do; without the extra steps.
>
>On Fri, 7 Dec 2001, Jude DaShiell wrote:
>
>> Your safest way is going to be with a little shell script.  If you have
>> the vis command it's probably better than cat -v.  I don't know if these
>> files are parts of a binary or text file.  The general script would look
>> something like this.  The redirection I do is for a good reason. cat -v a1
>> a2 a3 a4 a5 a6 a7 a8 a9 >>afile. The first line of the script would be
>> #!/bin/sh.  That longer line I wrote earlier would be duplicated as many
>> times as necessary and you'd change the numbers each line down the script.
>> so that the last line in the script would be cat a91 a92 a93 a94 a95 a96
>> a97 a98 a99 >>afile.  If you use a command like .,.s/a[1-9]/a1[1-9]/gp
>> <cr> That should change line 3 in the script from cat a1 a2 a3 a4 to cat
>> a11 a12 a13 a14 etc.
>>
>> Jude <jdashiel@shellworld.net>
>>
>>
>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://listman.redhat.com/mailman/listinfo/blinux-list
>>
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>




  parent reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Brent Harding
 ` Luke Davis
 ` Mike Gorse
 ` dreamwvr
   ` Luke Davis
     [not found]   ` <Pine.BSF.4.43.0111301549410.66683-100000@server1.shellworl d.net>
     ` Brent Harding
       ` Luke Davis
       ` Nicolas Pitre
         ` Luke Davis
         ` Brent Harding
           ` Henry Yen
     [not found]       ` <Pine.BSF.4.43.0111301627330.66683-100000@server1.shellworl d.net>
         ` Brent Harding
           ` dreamwvr
       ` Jude DaShiell
         ` Luke Davis
     [not found]         ` <Pine.BSF.4.43.0112070250210.85814-100000@server1.shellworl d.net>
           ` Brent Harding [this message]
     ` John G. Heim (26 2-9887)

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=3.0.6.32.20011207130721.008d3a70@mail.doorpi.net \
    --to=bharding@doorpi.net \
    --cc=blinux-list@redhat.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).