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

Diff of /sed/sed.html

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

revision 1.10 by meyering, Sun Jan 1 16:55:33 2017 UTC revision 1.11 by th_g, Sat Aug 8 15:55:23 2020 UTC
# Line 1  Line 1 
1  <!--#include virtual="/server/header.html" -->  <!--#include virtual="/server/header.html" -->
2  <!-- Parent-Version: 1.79 -->  <!-- Parent-Version: 1.92 -->
3    <!-- This page is derived from /server/standards/boilerplate.html -->
4  <title>GNU sed - GNU Project - Free Software Foundation</title>  <title>GNU sed - GNU Project - Free Software Foundation</title>
5  <link rel="stylesheet" type="text/css" href="sed.css" />  <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  <p>  <p>
14    sed (stream editor) is a non-interactive command-line text editor.    sed (stream editor) is a non-interactive command-line text editor.
# Line 25  $ sed '10,20s/hello/world/' input.txt &g Line 29  $ sed '10,20s/hello/world/' input.txt &g
29    occurrences of a string within a file.    occurrences of a string within a file.
30  </p>  </p>
31    
 <h3><a name="help">Getting Help</a></h3>  
32    
33  <ul style="margin-top:0;">  <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 -->  <!-- SED Manual -->
51  <li>  <li>
52    Read the manual locally using <samp>info sed</samp> or see the latest    Read the manual locally using <kbd>info sed</kbd> or see the latest
53    <a href="manual/">online manual</a>    <a href="manual/">online manual</a>.
54  </li>  </li>
55    
56  <!-- Search Mailing lists -->  <!-- Search Mailing lists -->
57  <li>Search the archives for previous questions and answers:  <li>Search the archives for previous questions and answers:
58    <ul style="margin-top:0; margin-bottom:0;">    <ul>
59      <li>Questions, Development, and General Discussion:      <li>questions, development, and general discussion:
60          <a href="http://lists.gnu.org/archive/html/sed-devel/">          <a href="https://lists.gnu.org/archive/html/sed-devel/">
61          sed-devel Mailing list          sed-devel mailing list</a>;
         </a>  
62      </li>      </li>
63      <li>Bug reports:      <li>bug reports:
64          <a href="http://lists.gnu.org/archive/html/bug-sed/">          <a href="https://lists.gnu.org/archive/html/bug-sed/">
65          bug-sed Mailing List          bug-sed mailing list</a>.
         </a>  
66      </li>      </li>
67    </ul>    </ul>
68  </li>  </li>
69    
70  <!-- http://sed.sf.net -->  <!-- http://sed.sf.net -->
71  <li>General SED resources are available at  <li>General sed resources are available at
72    <a href="http://sed.sf.net">http://sed.sf.net</a>, including:    <a href="http://sed.sf.net">SourceForge.net</a>, including:
73    <ul style="margin-top:0;margin-bottom:0;">    <ul>
74      <li>      <li>
75        <a href="http://sed.sourceforge.net/#docs">        <a href="http://sed.sourceforge.net/#docs">
76          Documentations, FAQ, one-liners</a>          documentations, FAQ, one-liners</a>,
77      </li>      </li>
78      <li>      <li>
79        <a href="http://sed.sourceforge.net/#books">        <a href="http://sed.sourceforge.net/#books">
80          Books</a>          books</a>, and
81      </li>      </li>
82      <li>      <li>
83        <a href="http://sed.sourceforge.net/#scripts">        <a href="http://sed.sourceforge.net/#scripts">
84          Example scripts<a/>          example scripts</a>.
85      </li>      </li>
86    </ul>    </ul>
87  </li>  </li>
# Line 73  $ sed '10,20s/hello/world/' input.txt &g Line 89  $ sed '10,20s/hello/world/' input.txt &g
89    
90  <!-- http://translationproject.org/domain/sed.html -->  <!-- http://translationproject.org/domain/sed.html -->
91  <li>  <li>
92    Send translation requests to the language team linked from:    Send translation requests to the language team at the
93    <a href="http://translationproject.org/domain/sed.html">    <a href="https://translationproject.org/domain/sed.html">
94      http://translationproject.org/domain/sed.html      Translation Project</a>.
   </a>  
