/[sed]/sed/sed.html
ViewVC logotype

Diff of /sed/sed.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.4 by karl, Fri Jan 4 23:50:43 2013 UTC revision 1.12 by th_g, Sun Aug 9 19:04:21 2020 UTC
# Line 1  Line 1 
1  <!--#include virtual="/server/header.html" -->  <!--#include virtual="/server/header.html" -->
2  <title>GNU sed - GNU Project - Free Software Foundation (FSF)</title>  <!-- Parent-Version: 1.92 -->
3    <!-- This page is derived from /server/standards/boilerplate.html -->
4    <title>GNU sed - GNU Project - Free Software Foundation</title>
5    <link rel="stylesheet" type="text/css" href="sed.css" />
6    <!--#include virtual="/server/gnun/initial-translations-list.html" -->
7  <!--#include virtual="/server/banner.html" -->  <!--#include virtual="/server/banner.html" -->
8    <div class="reduced-width">
9    
10  <h2>GNU sed</h2>  <h2>GNU sed</h2>
11    <hr class="thin" />
12    
13  <hr>  <p>
14  <p>sed is looking for a maintainer.    sed (stream editor) is a non-interactive command-line text editor.
15  If you're interested, please take a look at this <a  </p>
16  href="/help/evaluation.html#whatmeans">general information about GNU  <pre class="example">
17  packages and being a GNU maintainer</a>, and then email  # Example: delete the 4th line in a file
18  maintainers@gnu.org with a bit about your background and particular  $ sed '4d' input.txt &gt; output.txt
19  interest in this package.  Thanks.</p>  
20  <hr>  # Example: replace every occurrence of 'hello' with 'world' on lines 10-20
21    $ sed '10,20s/hello/world/' input.txt &gt; output.txt
22    </pre>
23    
24    <p>
25      sed is commonly used to filter text, i.e., it takes text
26      input, performs some operation (or set of operations) on it, and
27      outputs the modified text.  sed is typically used for extracting
28      part of a file using pattern matching or substituting multiple
29      occurrences of a string within a file.
30    </p>
31    
32    
33    <div class="summary">
34    <h3 class="no-display">Table of Contents</h3>
35    <ul>
36      <li><a href="#help">Getting Help</a></li>
37      <li><a href="#download">Downloads</a></li>
38      <li><a href="#source">Latest Source</a></li>
39      <li><a href="#mailinglists">Mailing Lists</a></li>
40      <li><a href="#maintainers">Maintainers</a></li>
41    </ul>
42    <hr class="no-display" />
43    </div>
44    
45    
46    <h3 id="help">Getting Help</h3>
47    
48    <ul>
49    
50    <!-- SED Manual -->
51    <li>
52      Read the manual locally using <kbd>info sed</kbd> or see the latest
53      <a href="manual/">online manual</a>.
54    </li>
55    
56    <!-- Search Mailing lists -->
57    <li>Search the archives for previous questions and answers:
58      <ul>
59        <li>questions, development, and general discussion:
60            <a href="https://lists.gnu.org/archive/html/sed-devel/">
61            sed-devel mailing list</a>;
62        </li>
63        <li>bug reports:
64            <a href="https://lists.gnu.org/archive/html/bug-sed/">
65            bug-sed mailing list</a>.
66        </li>
67      </ul>
68    </li>
69    
70    <!-- http://sed.sf.net -->
71    <li>General sed resources are available at
72      <a href="http://sed.sf.net">SourceForge.net</a>, including:
73      <ul>
74        <li>
75          <a href="http://sed.sourceforge.net/#docs">
76            documentations, FAQ, one-liners</a>,
77        </li>
78        <li>
79          <a href="http://sed.sourceforge.net/#books">
80            books</a>, and
81        </li>
82        <li>
83          <a href="http://sed.sourceforge.net/#scripts">
84            example scripts</a>.
85        </li>
86      </ul>
87    </li>
88    
89    
90    <!-- http://translationproject.org/domain/sed.html -->
91    <li>
92      Send translation requests to the language team at the
93      <a href="https://translationproject.org/domain/sed.html">
94        Translation Project</a>.
95    </li>
96    
97    <!-- sed-devel@gnu.org for GENERAL QUESTIONS -->
98    <li>
99      Send general questions or suggestions to the mailing list at
100      &lt;<a href="mailto:sed-devel@gnu.org">sed-devel@gnu.org</a>&gt;.
101    </li>
102    
103    <!-- bug-sed@gnu.org for BUG REPORTS -->
104    <li>
105      Report bugs, including version and distribution variant, to the list at
106      &lt;<a href="mailto:bug-sed@gnu.org">bug-sed@gnu.org</a>&gt;.<br/> Before
107      sending the bug, please consult the FAQ and mailing list archives
108      (above).<br/>  Often these perceived bugs are simply due to wrong
109      program usage.<br/>  To learn more about reporting bugs,
110      see <a href="/software/gethelp.html">Getting help with GNU software</a>.
111    </li>
112    
113    </ul>
114    
115    <h3 id="download">Downloads</h3>
116    
117    <p>
118      Stable source releases are available on the main GNU download server
119      (<a href="https://ftp.gnu.org/gnu/sed/">HTTPS</a>,&nbsp;
120      <a href="http://ftp.gnu.org/gnu/sed/">HTTP</a>,&nbsp;
121      <a href="ftp://ftp.gnu.org/gnu/sed/">FTP</a>) and its
122      <a href="/prep/ftp.html">mirrors</a>. Please
123      <a href="https://ftpmirror.gnu.org/gnu/sed/">use a mirror</a> if possible.
124    </p>
125    
126    <h3 id="source">Latest Source</h3>
127    
128    <p>
129    The latest source with revision history can be browsed using
130    <a href="https://git.sv.gnu.org/cgit/sed.git">cgit</a> or
131    <a href="https://git.sv.gnu.org/gitweb/?p=sed.git">gitweb</a>.
132    Assuming you have <a href="https://git-scm.com/">git</a> installed, you
133    can retrieve the latest version with this command:</p>
134    <pre class="emph-box">
135    <samp>git clone git://git.sv.gnu.org/sed</samp>
136    </pre>
137    
138    <!-- TODO: add README-hacking to SED
139    To build from the latest sources please follow the instructions in
140    <a href="http://git.savannah.gnu.org/cgit/sed.git/plain/README-hacking">README-hacking</a><br/>
141    -->
142    <p>
143    Please note that we do not suggest using test versions of sed
144    for production use.
145    </p>
146    
147    
148    <!-- TODO: Add SED to all of the websites below
149    <h3 id="testing">Third party testing resources</h3>
150    <p>
151    <ul>
152        <li><a href="http://hydra.nixos.org/jobset/gnu/coreutils-master">
153        Hydra continuous integration jobs</a></li>
154        <li><a href="https://scan.coverity.com/projects/29?tab=Overview">
155        Coverity static analysis</a></li>
156        <li><a href="http://www.opencoverage.net/coreutils">
157        Open coverage test coverage report</a></li>
158        <li><a href="http://hydra.nixos.org/job/gnu/coreutils-master/coverage/latest/log/tail-reload">
159        Latest Hydra test coverage results</a></li>
160    </ul>
161    </p>
162    -->
163    
164    
165    <h3 id="mailinglists">Mailing Lists</h3>
166    
167    <p>
168    You do not need to be subscribed in order to post messages to any GNU
169    mailing list.  However non-subscribers are moderated by humans so
170    please be patient when waiting for your email to arrive.
171    </p>
172    
173    <p>
174    You can subscribe to any GNU mailing list via the web as described
175    below. Or you can send an empty mail with a <i>Subject:</i> header line of
176    just &ldquo;subscribe&rdquo; to the relevant <i>-request</i> list. For example, to
177    subscribe yourself to the main sed-devel list, you would
178    send mail to &lt;<a
179    href="mailto:sed-devel-request@gnu.org">sed-devel-request@gnu.org</a>&gt;
180    with no body and a <i>Subject:</i> header line of just &ldquo;subscribe&rdquo;.
181    </p>
182    
183    <p>
184    It has been necessary to moderate the sed  mailing lists to prevent the
185    flood of spam. Postings to the lists are held for release by
186    the list moderator. Sometimes the moderators are unavailable for
187    brief periods of time. Please be patient when posting. If you
188    don't eventually see the message in the list archive then it did not
189    get posted.
190    </p>
191    
192    <dl>
193    <dt>Announcements</dt>
194    <dd>
195    <p>
196    Important announcements about GNU sed and most other GNU Software are
197    also made on the
198    <a href="https://lists.gnu.org/mailman/listinfo/info-gnu">
199      info-gnu@gnu.org mailing list</a>.
200    </p>
201    </dd>
202    
203    <dt>Discussion List</dt>
204    <dd>
205    <p>
206    The main discussion list for all things related to GNU sed is
207    <a href="https://lists.gnu.org/mailman/listinfo/sed-devel">sed-devel@gnu.org</a>.
208    If you have questions, comments, or other general
209    discussion about sed then this is the mailing list for that
210    discussion.  If you don't know where to start then this is the place
211    to start.  You can browse and search past postings to the
212    <a href="https://lists.gnu.org/archive/html/sed-devel/">sed-devel archive</a>.
213    </p>
214    </dd>
215    
216    <dt>Bug Reports</dt>
217    <dd>
218    <p>
219    If you think you have found a bug in GNU sed, then please send
220    as complete a bug report as possible to
221    <a href="https://lists.gnu.org/mailman/listinfo/bug-sed">bug-sed@gnu.org</a>,
222    and it will automatically be entered into the <a href="https://debbugs.gnu.org/sed">
223    sed bug tracker</a>.
224    <!-- TODO: sed FAQ?
225    Before reporting bugs please read the <a href="faq/coreutils-faq.html">FAQ</a>.
226    -->
227    A very useful and often referenced guide on how to write bug reports
228    and ask good questions is the document
229    <a href="http://www.catb.org/~esr/faqs/smart-questions.html">
230    How To Ask Questions The Smart Way</a>.
231    You can browse previous postings and search the
232    <a href="https://lists.gnu.org/archive/html/bug-sed/">bug-sed archive</a>.
233    </p>
234    </dd>
235    
236    <dt>Platform Testing</dt>
237    <dd>
238    <p>
239    Trying the latest test release (when available) is always appreciated.
240    Test releases of sed are typically announced on the
241    <a href="https://lists.gnu.org/mailman/listinfo/platform-testers">
242    platform-testers</a> mailing list.
243    </p>
244    </dd>
245    
246    <dt>Enhancement Requests</dt>
247    <dd>
248  <p>  <p>
249  sed (stream editor) isn't an interactive text editor.  If you would like any new feature to be included in future versions of
250  Instead, it is used to filter text, i.e., it takes text input, performs  sed, please send a request to <a
251  some operation (or set of operations) on it, and outputs the modified text.  href="https://lists.gnu.org/mailman/listinfo/sed-devel">sed-devel@gnu.org</a>.
252  sed is typically used for extracting part of a file using pattern matching  
253  or substituting multiple occurrences of a string within a file.  This is the general discussion list and a good place to start
254    discussion of a new feature.  After consideration you may be asked to
255    log a request into the bug tracker so that the issue is not lost.
256    
257    If you would like to implement yourself, then note that non trivial changes
258    require copyright assignment to the FSF as detailed in the &ldquo;Copyright Assignment&rdquo;
259    <!-- TODO: add HACKING to sed -->
260    section of GNU coreutils <a href="https://git.sv.gnu.org/cgit/coreutils.git/plain/HACKING">HACKING</a> notes.
261    </p>
262    </dd>
263    
264    <dt>Mailing List Etiquette</dt>
265    <dd>
266    <p>
267    Please do not send messages encoded as HTML nor encoded as base64 MIME
268    nor included as multiple formats.
269    Please send messages as
270    <a href="https://web.archive.org/web/20160305050159/http://stagecraft.theprices.net/nomime.html">
271    plain text</a>.
272    Please include a descriptive subject line. If all of the subjects are
273    <em>bug</em> then it is impossible to differentiate them.
274    Please avoid sending large messages, such as log files, system call
275    trace output, and other content resulting in messages over about 40 kB,
276    to the mailing lists without prior contact. Those are best sent
277    directly to those requesting that information after initial contact.
278  </p>  </p>
279    
280  <p>  <p>
281  <a href="manual/">Online documentation</a> is available.  Please remember that development of GNU sed is a volunteer effort, and you
282    can also contribute to its development. For information about contributing
283    to the GNU Project, please read <a href="/help/">How to help GNU</a>.
284  </p>  </p>
285    </dd>
286    </dl>
287    
288    <h3 id="maintainers">Maintainers</h3>
289    
290    <p>
291    GNU sed is currently being maintained by
292    Jim Meyering &lt;<a href="mailto:jim@meyering.net">jim@meyering.net</a>&gt;,
293    and
294    Assaf Gordon &lt;<a href="mailto:assafgordon@gmail.com">assafgordon@gmail.com</a>&gt;.
295    </p>
296    
297    
298  <!-- If needed, change the copyright block at the bottom. In general, -->  </div>
 <!-- all pages on the GNU web server should have the section about    -->  
 <!-- verbatim copying.  Please do NOT remove this without talking     -->  
 <!-- with the webmasters first. -->  
 <!-- Please make sure the copyright date is consistent with the document -->  
 <!-- and that it is like this "2001, 2002" not this "2001-2002." -->  
