Bug 85103
| Summary: | sh(1) manpage doesn't contain the word "comment", etc. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Documentation | Reporter: | Gary W. Swearingen <garys> | ||||
| Component: | Books & Articles | Assignee: | freebsd-doc (Nobody) <doc> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
On 2005-08-18 17:41, "Gary W. Swearingen" <garys@opusnet.com> wrote: > The sh(1) manpage doesn't describe "#" comments or contain the > word "comment" for people searching for that. > > The "pdksh" manpage slips in this phrase: > > #, if used at the beginning of a word, introduces a comment -- > everything after the # up to the nearest newline is ignored; > > but it should also say something about it not working interactively. It does work interactively too: % flame:/home/keramida$ env PS1='$ ' sh % $ echo foo # bar % foo % $ But you're right we should add something about comments. Hello, Here is diff. -- Sincerely, Daniel Gerzo State Changed From-To: open->closed Committed. Thanks! |
The sh(1) manpage doesn't describe "#" comments or contain the word "comment" for people searching for that. Fix: The "pdksh" manpage slips in this phrase: #, if used at the beginning of a word, introduces a comment -- everything after the # up to the nearest newline is ignored; but it should also say something about it not working interactively.