95  </li>  </li>
96    
97  <!-- sed-devel@gnu.org for GENERAL QUESTIONS -->  <!-- sed-devel@gnu.org for GENERAL QUESTIONS -->
98  <li>  <li>
99    Send general questions or suggestions to the mailing list at:    Send general questions or suggestions to the mailing list at
100    <a href="mailto:sed-devel@gnu.org">sed-devel@gnu.org</a>    &lt;<a href="mailto:sed-devel@gnu.org">sed-devel@gnu.org</a>&gt;.
101  </li>  </li>
102    
103  <!-- bug-sed@gnu.org for BUG REPORTS -->  <!-- bug-sed@gnu.org for BUG REPORTS -->
104  <li>  <li>
105    Report bugs, including version and distribution variant, to the list at:    Report bugs, including version and distribution variant, to the list at
106    <a href="mailto:bug-sed@gnu.org">bug-sed@gnu.org</a><br/> Before    &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    sending the bug, please consult the FAQ and mailing list archives
108    (above).<br/>  Often these perceived bugs are simply due to wrong    (above).<br/>  Often these perceived bugs are simply due to wrong
109    program usage.<br/>  To learn more about reporting bugs,    program usage.<br/>  To learn more about reporting bugs,
110    see <a href="/help/gethelp.html">Getting help with GNU software</a>    see <a href="/software/gethelp.html">Getting help with GNU software</a>.
111  </li>  </li>
112    
113  </ul>  </ul>
114    
115  <h3 id="download">Downloads</h3>  <h3 id="download">Downloads</h3>
116    
117  <p>  <ul>
118  Stable source releases can be found at   <li><strong>Stable source releases</strong> are available on the main
119  <a href="http://ftp.gnu.org/gnu/sed/">http://ftp.gnu.org/gnu/sed/</a>    GNU download server (<a href="https://ftp.gnu.org/gnu/sed/">HTTPS</a>,&nbsp;
120  <a href="ftp://ftp.gnu.org/gnu/sed/">(FTP)</a>    <a href="http://ftp.gnu.org/gnu/sed/">HTTP</a>,&nbsp;
121  <a href="/order/ftp.html">(local mirrors)</a><br/>    <a href="ftp://ftp.gnu.org/gnu/sed/">FTP</a>) and its
122  Test source releases can be found at    <a href="/prep/ftp.html">mirrors</a>. Please
123  <a href="ftp://alpha.gnu.org/gnu/sed/">http://alpha.gnu.org/gnu/sed/</a>    <a href="https://ftpmirror.gnu.org/gnu/sed/">use a mirror</a> if possible.
124  </p>   </li>
125     <li>Some test releases can be found on the GNU &ldquo;alpha&rdquo; server
126      (<a href="https://alpha.gnu.org/gnu/sed/">HTTPS</a>,&nbsp;
127      <a href="http://alpha.gnu.org/gnu/sed/">HTTP</a>,&nbsp;
128      <a href="ftp://alpha.gnu.org/gnu/sed/">FTP</a>) and its
129      <a href="/prep/ftp.html">mirrors</a>.
130     </li>
131    </ul>
132    
133  <h3 id="source">Latest Source</h3>  <h3 id="source">Latest Source</h3>
134    
135  <p>  <p>
136  The latest source with revision history can be browsed using  The latest source with revision history can be browsed using
137  <a href="http://git.sv.gnu.org/cgit/sed.git">cgit</a>,  <a href="https://git.sv.gnu.org/cgit/sed.git">cgit</a> or
138  <a href="http://git.sv.gnu.org/gitweb/?p=sed.git">gitweb</a> or  <a href="https://git.sv.gnu.org/gitweb/?p=sed.git">gitweb</a>.
139  Assuming you have <a href="http://git.or.cz/">git</a> installed, you  Assuming you have <a href="https://git-scm.com/">git</a> installed, you
140  can retrieve the latest version with this command:  can retrieve the latest version with this command:</p>
141  <samp>git clone git://git.sv.gnu.org/sed</samp><br/>  <pre class="emph-box">
142    <samp>git clone git://git.sv.gnu.org/sed</samp>
143    </pre>
144    
145  <!-- TODO: add README-hacking to SED  <!-- TODO: add README-hacking to SED
146  To build from the latest sources please follow the instructions in  To build from the latest sources please follow the instructions in
# Line 145  for production use. Line 169  for production use.
169  -->  -->
170    
171    
172  <h3>Mailing Lists</h3>  <h3 id="mailinglists">Mailing Lists</h3>
173    
174  <p>  <p>
175  You do not need to be subscribed in order to post messages to any GNU  You do not need to be subscribed in order to post messages to any GNU
# Line 155  please be patient when waiting for your Line 179  please be patient when waiting for your
179    
180  <p>  <p>
181  You can subscribe to any GNU mailing list via the web as described  You can subscribe to any GNU mailing list via the web as described
182  below. Or you can send an empty mail with a Subject: header line of  below. Or you can send an empty mail with a <i>Subject:</i> header line of
183  just "subscribe" to the relevant -request list. For example, to  just &ldquo;subscribe&rdquo; to the relevant <i>-request</i> list. For example, to
184  subscribe yourself to the main sed-devel list, you would  subscribe yourself to the main sed-devel list, you would
185  send mail to <a href="mailto:sed-devel-request@gnu.org">  send mail to &lt;<a
186  <em>sed-devel-request@gnu.org</em></a> with no body and a Subject:  href="mailto:sed-devel-request@gnu.org">sed-devel-request@gnu.org</a>&gt;
187  header line of just "subscribe".  with no body and a <i>Subject:</i> header line of just &ldquo;subscribe&rdquo;.
188  </p>  </p>
189    
190  <p>  <p>
191  It has been necessary to moderate the Sed  mailing lists to prevent the  It has been necessary to moderate the sed  mailing lists to prevent the
192  flood of spam. Postings to the lists are held for release by  flood of spam. Postings to the lists are held for release by
193  the list moderator. Sometimes the moderators are unavailable for  the list moderator. Sometimes the moderators are unavailable for
194  brief periods of time. Please be patient when posting. If you  brief periods of time. Please be patient when posting. If you
# Line 172  don't eventually see the message in the Line 196  don't eventually see the message in the
196  get posted.  get posted.
197  </p>  </p>
198    
199    <dl>
200  <h4>Announcements</h4>  <dt>Announcements</dt>
201    <dd>
202  <p>  <p>
203  Important announcements about GNU sed and most other GNU Software are  Important announcements about GNU sed and most other GNU Software are
204  also made on  also made on the
205  <a href="http://lists.gnu.org/mailman/listinfo/info-gnu">  <a href="https://lists.gnu.org/mailman/listinfo/info-gnu">
206    info-gnu@gnu.org mailing list    info-gnu@gnu.org mailing list</a>.
 </a>.  
