<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Understanding Sed statement in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/understanding-sed-statement/m-p/5242838#M676671</link>
    <description>Ok thanks for the explanation.</description>
    <pubDate>Tue, 08 Jun 2010 10:06:19 GMT</pubDate>
    <dc:creator>Brecht De Baets</dc:creator>
    <dc:date>2010-06-08T10:06:19Z</dc:date>
    <item>
      <title>Understanding Sed statement</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/understanding-sed-statement/m-p/5242836#M676669</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have found the following statement to list only subdirectories which are not empty.&lt;BR /&gt;&lt;BR /&gt;find . -type f | sed "s%/[^/]*$%%" | sort -u&lt;BR /&gt;&lt;BR /&gt;I don't really understand the sed statement. I know it cuts the filenames away at the end of each line that was found by "find -type f", but I would like to be able to understand how&lt;BR /&gt;the statement actually is built.&lt;BR /&gt;Is there anyone who is able to explain the sed-part ?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Brecht</description>
      <pubDate>Tue, 08 Jun 2010 09:13:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/understanding-sed-statement/m-p/5242836#M676669</guid>
      <dc:creator>Brecht De Baets</dc:creator>
      <dc:date>2010-06-08T09:13:57Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding Sed statement</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/understanding-sed-statement/m-p/5242837#M676670</link>
      <description>&lt;!--!*#--&gt;"s" is "substitute".&lt;BR /&gt;&lt;BR /&gt;"%" is a delimiter.  Normally, people use&lt;BR /&gt;"/" for that, but that's inconvenient when&lt;BR /&gt;looking for a "/" (and "sed" lets you use any&lt;BR /&gt;character as a delimiter).&lt;BR /&gt;&lt;BR /&gt;So, it's looking for a "/", followed by any&lt;BR /&gt;number of non-"/" characters ("[^/]*") at the&lt;BR /&gt;end of a line ("$"), and substituting nothing&lt;BR /&gt;(what's between "%" and "%" in "%%") for&lt;BR /&gt;that.&lt;BR /&gt;&lt;BR /&gt;      man sed</description>
      <pubDate>Tue, 08 Jun 2010 09:27:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/understanding-sed-statement/m-p/5242837#M676670</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2010-06-08T09:27:25Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding Sed statement</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/understanding-sed-statement/m-p/5242838#M676671</link>
      <description>Ok thanks for the explanation.</description>
      <pubDate>Tue, 08 Jun 2010 10:06:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/understanding-sed-statement/m-p/5242838#M676671</guid>
      <dc:creator>Brecht De Baets</dc:creator>
      <dc:date>2010-06-08T10:06:19Z</dc:date>
    </item>
  </channel>
</rss>

