Bug 85103 - sh(1) manpage doesn't contain the word "comment", etc.
Summary: sh(1) manpage doesn't contain the word "comment", etc.
Status: Closed FIXED
Alias: None
Product: Documentation
Classification: Unclassified
Component: Books & Articles (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-doc (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-19 01:50 UTC by Gary W. Swearingen
Modified: 2006-01-01 16:14 UTC (History)
0 users

See Also:


Attachments
sh.1.diff (429 bytes, patch)
2005-12-31 13:44 UTC, Daniel Gerzo
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gary W. Swearingen 2005-08-19 01:50:19 UTC
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.
Comment 1 Giorgos Keramidas 2005-08-19 13:52:06 UTC
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.
Comment 2 Daniel Gerzo 2005-12-31 13:44:10 UTC
Hello,

   Here is diff.

-- 
Sincerely,
   Daniel Gerzo
Comment 3 Stefan Farfeleder freebsd_committer freebsd_triage 2006-01-01 16:14:12 UTC
State Changed
From-To: open->closed

Committed.  Thanks!