207  </p>  </p>
208    </dd>
209    
210    <dt>Discussion List</dt>
211    <dd>
 <h4>Discussion List</h4>  
   
212  <p>  <p>
213  The main discussion list for all things related to GNU sed is  The main discussion list for all things related to GNU sed is
214  <a href="https://lists.gnu.org/mailman/listinfo/sed-devel">&lt;<em>sed-devel@gnu.org</em>&gt;</a>.  <a href="https://lists.gnu.org/mailman/listinfo/sed-devel">sed-devel@gnu.org</a>.
215  If you have questions, comments, or other general  If you have questions, comments, or other general
216  discussion about sed then this is the mailing list for that  discussion about sed then this is the mailing list for that
217  discussion.  If you don't know where to start then this is the place  discussion.  If you don't know where to start then this is the place
218  to start.  You can browse and search past postings to the  to start.  You can browse and search past postings to the
219  <a href="http://lists.gnu.org/archive/html/sed-devel/">sed-devel archive</a>.  <a href="https://lists.gnu.org/archive/html/sed-devel/">sed-devel archive</a>.
220  </p>  </p>
221    </dd>
222    
223    <dt>Bug Reports</dt>
224  <h4>Bug Reports</h4>  <dd>
   
225  <p>  <p>
226  If you think you have found a bug in GNU sed, then please send  If you think you have found a bug in GNU sed, then please send
227  as complete a bug report as possible to  as complete a bug report as possible to
228  <a href="http://lists.gnu.org/mailman/listinfo/bug-sed">&lt;bug-sed@gnu.org&gt;</a>,  <a href="https://lists.gnu.org/mailman/listinfo/bug-sed">bug-sed@gnu.org</a>,
229  and it will automatically be entered into the <a href="http://debbugs.gnu.org/sed">  and it will automatically be entered into the <a href="https://debbugs.gnu.org/sed">
230  sed bug tracker</a>.  sed bug tracker</a>.
231  <!-- TODO: sed FAQ?  <!-- TODO: sed FAQ?
232  Before reporting bugs please read the <a href="faq/coreutils-faq.html">FAQ</a>.  Before reporting bugs please read the <a href="faq/coreutils-faq.html">FAQ</a>.
# Line 212  Before reporting bugs please read the <a Line 234  Before reporting bugs please read the <a
234  A very useful and often referenced guide on how to write bug reports  A very useful and often referenced guide on how to write bug reports
235  and ask good questions is the document  and ask good questions is the document
236  <a href="http://www.catb.org/~esr/faqs/smart-questions.html">  <a href="http://www.catb.org/~esr/faqs/smart-questions.html">
237  How To Ask Questions The Smart Way  How To Ask Questions The Smart Way</a>.
 </a>.  
238  You can browse previous postings and search the  You can browse previous postings and search the
239  <a href="http://lists.gnu.org/archive/html/bug-sed/">bug-sed archive</a>.  <a href="https://lists.gnu.org/archive/html/bug-sed/">bug-sed archive</a>.
240  </p>  </p>
241    </dd>
242    
243    <dt>Enhancement Requests</dt>
244  <h4>Enhancement Requests</h4>  <dd>
   
