From: Tim Walberg <twalberg@mindspring.com>
To: Shawn Ashlee <shawn@ashlee.info>
Cc: linux-admin@vger.kernel.org
Subject: Re: [Fwd: Re: ctrl-M]
Date: Wed, 27 Aug 2003 15:05:06 -0500 [thread overview]
Message-ID: <20030827150506.F21046@mindspring.com> (raw)
In-Reply-To: <3F4D0AF8.8090909@ashlee.info> from Shawn Ashlee on 08/27/2003 14:48
Remove the "\r" bits... The newline that follows each
of them is already embedded in the string which you are
echo-ing, so the file should look like you expect...
Another way to do this that might be slightly
easier than the echo statement would be to
use the "here-document" feature (although
a performance nazi might point out that the
binary for cat takes up slightly more memory
than that for echo):
cat > $PROCFILE <<EOF
# $2 start
...
...
EOF
On 08/27/2003 12:48 -0700, Shawn Ashlee wrote:
>> (Freddie)Here is the snippet:
>> echo "$2" | sed -e 's/\./\\./g' > /tmp/add_to_proc.tmp
>> TEMPFILE=`cat /tmp/sed/add_to_proc.tmp`;
>>
>> echo -e "
>> # $2 start\r
>> :0:\r
>> * ^From: .*$TEMPFILE.*\r
>> /dev/null\r
>> # $2 end\r
>> " >> $PROCFILE
>>
>> echo "Sucessfully added $2 to $PROCFILE"
>> exit 0
>>
>> This is just for a Linux box, it will not be moved to dos. The "only"
>> problem with the ctrl-M is that procmail will not read the file with
>> those in there. Like I said, it shows them in vi but not when you cat
>> the file.
>>
>> Shawn
>>
>> -------- Original Message --------
>> From: - Wed Aug 27 12:43:23 2003
>> X-UIDL: 3f4d06fb00000001
>> X-Mozilla-Status: 0011
>> X-Mozilla-Status2: 00000000
>> Return-Path: <freddie@tumsan.fi>
>> Received: from virt19x.secure-wi.com (root@localhost) by ashlee.info
>> (8.11.6/8.11.6) with ESMTP id h7RJRP401864 for <shawn@ashlee.info>; Wed,
>> 27 Aug 2003 12:27:25 -0700
>> X-ClientAddr: 217.116.160.18
>> Received: from ns.tumsan.fi (mail.tumsan.fi [217.116.160.18]) by
>> virt19x.secure-wi.com (8.11.6/8.11.6) with ESMTP id h7RJRMl01805 for
>> <shawn@ashlee.info>; Wed, 27 Aug 2003 12:27:23 -0700
>> Received: from mouse.tumsan.fi (mouse.tumsan.fi [217.116.165.11]) by
>> ns.tumsan.fi (8.11.2/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id
>> h7RJR6210842 for <shawn@ashlee.info>; Wed, 27 Aug 2003 22:27:06 +0300
>> Message-Id: <5.1.0.14.0.20030827221350.00b15820@217.116.160.18>
>> X-Sender: freddie@217.116.160.18
>> X-Mailer: QUALCOMM Windows Eudora Version 5.1
>> Date: Wed, 27 Aug 2003 22:14:28 +0300
>> To: Shawn Ashlee <shawn@ashlee.info>
>> From: freddie <freddie@tumsan.fi>
>> Subject: Re: ctrl-M
>> In-Reply-To: <3F4D0079.9060106@ashlee.info>
>> Mime-Version: 1.0
>> Content-Type: text/plain; charset="us-ascii"; format=flowed
>> X-MailScanner: Found to be clean
>> Status: O
>>
>> could you post up your script (or at least the part that does the writing)?
>>
>> >I have a bash script writting to a .procmailrc file, but it is putting in
>> >ctrl-M's where I have \r or \015. You can see them in vi but not when you
>> >cat the file. It wouldn't be a problem, but procmail cant read it with
>> >those in there. I tried \n, but it adds alot of blank lines.
>> >The archives mostly talk about compatability for dos/linux, but that
>> >doesnt help me.
>> >
>> >Thanks,
>> >Shawn
>> >
>> >
>> >
>> >-
>> >To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>> >the body of a message to majordomo@vger.kernel.org
>> >More majordomo info at http://vger.kernel.org/majordomo-info.html
>> >
>>
>>
>>
>>
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
End of included message
--
+--------------------------+------------------------------+
| Tim Walberg | twalberg@mindspring.com |
| 830 Carriage Dr. | www.mindspring.com/~twalberg |
| Algonquin, IL 60102 | |
+--------------------------+------------------------------+
next prev parent reply other threads:[~2003-08-27 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 19:48 [Fwd: Re: ctrl-M] Shawn Ashlee
2003-08-27 20:05 ` Tim Walberg [this message]
2003-08-27 20:06 ` freddie
2003-08-29 5:12 ` Stephen Samuel
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=20030827150506.F21046@mindspring.com \
--to=twalberg@mindspring.com \
--cc=linux-admin@vger.kernel.org \
--cc=shawn@ashlee.info \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.