Hi Dave,
> However, even Branden's more stringent requirement can be met by
> turning the parenthetical sentence into a subordinate clause:
>
> They can be specified in any lettercase (unlike in AT&T tbl, which
> accepted only options with all characters in the same lettercase) and
> must be separ
Hi Branden,
> Do you think I should go further and warn man page authors away from
> attempting to redefine these macros in their pages?
No, I think you should go less and not change the headers and footers so
as to inspire the man-page author to correct the deviancy. :-)
--
Cheers, Ralph.
Hi Branden,
> You can _do_ the table of contents in one pass; relocating it to the
> front matter requires either a second pass or a post-processing tool.
> An index is a much bigger pain because it has to be sorted.
I have idly wondered from time to time if one diversion after another
could be c
[Sending to the list, now that I have access to a computer.
I also added a bit more to it.]
Hi Branden!
On 7/23/22 04:50, G. Branden Robinson wrote:
Thank you; I appreciate the review. Yours is the first it's gotten
since I rewrote it.
[
spaces, or tabs. (AT&T tbl accepted only o
Hi Ingo,
On 7/23/22 21:29, Ingo Schwarze wrote:
Hi Alejandro,
On 7/22/22 12:35, Alejandro Colomar (man-pages) wrote:
BTW, I think I didn't reply (or if I did was very short) to your comment
that other languages may find it difficult to mirror our use of
subsections, since their main section i
At 2022-07-24T11:19:19+0100, Ralph Corderoy wrote:
> How about this middle paragraph, with the other two unaltered ones for
> context.
>
> The line immediately following the .TS token may specify region options:
> keywords that influence the interpretation or rendering of the region as
>
At 2022-07-24T11:35:45+0100, Ralph Corderoy wrote:
> > You can _do_ the table of contents in one pass; relocating it to the
> > front matter requires either a second pass or a post-processing
> > tool. An index is a much bigger pain because it has to be sorted.
>
> I have idly wondered from time
On 7/23/22 21:30, G. Branden Robinson wrote:
IMO system_data_types(7) bit off too much to chew. The Linux system
programming interface is a collection of independently developed
components, generally with loose coupling. At the risk of repeating
myself, I think the data types of these compon
Hi Branden,
On 7/23/22 21:30, G. Branden Robinson wrote:
If I were to rewrite the C library and kernel from scratch, without
backwards compatibility, I'd fix many many things. But that train
passed many years before I was born.
Lightning will not strike in the same way again. But we are engi
Hi Alex,
At 2022-07-24T12:36:43+0200, Alejandro Colomar (man-pages) wrote:
> And the Spanish rules also indicate that the level of isolation from
> the main text is, from more isolation to less isolation: em dash,
> commas, parentheses.
I don't have a citation for this, but my impression as a gra
Hi Branden and Ralph,
On 7/24/22 12:25, Ralph Corderoy wrote:
Hi Branden,
Do you think I should go further and warn man page authors away from
attempting to redefine these macros in their pages?
No, I think you should go less and not change the headers and footers so
as to inspire the man-pa
Hi Dave,
On 7/23/22 16:58, Dave Kemper wrote:
On 7/23/22, G. Branden Robinson wrote:
That's _still_ too general a claim, but it
will take me some time to find a way to articulate it well.
No need; we don't have to document our personal punctuation principles
here. We've resolved this tbl ma
Hi Ralph,
On 7/23/22 12:36, Ralph Corderoy wrote:
Hi Alejandro,
Wandering off-topic...
$ find man* -type f \
| tr '[:upper:]' '[:lower:]' \
| sort \
| uniq -d \
| while read f; do
find man* -type f \
| grep -i $f;
done;
man2/_Exit.2
man2/_exit.2
man3/nan.3
On Sunday, 24 July 2022 03:08:01 BST G. Branden Robinson wrote:
> At 2022-07-23T18:30:22-0700, Larry McVoy wrote:
> > (a) the two pass thing so you could easily do a table of contents and
>
> You can _do_ the table of contents in one pass; relocating it to the
> front matter requires either a seco
Hi Ralph!
On 7/23/22 12:23, Ralph Corderoy wrote:
Hi Alejandro,
As hinted in recent mails to groff@ and linux-man@,
I'm going to inaugurate a new [sub]section for constants.
This seems a bad idea. They're quite at home in section 3.
Others disagree, with the argument that 3 is reserved fo
Hi Alejandro,
Alejandro Colomar wrote on Sun, Jul 24, 2022 at 01:20:46PM +0200:
> On 7/23/22 21:29, Ingo Schwarze wrote:
>> On 7/22/22 12:35, Alejandro Colomar (man-pages) wrote:
>>> BTW, I think I didn't reply (or if I did was very short) to your comment
>>> that other languages may find it diff
Hi Alex,
> > $ grep -m1 ^ `find -type f | sort -f | uniq -Di`
>
> I'm a big fan of pipes and xargs(1). I only use `` or $() when I
> _really_ need to. I'd use:
>
> $ find -type f | sort -f | uniq -Di | xargs grep -m1 ^
I too use xargs(1). But beware its defaults. Unless I know the nature
At 2022-07-24T16:57:19+0200, Ingo Schwarze wrote:
> But dismissing decade-old *BSD standards like the use of /usr/ for the
> base system and /usr/local/ for packages as a standard violation, and
> promoting /opt/ which is firmly a Linux-only invention,
Oh, no it's not. I remember that thing from
On Sun Jul 24, 2022 at 8:06 AM EDT, G. Branden Robinson wrote:
> At 2022-07-24T03:17:44+, DJ Chase wrote:
> > On Sat Jul 23, 2022 at 10:08 PM EDT, G. Branden Robinson wrote:
> > > I don't think the lack of availability of troff source mattered much
> > > since groff had been out for 10 years by
At 2022-07-24T15:45:46+, DJ Chase wrote:
> On Sun Jul 24, 2022 at 8:06 AM EDT, G. Branden Robinson wrote:
> > At 2022-07-24T03:17:44+, DJ Chase wrote:
> > > I’ve never read the Texinfo manual; I learned *roff through Unix
> > > For People,[1] then various online materials maybe half a year
Hi Ingo,
On 7/24/22 16:57, Ingo Schwarze wrote:
[...]
I'm not happy with this approach. I don't want to be typing paths for
system stuff (your /usr/local is /usr in GNU/Linux systems;
Then use an alias like
alias tclman='man -M /usr/local/lib/tcl/tcl8.5/man/'
It's not like users are norm
Hi Ingo and Branden!
On 7/24/22 16:57, Ingo Schwarze wrote:
> P.S.
> I moved this to the bottom because it is off-topic:
>
> Alejandro Colomar wrote on Sun, Jul 24, 2022 at 01:20:46PM +0200:
>> BTW, that's a thing I don't like at all from BSDs; IMO (and FHS's),
>
> Years ago, i tried to engage wi
On Sun Jul 24, 2022 at 12:11 PM EDT, G. Branden Robinson wrote:
> At 2022-07-24T15:45:46+, DJ Chase wrote:
> > I just read some of it. I wish I read it when it felt like I was
> > fighting with the typesetter — it’s very helpful.
>
> I should correct myself. I've only been hacking on our Texin
At 2022-07-24T17:49:56+, DJ Chase wrote:
> On Sun Jul 24, 2022 at 12:11 PM EDT, G. Branden Robinson wrote:
> > At 2022-07-24T15:45:46+, DJ Chase wrote:
> > > I just read some of it. I wish I read it when it felt like I was
> > > fighting with the typesetter — it’s very helpful.
> >
> > I sh
Reported-by: "G. Branden Robinson"
Cc: Ralph Corderoy
Cc: Ingo Schwarze
Signed-off-by: Alejandro Colomar
---
v2:
- Move to man3const [Ralph, Branden]
- Added LIBRARY section
- Added #include [Ralph]
- Note that it can also be used as a function pointer [Ralph]
- Document that 0 is another nul
Reported-by: "G. Branden Robinson"
Cc: Ralph Corderoy
Cc: Ingo Schwarze
Signed-off-by: Alejandro Colomar
---
v2:
- Move to man3const [Ralph, Branden]
- Added LIBRARY section
- Added #include [Ralph]
- Note that it can also be used as a function pointer [Ralph]
- Document that 0 is another nu
On Sun Jul 24, 2022 at 2:02 PM EDT, G. Branden Robinson wrote:
> At 2022-07-24T17:49:56+, DJ Chase wrote:
> > On Sun Jul 24, 2022 at 12:11 PM EDT, G. Branden Robinson wrote:
> > > At 2022-07-24T15:45:46+, DJ Chase wrote:
> > > > Good luck; It’s out of print and physical copies are very hard
On Sun, Jul 24, 2022 at 11:11:10AM -0500, G. Branden Robinson wrote:
> At 2022-07-24T15:45:46+, DJ Chase wrote:
> > On Sun Jul 24, 2022 at 8:06 AM EDT, G. Branden Robinson wrote:
> > > At 2022-07-24T03:17:44+, DJ Chase wrote:
> > > > I???ve never read the Texinfo manual; I learned *roff thr
On Sun Jul 24, 2022 at 4:18 PM EDT, Larry McVoy wrote:
> Am I the only person who thinks that have *roff documentation in a different
> markup is crazy?
>
> I wrote a couple source management systems, this is like I was storing
> BitKeeper in Git. That says I trust Git but not my own code.
>
> Has
On Sun, Jul 24, 2022 at 08:42:32PM +, DJ Chase wrote:
> On Sun Jul 24, 2022 at 4:18 PM EDT, Larry McVoy wrote:
> > Am I the only person who thinks that have *roff documentation in a different
> > markup is crazy?
> >
> > I wrote a couple source management systems, this is like I was storing
> >
On Sun Jul 24, 2022 at 4:57 PM EDT, Larry McVoy wrote:
> On Sun, Jul 24, 2022 at 08:42:32PM +, DJ Chase wrote:
> > 1. People might need to read the documentation for a format’s tools
> > before they can read files in that format (this isn’t the case for
> > Groff specifically, but a
[dropped DJ from Cc]
At 2022-07-24T13:18:46-0700, Larry McVoy wrote:
> Has anyone proposed redoing the texinfo stuff in Groff?
You do, approximately every time the subject comes up.[1] ;-)
> Am I the only person who thinks that have *roff documentation in a
> different markup is crazy?
In lite
On 7/24/22, Larry McVoy wrote:
> I don't use the texinfo manual because it
> is very emacs-like and I'm a vi person.
A trick I learned on this list a while back is that you can read the
info manual's content without using the info interface simply by
piping the "info" command: "info groff | less"
On Sun, Jul 24, 2022 at 06:27:58PM -0500, Dave Kemper wrote:
> On 7/24/22, Larry McVoy wrote:
> > I don't use the texinfo manual because it
> > is very emacs-like and I'm a vi person.
>
> A trick I learned on this list a while back is that you can read the
> info manual's content without using th
On Sunday, July 24, 2022, Larry McVoy wrote:
>
> Am I the only person who thinks that have *roff documentation in a
> different
> markup is crazy?
>
> I wrote a couple source management systems, this is like I was storing
> BitKeeper in Git. That says I trust Git but not my own code.
>
> Has anyo
On Sun Jul 24, 2022 at 12:11 PM EDT, G. Branden Robinson wrote:
> At 2022-07-24T15:45:46+, DJ Chase wrote:
> > On Sun Jul 24, 2022 at 8:06 AM EDT, G. Branden Robinson wrote:
> > > At 2022-07-24T03:17:44+, DJ Chase wrote:
> > > > I’ve never read the Texinfo manual; I learned *roff through Un
36 matches
Mail list logo
