public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: cannot display man page for /bin/passwd
Date: Wed, 06 Aug 2014 20:05:00 -0000	[thread overview]
Message-ID: <613520457.20140806235725@yandex.ru> (raw)
In-Reply-To: <20140806193059.GO13601@calimero.vinschen.de>

Greetings, Corinna Vinschen!

>> >> When I try to display the man page for /bin/passwd, the man page for
>> >> the openssl passwd subcommand is displayed.
>> >> 
>> >> It appears that both the package containing /bin/passwd, and the
>> >> openssl package place the passwd.1.gz file in the /usr/share/man/man1
>> >> directory, so that only the man page from the most recently installed
>> >> package is displayed.
>> 
>> > No, the Cygwin passwd tool has no man page.
>> 
>> That's sad. Can we change it?

> Would you like to take over maintainance of the cygwin-doc package?
> It's orphaned and in desperate need of an active maintainer.

That's tempting. I'll think about it. It doesn't involve deep knowledge in
the C language, I assume? (Which I'm lacking.)

>> Also, the paragraph "All operations affecting the current user" is missing a
>> "$" sign in reference to environment variable LOGONSERVER.

> No, that's deliberate at this point.

If we are to think about it as actual Windows environment variable being
propagated to affect Cygwin processes, it makes sense.
I'll amend the man page in this regard.

>> The phrase "to enter a password which" is probably missing a comma.

> Hmm, not sure.  The English language is pretty lazy in terms of
> punctuation characters.

Uhhu...

>> Slightly unrelated question. I've noticed, that if a paragraph in source file
>> have line break after a period, the page is rendered with two spaces between
>> a period and first letter of next sentence, even though there's only one
>> character (a linefeed) exists. No stray spaces, no CR's. Is this intended?

> Yes, for the English language.  See
> http://en.wikipedia.org/wiki/History_of_sentence_spacing#French_and_English_spacing

Thanks. It was looked deliberate, judging from reproducibility on a number of
available systems, was just unsure, why.
Should probably follow locale settings, though... And it looks weird on
fixed-width terminal, especially if you are using pretty-printing font (with
most of punctuation shifted to the left). Looks almost like there's 3 spaces
between sentences.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 06.08.2014, <23:46>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2014-08-06 20:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 19:48 Doug Henderson
2014-08-05  8:21 ` Corinna Vinschen
2014-08-05 13:43   ` Nellis, Kenneth
2014-08-05 14:01     ` Corinna Vinschen
2014-08-05 15:09   ` Doug Henderson
2014-08-05 16:48     ` Larry Hall (Cygwin)
2014-08-05 17:45       ` Doug Henderson
2014-08-06 17:35   ` Andrey Repin
2014-08-06 19:31     ` Corinna Vinschen
2014-08-06 20:05       ` Andrey Repin [this message]
2014-08-06 20:45         ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=613520457.20140806235725@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).