Hello Doug,
for (1), I am CCing Michael Kerrisk — and the procedure to report issues on
the man pages is tracked here
https://www.kernel.org/doc/man-pages/reporting_bugs.html (In brief: email
mtk.manpa...@gmail.com and CC linux-...@vger.kernel.org).
Best -Federico
> On Dec 27, 2019, at 1
:18 PM, Ingo Schwarze wrote:
>
> Hi Federico,
>
> Federico Lucifredi wrote on Fri, Dec 27, 2019 at 01:31:00PM -0500:
>
>> for (1), I am CCing Michael Kerrisk
>
> fortunately, you forgot to, unless you used Bcc:.
>
>> and the procedure to report issues on
Hello Raf,
>
> Also, when it comes to history of *roff from the UNIX manpages
> angle, this[0] is a good place to visit.
>
> [0] https://manpages.bsd.lv/history.html
>
That is awesome, it is one of the best stories of man yet (there was a good
conference talk a few years back as well, I will
Hello Ingo,
> On Oct 14, 2020, at 7:10 AM, Ingo Schwarze wrote:
>
> Finally, there is an obvious, rather serious error. I do not think
> misattribution should be taken lightly:
>
> the man macro package, originally written by James Clark
>
> The correct statement is:
>
> The man language f
Hello Ingo,
> On Oct 14, 2020, at 9:06 AM, Ingo Schwarze wrote:
> [..]
>
>> Interesting. As far as I can tell, the origin of that statement
>> is in man 7 groff_man:
>> http://manpages.ubuntu.com/manpages/trusty/man7/groff_man.7.html
>
> That document says:
>
> DESCRIPTION
> The man macros u
Hi James
> On Oct 14, 2020, at 12:08 PM, James K. Lowden
> wrote:
>
> On Wed, 14 Oct 2020 11:13:39 -0400
> Federico Lucifredi wrote:
>
>>> For man pages, what you need is knowledge of the man macro package,
>>> originally written by James Clark [...]
&
I will look at this during the weekend and get back to you. It should not be
difficult with Werner's comments.
When you first raised this, you were ahead of the curve. Fixing it then was
harder than it is today... Time to get it done.
Best-F
Sent from my iPhone
> On Sep 26, 2013, at 3:43 PM,
Sorry guys, traveling till Sunday. Will comment then.
Best-F
Sent from my iPhone
> On Sep 26, 2013, at 3:43 PM, Werner LEMBERG wrote:
>
>
>> My conclusion is that the coding tag in the man page is not working,
>> even when you disable all preprocessors and the coding tag gets to
>> the secon
On Sep 26, 2013, at 4:32 AM, Colin Watson wrote:
>> Assuming that the problem is caused by `-p', a possible solution is to
>> not use this man option or environment variable and add option `-t' to
>> nroff in `/etc/man.conf'.
>
> Or use man-db instead, which is much smarter about character enco
> On Thu, Sep 26, 2013 at 05:55:52PM -0400, Federico Lucifredi wrote:
>> On Sep 26, 2013, at 4:32 AM, Colin Watson wrote:
>>> Or use man-db instead, which is much smarter about character encodings
>>> and handles your situation out of the box with no configuration
>
On Feb 26, 2014, at 8:19 AM, Ralph Corderoy wrote:
> Hi Walter,
>
>> Man pages are not tutorials or complete manuals
>
> Yes they are, or should be. They used to be. I learnt Perl 4 from
> perl(1). Back then it was a single long man page, well-written by an
> experienced Unix hand, Larry Wa
While we are (slightly) digressing, may I ask the broader group, what are the
best current tutorials for Groff?
Most of the material I know of is… rather dated. Not necessarily bad, but not
very recent either - and not very concise, either. What do you point to get
new users started? What’s th
On 03/01/2014 04:41 PM, Colin Watson wrote:
I think it makes more sense to make sureman:foo and similar URLs do
sensible things in all the browsers people use. While there are
exceptions, if you want to see something in a browser, it's usually more
natural to start from that browser's URL bar.
Hi Johann,
If you confined yourself to writing man pages, you do not need to learn the
whole of Troff, and you can limit yourself to a more friendly subset — and
copying from the many examples found on a *nix system surely helps ;-)
For man page writing, I collected the available resources i
14 matches
Mail list logo
