Anonymous | Login | 2024-04-25 12:07 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||
ID | Category | Severity | Type | Date Submitted | Last Update | ||
0000264 | [1003.1(2008)/Issue 7] Shell and Utilities | Objection | Error | 2010-06-23 03:15 | 2010-06-25 16:31 | ||
Reporter | eblake | View Status | public | ||||
Assigned To | ajosey | ||||||
Priority | normal | Resolution | Duplicate | ||||
Status | Closed | ||||||
Name | Eric Blake | ||||||
Organization | Red Hat | ||||||
User Reference | ebb.sed2 | ||||||
Section | sed | ||||||
Page Number | 3156 | ||||||
Line Number | 104908 | ||||||
Interp Status | --- | ||||||
Final Accepted Text | |||||||
Summary | 0000264: sed addr in braces | ||||||
Description |
The description of the { command verb begins: [2addr] {function function ... } Execute a list of sed functions only when the pattern space is selected. Since it refers to "function(s)", and the beginning of the EXTENDED DESCRIPTION says a function is a command verb followed by any applicable arguments, this means sed is not required to support the use of addresses within braces. It seems likely that this is unintentional, as such usage is common in applications (and applications which use it do not appear to be having any portability problems). For example: sed -n '1,/^$/{ /^Subject: /p }' To require sed to support the use of addresses within braces, the description should use the term "editing command" instead of "function". |
||||||
Desired Action |
Change "function" to "editing command" throughout the description of the { command verb. |
||||||
Tags | No tags attached. | ||||||
Attached Files | |||||||
|
Relationships | |||||||
|
Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |