Date: Wed, 25 Oct 2017 14:49:26 +0100 From: Rafal Lukawiecki <raf@rafal.net> To: "James B. Byrne via freebsd-questions" <freebsd-questions@freebsd.org> Subject: Re: A request to segregate man pages for shell built-ins Message-ID: <3A716B0D-8291-4CB1-9DE5-370ABA4CF583@rafal.net> In-Reply-To: <57bd52d4-bf61-454f-1b11-d7f96aa1c049@sjmulder.nl> References: <VI1PR02MB1200817E0E2CDD2A2A42E1A5F6440@VI1PR02MB1200.eurprd02.prod.outlook.com> <f88cd63e-3cbc-4463-5219-99d204742b85@FreeBSD.org> <6f62db58-8220-0fe4-133b-410da2f58579@qeng-ho.org> <f88bce52-b120-c9cf-05bf-3c99ab99c522@FreeBSD.org> <57bd52d4-bf61-454f-1b11-d7f96aa1c049@sjmulder.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
For what it is worth, I would have found this segregated access to man for shell built-ins very useful in the last two months, as I have been rapidly re-skilling from bash/Linux to sh/FreeBSD. I spent too much time browsing the net while, ideally, most of it could have come from man. Anything that makes it easier to get up to speed with sh is going to make FreeBSD more accessible, especially to those coming from bash, in my opinion. However, it is also quite useful to have a single, long document on sh, which is capable of covering the more general issues such as variable scope and flow control. I wonder if there is a risk that a segregated approach could remove that important benefit. -- Rafal Lukawiecki Data Scientist Project Botticelli Ltd
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A716B0D-8291-4CB1-9DE5-370ABA4CF583>