299  </div><!-- for id="content", starts in the include above -->  </div><!-- for id="content", starts in the include above -->
300  <!--#include virtual="/server/footer-min.html" -->  <!--#include virtual="/server/footer.html" -->
301  <div id="footer">  <div id="footer">
302    <div class="unprintable">
303    
304  <p>  <p>Please send general FSF &amp; GNU inquiries to
305  Please send FSF &amp; GNU inquiries to  <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
 <a href="mailto:gnu@gnu.org"><em>gnu@gnu.org</em></a>.  
306  There are also <a href="/contact/">other ways to contact</a>  There are also <a href="/contact/">other ways to contact</a>
307  the FSF.  the FSF.  Broken links and other corrections or suggestions can be sent
308  <br />  to <a href="mailto:sed-devel@gnu.org"><em>sed-devel@gnu.org</em></a>.
 Please send broken links and other corrections or suggestions to  
 <a href="mailto:bug-sed@gnu.org"><em>bug-sed@gnu.org</em></a>.  
309  </p>  </p>
310    
311  <p>Copyright &copy; 2013 Free Software Foundation, Inc.</p>  <p>Please see the <a
312    href="/server/standards/README.translations.html">Translations
313    README</a> for information on coordinating and contributing translations
314    of this article.</p>
315    </div>
316    
317    <!-- Regarding copyright, in general, standalone pages (as opposed to
318         files generated as part of manuals) on the GNU web server should
319         be under CC BY-ND 4.0.  Please do NOT change or remove this
320         without talking with the webmasters or licensing team first.
321         Please make sure the copyright date is consistent with the
322         document.  For web pages, it is ok to list just the latest year the
323         document was modified, or published.
324    
325         If you wish to list earlier years, that is ok too.
326         Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
327         years, as long as each year in the range is in fact a copyrightable
328         year, i.e., a year in which the document was published (including
329         being publicly visible on the web or in a revision control system).
330    
331         There is more detail about copyright years in the GNU Maintainers
332         Information document, www.gnu.org/prep/maintain. -->
333    
334    <p>Copyright &copy; 2013, 2014, 2015, 2016 Free Software Foundation, Inc.</p>
335    
336  <p>This page is licensed under a <a rel="license"  <p>This page is licensed under a <a rel="license"
337  href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative  href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
338  Commons Attribution-NoDerivs 3.0 United States License</a>.</p>  Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
339    
340    <!--#include virtual="/server/bottom-notes.html" -->
341    
342    <p class="unprintable">Updated:
343    <!-- timestamp start -->
344    $Date$
345    <!-- timestamp end -->
346    </p>
347  </div>  </div>
348  </div>  </div>
349  </body>  </body>
Legend:
Removed from v.1.4  
changed lines
  Added in v.1.12
savannah-hackers-public@gnu.org
 ViewVC Help
Powered by ViewVC 1.1.26