Re: sed & or -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: sed & or
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 19 Sep 2018 10:41:41 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Thing is, if you use the pipe bar to delimit, the escaped pipe bar is going
to be taken for the end delimiter.

On Wed, Sep 19, 2018 at 10:36 AM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Wed, Sep 19, 2018 at 12:27 PM Jack Woehr
<jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

well, for one thing, in delimiting the sed pattern, you could use
leading-slash s/foo/bar/

Until I started seeing the pipe character used for that purpose on
these lists, I didn't realize there WAS any other usable delimiter
besides the slash.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.