Re: TAB character in groff output

At 2022-08-16T00:01:40+0200, Alejandro Colomar wrote: > I like it. I applied a patch with exactly that (but .MR -> .BR; I'll still > wait a few years before using that). BTW, Branden, did you notice? :P Yes. :D But waiting a "few years", oof! Well, it'll come sooner if we can get our official

Re: TAB character in groff output

Hi Alejandro, Alejandro Colomar wrote on Tue, Aug 16, 2022 at 12:01:40AM +0200: > Ingo, is mandoc(1) planning to support .MR? Yes, almost certainly. I'm not enthusiastic about it, but given that groff is going ahead with it, it is clearly better to support it than to not support it. The most l

Re: TAB character in groff output

Hi Ingo, On 8/16/22 00:01, Alejandro Colomar wrote: I like it.  I applied a patch with exactly that (but .MR -> .BR; I'll still wait a few years before using that).  BTW, Branden, did you notice? :P

Re: TAB character in groff output

On 8/11/22 14:34, Ingo Schwarze wrote: Hi Alejandro, sorry for getting distracted and returning late to the party. Alejandro Colomar wrote on Tue, Aug 02, 2022 at 05:14:47PM +0200: [...] $ make lint-man-mandoc LINT (mandoc) tmp/lint/man7/spufs.7.lint-man.mandoc.touch mandoc: man7/spufs.7:

Re: TAB character in groff output

Hi Alejandro, sorry for getting distracted and returning late to the party. Alejandro Colomar wrote on Tue, Aug 02, 2022 at 05:14:47PM +0200: [...] > $ make lint-man-mandoc > LINT (mandoc) tmp/lint/man7/spufs.7.lint-man.mandoc.touch > mandoc: man7/spufs.7:748:7: WARNING: tab in filled text My g

Re: TAB character in groff output

On Tuesday, 2 August 2022 17:58:38 BST Ingo Schwarze wrote: > Then again, the wording > > "Typeset the glyph with code n in the current font ..." > > does provide an *implicit* hint that this can hardly be expected to > be device-independent. > > > when attempting it on a platform that uses IB

Re: TAB character in groff output

Hi Ingo, On 8/2/22 18:58, Ingo Schwarze wrote: [...] when attempting it on a platform that uses IBM code page 1047 as its input encoding. ;-) I would have expected the *output* font numbering to cause even more serious trouble than the *input* encoding. Besides, not being a masochist to that

Re: TAB character in groff output

Hi Branden, G. Branden Robinson wrote on Tue, Aug 02, 2022 at 10:42:45AM -0500: > At 2022-08-02T15:44:21+0200, Ingo Schwarze wrote: >> In groff, this works for me: >> >> $ printf "aN'9'b" | groff -T ascii | hexdump -C | head -n 1 >> 61 09 62 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a

Re: TAB character in groff output

At 2022-08-02T15:44:21+0200, Ingo Schwarze wrote: > In groff, this works for me: > > $ printf "aN'9'b" | groff -T ascii | hexdump -C | head -n 1 > 61 09 62 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a |a.b.| > > Mandoc behaves differently and treats \N'9' exactly like a lit

Re: TAB character in groff output

At 2022-08-02T14:14:58+0200, Alejandro Colomar wrote: > I'd like to be able to produce ASCII HT ('\t' - horizontal tab) in man > pages output. I don't want to align things; I do want a tab > character. Rationale: examples in fstab(5). > > Is that possible? I didn't find anything in groff_char(7)

Re: TAB character in groff output

Hi Ingo, On 8/2/22 15:44, Ingo Schwarze wrote: Hi Alejandro, Alejandro Colomar wrote on Tue, Aug 02, 2022 at 02:14:58PM +0200: I'd like to be able to produce ASCII HT ('\t' - horizontal tab) in man pages output. I don't want to align things; I do want a tab character. Rationale: examples in

Re: TAB character in groff output

Hi Alejandro, Alejandro Colomar wrote on Tue, Aug 02, 2022 at 02:14:58PM +0200: > I'd like to be able to produce ASCII HT ('\t' - horizontal tab) in man > pages output. I don't want to align things; I do want a tab character. > Rationale: examples in fstab(5). I don't understand. On Debian,

TAB character in groff output

Hi Branden, I'd like to be able to produce ASCII HT ('\t' - horizontal tab) in man pages output. I don't want to align things; I do want a tab character. Rationale: examples in fstab(5). Is that possible? I didn't find anything in groff_char(7). Cheers, Alex -- Alejandro Colomar