From: Alejandro Colomar <alx.manpages@gmail.com>
To: Oran Bodner <OJBodner@hotmail.com>, "alx@kernel.org" <alx@kernel.org>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: tput man page
Date: Mon, 17 Apr 2023 19:19:45 +0200 [thread overview]
Message-ID: <3973a1bf-33b4-2e12-d5c5-021c3128f5c3@gmail.com> (raw)
In-Reply-To: <TY0PR0101MB4214981A3155E7D25FC5FB00DA9C9@TY0PR0101MB4214.apcprd01.prod.exchangelabs.com>
[-- Attachment #1.1: Type: text/plain, Size: 2015 bytes --]
Hi Oran,
On 4/17/23 10:55, Oran Bodner wrote:
> Hi, I happened upon your man page for tput https://man7.org/linux/man-pages/man1/tput.1.html
This page is part of the ncurses project, not of the Linux man-pages project.
The Linux man-pages project is concerned mostly just about glibc and the
Linux kernel (so man2 and man3), with little pages apart from those.
To report this bug, please follow the COLOPHON section at the bottom of that
page:
COLOPHON
This page is part of the ncurses (new curses) project.
Information about the project can be found at
⟨https://www.gnu.org/software/ncurses/ncurses.html⟩. If you have
a bug report for this manual page, send it to
bug-ncurses-request@gnu.org. This page was obtained from the
project's upstream Git mirror of the CVS repository
⟨https://github.com/mirror/ncurses.git⟩ on 2022-12-17. (At that
time, the date of the most recent commit that was found in the
repository was 2022-12-11.) If you discover any rendering
problems in this HTML version of the page, or you believe there
is a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to
man-pages@man7.org
Thanks,
Alex
> It is stated there that:
>
> The tput command was begun by Bill Joy in 1980.
>
> But I was actually the developer of this command.
> I proposed and wrote the command in 1983 while working at Bell labs
> https://www.linkedin.com/in/oran-bodner-b31245/details/experience/?profileId=ACoAAAAJBBUBcz6WMyu34xG8bufekJZ3i9g-oR8
>
> https://www.linkedin.com/in/oran-bodner-b31245/overlay/50057788/single-media-viewer/?profileId=ACoAAAAJBBUBcz6WMyu34xG8bufekJZ3i9g-oR8
>
> Thx, Oran Bodner
>
>
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2023-04-17 17:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <TY0PR0101MB4214981A3155E7D25FC5FB00DA9C9@TY0PR0101MB4214.apcprd01.prod.exchangelabs.com>]
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=3973a1bf-33b4-2e12-d5c5-021c3128f5c3@gmail.com \
--to=alx.manpages@gmail.com \
--cc=OJBodner@hotmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
/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 NNTP newsgroup(s).