245  <p>  <p>
246  If you would like any new feature to be included in future versions of  If you would like any new feature to be included in future versions of
247  sed, please send a request to <a  sed, please send a request to <a
248  href="http://lists.gnu.org/mailman/listinfo/sed-devel">&lt;sed-devel@gnu.org&gt;</a>.  href="https://lists.gnu.org/mailman/listinfo/sed-devel">sed-devel@gnu.org</a>.
249    
250  This is the general discussion list and a good place to start  This is the general discussion list and a good place to start
251  discussion of a new feature.  After consideration you may be asked to  discussion of a new feature.  After consideration you may be asked to
252  log a request into the bug tracker so that the issue is not lost.  log a request into the bug tracker so that the issue is not lost.
253    
254  If you would like to implement yourself, then note that non trivial changes  If you would like to implement yourself, then note that non trivial changes
255  require copyright assignment to the FSF as detailed in the "Copyright Assignment"  require copyright assignment to the FSF as detailed in the &ldquo;Copyright Assignment&rdquo;
256  <!-- TODO: add HACKING to sed -->  <!-- TODO: add HACKING to sed -->
257  section of GNU coreutils <a href="http://git.sv.gnu.org/cgit/coreutils.git/plain/HACKING">HACKING</a> notes.  section of GNU coreutils <a href="https://git.sv.gnu.org/cgit/coreutils.git/plain/HACKING">HACKING</a> notes.
258  </p>  </p>
259    </dd>
260    
261  <h4>Mailing List Etiquette</h4>  <dt>Mailing List Etiquette</dt>
262    <dd>
263  <p>  <p>
264  Please do not send messages encoded as HTML nor encoded as base64 MIME  Please do not send messages encoded as HTML nor encoded as base64 MIME
265  nor included as multiple formats.  nor included as multiple formats.
266  Please send messages as  Please send messages as
267  <a href="http://stagecraft.theprices.net/nomime.html">plain text</a>.  <a href="https://web.archive.org/web/20160305050159/http://stagecraft.theprices.net/nomime.html">
268    plain text</a>.
269  Please include a descriptive subject line. If all of the subjects are  Please include a descriptive subject line. If all of the subjects are
270  <em>bug</em> then it is impossible to differentiate them.  <em>bug</em> then it is impossible to differentiate them.
271  Please avoid sending large messages, such as log files, system call  Please avoid sending large messages, such as log files, system call
# Line 256  Please remember that development of GNU Line 279  Please remember that development of GNU
279  can also contribute to its development. For information about contributing  can also contribute to its development. For information about contributing
280  to the GNU Project, please read <a href="/help/">How to help GNU</a>.  to the GNU Project, please read <a href="/help/">How to help GNU</a>.
281  </p>  </p>
282    </dd>
283    </dl>
284    
285    <h3 id="maintainers">Maintainers</h3>
 <h3>Maintainers</h3>  
286    
287  <p>  <p>
288  GNU Sed is currently being maintained by  GNU sed is currently being maintained by
289  Jim Meyering <a href="mailto:jim@meyering.net"><em>jim@meyering.net</em></a>,  Jim Meyering &lt;<a href="mailto:jim@meyering.net">jim@meyering.net</a>&gt;,
290  and  and
291  Assaf Gordon <a href="mailto:assafgordon@gmail.com"><em>assafgordon@gmail.com</em></a>.  Assaf Gordon &lt;<a href="mailto:assafgordon@gmail.com">assafgordon@gmail.com</a>&gt;.
292  </p>  </p>
293    
294    
295    </div>
   
296  </div><!-- for id="content", starts in the include above -->  </div><!-- for id="content", starts in the include above -->
297  <!--#include virtual="/server/footer.html" -->  <!--#include virtual="/server/footer.html" -->
298  <div id="footer">  <div id="footer">
# Line 281  There are also <a href="/contact/">other Line 304  There are also <a href="/contact/">other
304  the FSF.  Broken links and other corrections or suggestions can be sent  the FSF.  Broken links and other corrections or suggestions can be sent
305  to <a href="mailto:sed-devel@gnu.org"><em>sed-devel@gnu.org</em></a>.  to <a href="mailto:sed-devel@gnu.org"><em>sed-devel@gnu.org</em></a>.
306  </p>  </p>
307    
308    <p>Please see the <a
309    href="/server/standards/README.translations.html">Translations
310    README</a> for information on coordinating and contributing translations
311    of this article.</p>
312  </div>  </div>
313    
314  <!-- Regarding copyright, in general, standalone pages (as opposed to  <!-- Regarding copyright, in general, standalone pages (as opposed to
Legend:
Removed from v.1.10  
changed lines
  Added in v.1.11
savannah-hackers-public@gnu.org
 ViewVC Help
Powered by ViewVC 1.1.26