Hi,
If you look at the manual in Groff for fonts. You see that you can use the
-F option to specify a directory for your projects fonts.
Eg: Groff -F /home/project1/fonts
But in the fonts directory you have to place your fonts in the right device
directory. For postscript is devps. For pdf is dev
The contents of man pages are not groff's business. If a man page must
be conditioned by what's on a local system, that can likely be done
with .sy. But man(1) should not enable .sy. Enjoy the catch-22.
Another reason to keep the status quo in regard to referring to
nonexistent man pages is that s
On Sat, Oct 30, 2021, Larry McVoy wrote:
> If the proposal is to remove See Also's that aren't installed, I
> could not be more against that idea. That just makes the system
> harder to learn.
I don't have a position on this because I've never given it a
moment's thought. That said, surely a bet
On Sat, 30 Oct 2021 14:48:46 -0700
Larry McVoy wrote:
> If James is suggesting that dangling links are not helpful, I find
> the opposite to be true.
I too have benefited from pursuing hints I found in SEE ALSO, even for
uninstalled software. I remember one weekend searching to for a free
impl
On Sat, Oct 30, 2021 at 04:42:24PM -0700, Larry McVoy wrote:
> Subject: Re: SEE ALSO fails
>
> If the proposal is to remove See Also's that aren't installed, I
> could not be more against that idea. That just makes the system
> harder to learn.
>
> If I'm way off base, my apologies, please corre
On Sat, Oct 30, 2021 at 07:12:37PM -0400, Steve Izma wrote:
> On Sat, Oct 30, 2021 at 07:53:13PM +0200, Ingo Schwarze wrote:
> > Subject: Re: SEE ALSO fails
> >
> > James K. Lowden wrote on Sat, Oct 30, 2021 at 12:08:03PM -0400:
> >
> > > A longstanding complaint of mine regarding Linux man pages
On Sat, Oct 30, 2021 at 07:53:13PM +0200, Ingo Schwarze wrote:
> Subject: Re: SEE ALSO fails
>
> James K. Lowden wrote on Sat, Oct 30, 2021 at 12:08:03PM -0400:
>
> > A longstanding complaint of mine regarding Linux man pages is
> > that they frequently have broken SEE ALSO references. I
> > won
Me too. I though the OS write comparing BSD to Linux is spot on. Linux
is like C, it lets you do whatever you want but be careful what you want.
While it is not the prettiest to say "Whatever not found" it gives you
a hint to go look for Whatever. Those hints can save your butt.
If James is su
Add my voice to those saying to never delete those references: even if the
corresponding packages aren't installed, given the reference in the manual
page I can finding them using different means. If they're not in the
manual page, I don't have that opportunity.
On Sat, Oct 30, 2021 at 12:08 PM J
On Sat, 30 Oct 2021 19:53:13 +0200
Ingo Schwarze wrote:
> >> .Sh SEE ALSO
> >> .Xr mg 1 ,
> >> .Xr vi 1 ,
> >> .Xr editline 3edit ,
> >> .Xr el_wgets 3 ,
> >> .Xr el_wpush 3 ,
> >> .Xr el_wset 3 ,
> >> .Xr editrc 5edit
>
> > What, I wonder, is "mg"?
> >
> > $ man mg
> > No manual entr
On 10/30/21 19:53, Ingo Schwarze wrote:
Hi James,
James K. Lowden wrote on Sat, Oct 30, 2021 at 12:08:03PM -0400:
A longstanding complaint of mine regarding Linux man pages is that they
frequently have broken SEE ALSO references. I wonder if there's not
something the groff project could do to
Hi James,
James K. Lowden wrote on Sat, Oct 30, 2021 at 12:08:03PM -0400:
> A longstanding complaint of mine regarding Linux man pages is that they
> frequently have broken SEE ALSO references. I wonder if there's not
> something the groff project could do to encourage packaging systems to
> avo
On Wed, 27 Oct 2021 20:15:28 +1100
John Gardner wrote:
> There's already a deprecation warning in-place warning users against
> relying on the existence of /bin/bash or the assumption that /bin/sh
> == /bin/bash.
Every so often I get a +10 bump on SO for my answer about writing a
portable shell
A longstanding complaint of mine regarding Linux man pages is that they
frequently have broken SEE ALSO references. I wonder if there's not
something the groff project could do to encourage packaging systems to
avoid such errors.
Today's page in question is edltline(3), the BSD complement to
re
On Wed, 27 Oct 2021 18:11:36 +1100
"G. Branden Robinson" wrote:
Thanks for the explanation.
> There are multiple competing implementations of all of these except
> Perl (which competes mostly with its own release history).
Heh.
I have occassionally been bitten by mawk/gawk differences. One I
15 matches
Mail list logo
