Ingo Schwarze wrote:
|Steffen Nurpmeso wrote on Tue, Apr 25, 2017 at 08:19:21PM +0200:
|> the HTML output of mandoc used repeated per-paragraph style
|> directives and a CSS file, which caused enormous bloat, last
|> time i tried.
|
|Does that still apply to
|
| view-so
Deri James wrote:
|On Thu 27 Apr 2017 20:12:09 Ingo Schwarze wrote:
|> Does that still apply to
|>
|> view-source:http://man.openbsd.org/ksh
|
|compared with a PDF version:-
|
|http://chuzzlewit.co.uk/WebManPDF.pl/man:/1/ksh
Terrible, see the spacing errors surrounding the command list
Deri James wrote:
|On Thu 27 Apr 2017 23:48:29 Steffen Nurpmeso wrote:
|> Terrible, see the spacing errors surrounding the command list
|> before the "Substitution" heading! Not your fault of course, but
|> gr...
|>
|> --steffen
|
|Well, turns out it WA
i wrote:
|Ingo Schwarze wrote:
||Steffen Nurpmeso wrote on Tue, Apr 25, 2017 at 08:19:21PM +0200:
...
|As above. That is all for today, i spent three hopeless hours in
|the pic lex code, even shallow cloned 67 MB of gnulib for a few KB
|of datatable that doesn't get used the right way
i wrote:
|Ingo Schwarze wrote:
||Steffen Nurpmeso wrote on Tue, Apr 25, 2017 at 08:19:21PM +0200:
...
||P.S.
||Only bacause i'm replying anyway and it's just five lines:
|
|Sure.
|
||> .Op : Ns Fl c Ar cc-addr Ns \&:
||> .Fl S Ar var Ns Op Ns = Ns Ar value Ns
"G. Branden Robinson" wrote:
|Please find a patch attached.
Ordinary an ordinary, is that true.
I for one always found those one/two/one/two/.. macros very
suspicious, but now i see actual use cases.
--steffen
|Soylent Green is people!
Doug McIlroy wrote:
|Originally \(pl and \(mi came from a fixed font (S) while + and \-
|came from the current font. As I understand your comment, groff
|has reversed this troff convention. Additionally groff interprets - as
|a compromise HYPHEN-MINUS.
|
|man groff_char, however, tells the o
"G. Branden Robinson" wrote:
|At 2017-05-01T19:30:02+0200, Steffen Nurpmeso wrote:
|> "G. Branden Robinson" wrote:
|>|Please find a patch attached.
...
|> I for one always found those one/two/one/two/.. macros very
|> suspicious, but now i see actual use c
Ingo Schwarze wrote:
|Steffen Nurpmeso wrote on Tue, May 02, 2017 at 11:50:31AM +0200:
|> I now think it is better to revert all those per-macro adjustments
|> altogether and be pure; if people use \- to get "nicer" (smoother
|> and finer that is) output then pasting fr
Mike Bianchi wrote:
I absolutely and completely support this opinion of yours.
Maybe except that it would be nice if some future user could
easily find some documentation and now what to do to get "nice"r
looking output, maybe with some command line argument (variable),
or a configuration file,
Ralph Corderoy wrote:
|>> You could try replacing `.INCLUDE' with `.so'.
|>
|> First thing I tried with the OP. Same problem. .so is definitely not
|> playing nice with unicode.
|
|Ah, well, in that case, I think this explains it.
..
|$ soelim foo | preconv | groff -Tutf8 | grep .
|
Hey, Ingo,
Ingo Schwarze wrote:
|Steffen Nurpmeso wrote on Fri, Jul 21, 2017 at 10:30:36PM +0200:
|
|> In my humble opinion preconv has to go as such,
|> i just do not know yet. Just talking.
|
|So much talk...
SIIGHH!!!
|In mandoc, i completed that work in October 2014:
|
|
"E. Hoffmann" wrote:
|Am Fri, 21 Jul 2017 16:28:04 -0400
|schrieb Peter Schaffter :
|
|[...]
|>> $ soelim foo | preconv | groff -Tutf8 | grep .
|>> foo: ÄÖÜ SS ÒÓÔÕŎŌ Ç äöü ß òóôõŏō ç
|>> bar: ÄÖÜ SS ÒÓÔÕŎŌ Ç äöü ß òóôõŏō ç
|>> $
|>> $ groff -V -Tutf8 -sk foo
|>>
Hi.
mikkel meinike wrote:
|Can any of you walk me through what I should do to use the font 'bitstream
|vera sans' in my groff document? The font is somehow available in my system
|because I use it in my terminal (rxvt-unicode)
Peter Schaffter has written something that might help you out[1].
Peter Schaffter wrote:
|On Fri, Sep 08, 2017, Ralph Corderoy wrote:
|>> You'll notice that the top of the pdf file has a line of text spit out
|>> by grep(1) that obviously shouldn't be there.
|>
|> I couldn't come up with the groff 1.22.3-7 command line required to
|> build the PDF correct
i wrote:
|Peter Schaffter wrote:
||On Fri, Sep 08, 2017, Ralph Corderoy wrote:
||>> You'll notice that the top of the pdf file has a line of text spit out
||>> by grep(1) that obviously shouldn't be there.
...
||Problem solved.
...
||The solution is to pass the -a flag to grep.
This flag
cool, and maybe Freudian.
Attached.
(Ah, and i have tested it with my old groff installation, then
copied it onto a current v1.22.3.)
--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himse
Sorry, hit the wrong button!
-- >8 -- >8 -- Forwarded message -- 8< -- 8< --
Date: Thu, 09 Nov 2017 16:33:52 +0100
From: Steffen Nurpmeso
To: Bertrand Garrigues
Cc: Ingo Schwarze
Subject: Re: [Groff] Knuth-Plass Algorithm
Bertrand Garrigues wrote:
..
|Hmm... Bug #40716 &quo
Hi,
i am in the process of syncing my GPL2 roff tree once again,
hopefully to be able to start getting that thing going.
Let me first wonder why my valid remark regarding that Unicode
error (i have forgotten what it was, actually) is still not fixed
even if now with that GNU patch-in library thing
i wrote:
...
|I am here for something else, the commit mentioned changed
...
|I come up with (uncompiled and untested):
...
|
| void
| char_buffer::write_upto_newline(char_block **t, int *i, int is_html){
|enum {a_NONE, a_NL, a_LEADER} ev;
|char *b;
|int j, u;
|
|if
Werner LEMBERG wrote:
|> Blush. This should have been
|>
|> ev = (++j < u && b[j] == HTML_INLINE_LEADER_CHAR) ? a_LEADER : a_NL;
|>
|> instead. Now fixed. (Still uncompiled and untested, of course.)
|
|Please file a bug report in the issue tracker so that it won't be
|forgotten.
|commit 1294c8d2272e1c43b1b683e287deb1749865e642
|Author: G. Branden Robinson
|Date: Sat Nov 18 17:55:26 2017 -0500
|
|tmac: Move macro diagnostics away from `quotes'.
|
|Signed-off-by: G. Branden Robinson
|---
..
| tmac/doc-common-u | 86 ++--
Ingo Schwarze wrote:
|Steffen Nurpmeso wrote on Sun, Nov 19, 2017 at 02:57:36AM +0100:
|
|> selfishly decides over a style issue
|
|I think there was a discussion on this list, and what Branden does
|seems in line with the outcome to me.
Really? I must have missed that t
Ok, i finally say something.
g.branden.robin...@gmail.com (G. Branden Robinson) wrote:
|commit da6ac443f21ef09d90b40d2e8215955c916f396a
|Author: G. Branden Robinson
|Date: Sun Nov 19 22:19:52 2017 -0500
|
|contrib/hdtbl/examples/*.roff: Seed RNG.
|
|Support reproducible build
Hello Branden.
"G. Branden Robinson" wrote:
|At 2017-12-02T01:32:01+0100, Steffen Nurpmeso wrote:
...
|> g.branden.robin...@gmail.com (G. Branden Robinson) wrote:
|>|commit da6ac443f21ef09d90b40d2e8215955c916f396a
|>|Author: G. Branden Robinson
|>|Date: Sun Nov
Pierre-Jean wrote:
|For some reason, the html file was not joined, here it is...
No it is not. Maybe your mailer is the cause.. Or the used
version!
But interesting all that. That would have been my idea for going
HTML too, doing that in all of the macros which shall be usable,
but i never re
Hey.
Stephanie Björk wrote:
|For quite a bit, I've been trying to redefine the .$c macro for the -me
|macros. According to the reference manual, the macro package allows the
|user to redefine how chapters look when they get printed, by redefining
|that macro.
|
|Here's my redefinition. In
Stephanie Björk wrote:
|So, after having been on the mailing list for a bit, I've found that we are
|all sharing quite cool things here. Just a day ago, I wrote something
I do not. My macros are a bad hack.
|quite nice in Troff -- a macro package that provides for something that
|most macr
Jan Stary wrote:
|This is groff 1.22.3 as installed by the OpenBSD port.
|
|Below please find a short manpage written in mdoc(7),
|which I am trying to process into html with
|
| groff -Thtml -mdoc rtpdump.1 > rtpdump.html
|
|One point where it seems to fail is
|
| .Oo Ar address Oc Ns /
Ingo Schwarze wrote:
|i just posted a patch containing a complete rewrite of the mdoc(7) .Lk
|macro to: https://savannah.gnu.org/bugs/index.php?52849
I have not seen the patch yet, but .Lk is terrible and
unpredictable by the document author, as you say.
Making it not go in stand-out mode woul
Robert Thorsby wrote:
|Temperatures here in AU have been in the range 35-45 for the past week
|and are forecast to be the same for the next week. So with no
|inclination towards serious work I have turned my attention to
|rewriting my letterhead shell script, as one does.
And you have
Tadziu Hoffmann wrote:
|Just a short addendum:
|
|Since you know that you'll only be stripping off one of the
|known weekday names, there's also a simpler solution:
...
|However, there is still a caveat with these solutions: although
|\*[DATE*SHORT] may look like a (single-line) string exp
Tadziu Hoffmann wrote:
|> Why this? If i use \\*[DATE*SHORT] anything is fine, so it is
|> because the macro is evaluated while the string is defined.
|
|Yes.
|
|If you use the "string" like this:
|
| Some text before \*[DATE*SHORT], and some text after
|
|the expansion will yield
|
Doug McIlroy wrote:
|All these threads are tangled in my mind, so ...
|
|-a: I use this quite regularly for quick peeks at line and page
|breaks without the trouble of writing a file and looking at it
|in another window. It is certainly the option I type most--the
|rest are buried in shell s
Ralph Corderoy wrote:
|Ingo wrote:
|> The name of that standard section in man(7) and mdoc(7) is "EXIT
|> STATUS", not "Exit Status" nor "Exit status" nor "exit status".
|
|The shouting section heading makes it easier to find that heading rather
|than the same word occurring elsewhere, e.g.
ref="#description"],
a[href="#authors"] {
text-transform: uppercase;
}
Will typecast any link pointing to in majuscule "NAME".
It's all CSS. =)
On 21 April 2018 at 08:29, Steffen Nurpmeso wrote:
> Ralph Corderoy wrote:
> |Ingo wrote:
> |
Nate Bargmann wrote:
|* On 2018 19 Apr 18:47 -0500, James K. Lowden wrote:
|> On Fri, 20 Apr 2018 01:44:06 +1000
|> John Gardner wrote:
...
|I, for one, do not expect an HTML rendered version of *anything* to
|be a faithful representation of a printed page. The output of
|"groff -man -Th
Mike Bianchi wrote:
|True confession: Brian Kernighan is my hero. (stories upon request)
|
|In this talk, starting at about 41:45, he talks about the history of \
|creating
|the eqn, pic, grap "little languages".
|I offer it for those who might want a sense of how groff wound up where \
|
Keith Marshall wrote:
|On 05/05/18 10:48, G. Branden Robinson wrote:
|> (Incidentally, I share your preference for putting type qualifiers
|> [as opposed to storage classes] _after_ the type name itself. It
|> makes complex declarations easier to understand.)
|
|Personally, I consider that
Tadziu Hoffmann wrote:
|> Computer Science - Brian Kernighan on successful language design
|> https://www.youtube.com/watch?v=Sg4U4r_AgJU
|> "How to succeed in language design without really trying."
|
|Very interesting. It's somewhat amusing to see that already
|in 1961 (!) the proliferati
G. Branden Robinson wrote in <20180626153737.mf72sv3paetlc...@crack.dead\
beast.net>:
|I enjoyed this Easter egg; maybe you will too.
Why easter egg if i might ask?
|src/preproc/refer/refer.cpp:
...
|while (opt != 0 && *opt != '\0') {
| switch (*opt) {
...
| case '-':
|
Werner LEMBERG wrote in <20180802.162932.2121529583718521640...@gnu.org>:
|> There appears to be specific code in groff to explicitly *BREAK* the
|> return value of wcwidth(3). Actually, egregious mishandling of
|> wcwidth(3) is a quite common error in application programs, so groff
|> is cert
Hello Ingo,
Ingo Schwarze wrote in <20181201120713.ga89...@athene.usta.de>:
|John Gardner wrote on Sat, Dec 01, 2018 at 05:36:25PM +1100:
|> Ingo Schwarze wrote:
|>> Even moderately large systems can be beautifully documented in a
|>> single manual page - for example, a shell
|
|> It's amazi
Ingo Schwarze wrote in <20181209133200.gc7...@athene.usta.de>:
..
|Ralph Corderoy wrote on Sun, Dec 09, 2018 at 10:36:25AM +:
..
|> The time-honoured way to achieve this is using the built-in `set'.
|>
|> $ l='foo bar xyzzy'
|> $ set -- $l; for f; do echo f=$f; done | fmt
|>
Tadziu Hoffmann wrote in <20181218231523.gm7...@usm.uni-muenchen.de>:
|>> I'm against this whole locale thing. It needlessly
|>> complicates groff and will probably fail when reading
|>> foreign manual pages in a "C" locale.
|
|> That's _already_ a big fail, depending on the language.
|
|No
John Gardner wrote in :
|Hi Ricky,
|
|Try passing the paper-size option directly to Groff:
|
|groff -Tpdf *-P-l* …
I have an A4 alias with
-dpaper=a4 -P-pa4
--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach d
Hello.
KUBO Koichi wrote in <51fe9714-c2f9-5351-e4d5-aacc92fa0...@obuk.org>:
|I am using groff-1.22.4 on FreeBSD.
|After updating groff, I realized that there is no header in Japanese
|manpages using mdoc.tmac. So I added the following line to
|mdoc.local:
|
|.if ((\n[.x]\n[.y] >= 122) & (\
KUBO Koichi wrote in <51db73de-bc1a-e930-1be6-b5b04e432...@obuk.org>:
|On 4/21/19 2:22 AM, Steffen Nurpmeso wrote:
|> KUBO Koichi wrote in <51fe9714-c2f9-5351-e4d5-aacc92fa0...@obuk.org>:
|>|I am using groff-1.22.4 on FreeBSD.
|>|After updating groff, I realized that
James K. Lowden wrote in <20190703140438.a516b5af83532af9d7aa883b@schema\
mania.org>:
|On Wed, 3 Jul 2019 07:08:44 +1000
|John Gardner wrote:
|
|> Really? That's interesting. What did do? On the terminal
|> emulators I have on hand at the moment, none of them are responding
|> or behaving d
G. Branden Robinson wrote in <20190703154957.27lxnueucvu2cr5v@localhost.\
localdomain>:
|A recurring theme in my man page clean-up work has been my violent
|antipathy for shouting capitals in their texts. While I don't _like_
|being shouted at for reasons other than true emergency, the real pro
Steffen Nurpmeso wrote in <20190704202830.ds7rz%stef...@sdaoden.eu>:
|James K. Lowden wrote in <20190703140438.a516b5af83532af9d7aa883b@schema\
|mania.org>:
||On Wed, 3 Jul 2019 07:08:44 +1000
||John Gardner wrote:
||
||> Really? That's interesting. What did do? On the
Douglas Johnson wrote in <20190807133230.ga25...@panix.com>:
|On Aug 07, 2019, at 08:40, John Gardner wrote:
|
|>Installing TeX on macOS also requires a 3.9 GB download of the full
|>MacTeX distribution, whereas Groff's source tree doesn't even consume
|>that much space...
|
|Installing th
Andrea D'Amore wrote in :
|On Thu, 24 Oct 2019 at 17:11, Andrea D'Amore wrote:
|> link "groff and PostScript files--Beta" at [1] and built the default \
|> "utp_book.ps" target.
|[…]
|> [1]: https://www.oreilly.com/openbook/utp/
|
|While [1] is active the mentioned link points to a differen
Andrea D'Amore wrote in :
|Hello,
|I got the "UNIX Text Processing" book in groff format, link "groff and
|PostScript files--Beta" at [1] and built the default "utp_book.ps"
|target.
|The resulting PostScript file and its conversion to PDF via ps2pdf
|have no outline.
|
|I see the Makefile
Doug McIlroy wrote in <201912271608.xbrg84jr128...@tahoe.cs.dartmouth.edu>:
|The description of sprintf in the man page pic(1) does not
|reveal that only a few format codes are permitted.
|
|Eric Raymond's "Making Pictures With GNU PIC" says only
|%,%e,%f,%g are permitted. But what does a bar
Ingo Schwarze wrote in <20191227212705.gi66...@athene.usta.de>:
|Hi Doug,
|
|Steffen Nurpmeso wrote on Fri, Dec 27, 2019 at 06:45:23PM +0100:
|
|> Should be handled by [...]
|
|I believe the first patch that got sent to the list is incorrect.
|
|The parser in src/pre-pic/pic.
Jeff Conrad wrote in
:
|A major drawback to manual pages formatted using the man macros is the
|lack of bookmarks in a PDF file. A quick and dirty way to get bookmarks
|appears to be adding
|
|.am SH
|.pdfbookmark 1 "\&\\$*"
|..
|.am SS
|.pdfbookmark 2 "\&\\$*"
|..
Why quick and dirty?
Ingo Schwarze wrote in
<20200214184532.gj92...@athene.usta.de>:
|Hi Jeff,
|
|Jeff Conrad wrote on Thu, Feb 13, 2020 at 03:45:10PM -0800:
|
|> A major drawback to manual pages formatted using the man macros is the
|> lack of bookmarks in a PDF file. A quick and dirty way to get bookmarks
|>
B 9 wrote in
<20200619061008.okwcr%hacke...@member.fsf.org>:
|Since mdoc is a "semantic markup language", I presumed it would have
|some way to specify a hyperlink in running text that won't (to the
|best of mdoc's abilities) interfere with the flow of the text. The
|exact implementation would
--- Forwarded from B 9 ---
Date: Fri, 19 Jun 2020 13:55:30 -0700
From: B 9
To: Steffen Nurpmeso
Subject: Re: Groff macro to make .UR and .UE links clickable in PDF?
Message-ID: <20200619205530.n0y90%hacke...@member.fsf.org>
Steffen Nurpmeso wrote:
> Yes i am reading this list and
I am off-topic.
Ingo Schwarze wrote in
<20200625214812.gf90...@athene.usta.de>:
|given that two authoritative manual pages for the mdoc language
|exist that describe exactly the same language, but in a somewhat
...
| The manual page groff_mdoc(7): https://man.voidlinux.org/groff_mdoc
| cont
Michael Pirkola wrote in
<20200717123254.3aff0148@walrus>:
|On Sat, 11 Jul 2020 09:28:45 +0100
|Colin Watson wrote:
|
|> On Fri, Jul 10, 2020 at 11:26:46AM -0400, Steve Izma wrote:
|>> I think it's an abomination that a man page extends it's line
|>> length to fit the width of the terminal;
G. Branden Robinson wrote in
<20200815112655.xow4f3d4dcdaiaui@localhost.localdomain>:
|[CCing Russ Cox out of the blue; Russ, I work on GNU roff]
|
|Plan 9 went and did an interesting thing[1]. They implemented a macro
|just for man page cross-references.
...
|[1] https://github.com/9fans/
Sergiusz Pawlowicz wrote in
:
|Hi,
|is there anything like "manlint"?
|A tool which verifies the syntax of a man file and eventually points \
|to errors?
Use "mandoc -Tlint". It has flaws but is the best i know.
You can also use FreeBSD's igor, it is meant for mdoc macros but
nonetheless can
Hallo Ingo.
Ingo Schwarze wrote in
<20200915133505.gi1...@athene.usta.de>:
|Hi Steffen,
|
|Steffen Nurpmeso wrote on Tue, Sep 15, 2020 at 01:59:04PM +0200:
|
|> Just out of interest: why do you change an omnipresent idiom that
|> is in use for standard section headers in Unix
G. Branden Robinson wrote in
<20200915183356.3xt3ywitpzifixm2@localhost.localdomain>:
|At 2020-09-15T13:59:04+0200, Steffen Nurpmeso wrote:
|> Just out of interest: why do you change an omnipresent idiom that
|> is in use for standard section headers in Unix manual pages since
G. Branden Robinson wrote in
<20200927063701.vj6bg474km3ofpfh@localhost.localdomain>:
|At 2020-09-16T01:21:14+0200, Steffen Nurpmeso wrote:
|> C64 had no login. And DMR would not have used it.
|> I am all with Tadziu Hoffmann in this thread.
|
|Did Tadziu comment on this thre
Dave wrote in
<20201013-025509.sv93119.83...@savannah.gnu.org>:
|Update of bug #42233 (project groff):
|
| Summary: wcwidth(3) used on UCS4/UTF-32 codepoints \
| => [PATCH]
|wcwidth(3) used on UCS4/UTF-32 codepoints
My patch is based on old groff and even more
Dave wrote in
<20201013-025522.sv93119.18...@savannah.gnu.org>:
|Update of bug #43541 (project groff):
|
| Summary: FILE* encapsulation via class; compression \
| support
|for input files => [PATCH] FILE* encapsulation via class; compression \
|support
|for i
Dave wrote in
<20201013-025534.sv93119.11...@savannah.gnu.org>:
|Update of bug #45034 (project groff):
|
| Summary: mdoc(7): add support for the mdocmx(7) reference
|extension => [PATCH] mdoc(7): add support for the mdocmx(7) reference
|extension
Likewise, i am not going to r
Greg 'groggy' Lehey wrote in
<20201013232627.gb24...@eureka.lemis.com>:
|On Tuesday, 13 October 2020 at 22:49:03 +0200, J.-J. wrote:
|> Le mardi 13 octobre 2020 à 14:41 +0200, Johann Höchtl a écrit :
|>> * What would be a good starting point (tutorial) into troff and its
|>> core principles?
Morten Bo Johansen wrote in
:
|On 2020-10-14 Peter Schaffter wrote:
|
|> What difficulties do you have entering UTF8 directly into the
|> source? I've produced groff documents in most of the Western
|> European and Scandinavian languages
|
|I thought we Scandinavians were also considered p
|Steffen has withdrawn most/all of his other patches and even after reading
I do not know what this has to do with this bug.
|this report a few times I'm not clear on what exactly the problem is supposed
|to be.
|
|The "solution", "drop gnulib", is not likely, especially not during an RC
|c
Hello,
and sorry for the late reply.
G. Branden Robinson wrote in
<20201101035740.2azpyoxgyrd6ozdl@localhost.localdomain>:
|Hi, Steffen. Coming back to an old item of business.
|
|At 2020-09-29T19:12:00+1000, G. Branden Robinson wrote:
|> At 2020-09-28T22:57:37+0200, Steffen Nurpm
G. Branden Robinson wrote in
<20201101042024.gfw4dqth3qlfxxw2@localhost.localdomain>:
|At 2020-10-21T15:18:29+0200, Steffen Nurpmeso wrote:
|>> Steffen has withdrawn most/all of his other patches and even after
|>> reading
|>
|> I do not know what this has to do
Dorai Sitaram wrote in
<1129728531.3387046.1604937518...@mail.yahoo.com>:
|I have GROFF_ENCODING set to utf8, but this only works for the main \
|file processed by groff, not to any subfiles that are sourced via .so .
|Giving the -s option to groff to force a soelim doesn't work either.
|Add
Tadziu Hoffmann wrote in
<20201108120208.gd2...@usm.uni-muenchen.de>:
|
|> When you say points are '(about 1/72")', it probably
|> doesn't hurt to go the extra mile (!) in precision and
|> say '(1/72.27")'. It's shorter (no need for 'about')
|> and more correct.
|
|Historically, the size of
Timothy Groves wrote in
:
|Any attempt to use the pdfmark macro package causes exactly nothing to
|happen - no error messages, but also no metadata being added to my PDF.
|I've followed the instructions that come with pdfmark slavishly,
|including testing in the most minimal document human
Colin Watson wrote in
<20201214154336.ga32...@riva.ucam.org>:
|On Mon, Dec 14, 2020 at 02:12:28PM +1100, G. Branden Robinson wrote:
|> At 2020-12-12T21:19:38-0800, Jim Avera wrote:
|>> I suspect groff is always in UTC (but haven't confirmed).
|>
|> No, that is not true, at least not in gro
Hello.
Robert Goulding wrote in
:
|I've been away from groff for a long time; I think the last time I used it,
|there was no Unicode support at all. Now I'm interested in using it as a
|filter from markdown, through pandoc to groff to pdf.
|
|This is working well for me, except for a handful
Ulrich Lauther wrote in
<20210522214249.GA20730@starlite>:
|On Sat, May 22, 2021 at 08:18:41PM +0200, Oliver Corff wrote:
|>
|> "man cd", on the other hand, opens the bash built-in command *man page*,
|> which, at least on my system is a plethora of text to read (and digest).
|>
|on my syt
Hello.
|> Good idea. I've further changed the Subject: to reflect the flow of the
|> discussion.
...
|> I also wonder if the pager wars are basically over and less(1) won them.
|
|That's certainly what I thought...
..
Ever since less(1) started supporting OSC 8 "Hyperlinks in
Terminal Emu
Steffen Nurpmeso wrote in
<20210523212903.58vrh%stef...@sdaoden.eu>:
|Good evening and Hello.
And thanks to Mario Blättermann, replying to the mail unrevealed
a bug that is present in the MUA i maintain since at least 2003
(nail 10.05)!
A nice Monday i wish. (And happy 80th birthda
Good evening and Hello.
Steffen Nurpmeso wrote in
<20210523004836.gta8l%stef...@sdaoden.eu>:
...
||> Good idea. I've further changed the Subject: to reflect the flow of the
||> discussion.
| ...
||> I also wonder if the pager wars are basically over and less(1) won
Hey.
Steffen Nurpmeso wrote in
<20210523212903.58vrh%stef...@sdaoden.eu>:
|Steffen Nurpmeso wrote in
| <20210523004836.gta8l%stef...@sdaoden.eu>:
| ...
|||> Good idea. I've further changed the Subject: to reflect the flow \
|||> of the
|||> discussion.
|| ...
Ingo Schwarze wrote in
<20210602223746.ga92...@athene.usta.de>:
...
|Then again, i feel that's a problem of relatively little urgency.
That is because you use that mutilated less. The original can.
--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter he c
Wim Stockman wrote in
:
|Is there a function in groff to find the position of a char in a string.
|So I can split a string into more than one.
|I found the substring function that can cut based on length. If I could my
|marker in the string I could cut it there.
Loop over the string and use s
G. Branden Robinson wrote in
<20211125171302.ubixfedm3xtssc5m@localhost.localdomain>:
|I'm proposing a feature deletion.
|
|https://savannah.gnu.org/bugs/index.php?61561
|
|Have I overlooked something?
It is the counterpart to the environment variable *_NO_SGR, and
controls the same variable
Martin Sebor wrote in
:
|On 2/13/22 13:32, Alejandro Colomar (man-pages) wrote:
|> On 2/13/22 19:29, Alejandro Colomar (man-pages) wrote:
..
|>>> I expect/hope stpcpy to become the new norm for string copying, though
|>>> it will require overcoming much inertia and many dusty old books.
|>>>
Ingo Schwarze wrote in
:
|Douglas McIlroy wrote on Tue, Mar 22, 2022 at 08:58:19AM -0400:
|> Tangential comment:
|> I have always recoiled from git.
|
|I agree to some extent. Git does get a number of things right, but
|there are also many aspects of its user interface and design that make
Ingo Schwarze wrote in
:
|Alejandro Colomar wrote on Sun, Jun 19, 2022 at 04:11:49PM +0200:
|> On 6/19/22 16:00, Ralph Corderoy wrote:
...
|That makes compatibility in man(7) significantly more of a concern
|than in mdoc(7). All the same, i would certainly not consider
|adding anything as d
Ingo Schwarze wrote in
:
|Steffen Nurpmeso wrote on Mon, Jun 20, 2022 at 02:23:58PM +0200:
|
|> Just to mention that since 2014 my .Mx mdoc(7) extension is
|> distributed for the things i use, and i never have heard about an
|
|Just in case people aren't aware, even thou
Hello.
Gratulations for maintainership, Branden Robinson!
I am in the process of porting mdocmx to groff 1.23.
(That is to say: automake issues, after gnulib issues, git gc
--aggressive is killed by that ChangeLog which is nothing but
a duplicate of git log but prepends at the top instead of
app
Dave Kemper wrote in
:
|On 9/3/22, Steffen Nurpmeso wrote:
|> Letting aside that --with[out]-doc was blindly removed
|
|This was not done blindly: Ingo posted a lengthy rationale to this
|list (http://lists.gnu.org/r/groff/2022-04/msg9.html), and invited
|comment from anyone who wan
Alejandro Colomar wrote in
:
|Hi Branden,
|
|I see that you use .7.man or .1.man internally in the groff(1) source
|repository. But then those extensions are presumably removed during the
|installation, since man(1) doesn't like them. What are they for?
Surely automake sausage.
As like f
P.S.: i overtook this name change to my roff clone, shall that
ever spring into real existance. You have a credit, please
complain if you do not want to be named in THANKS.
diff --git a/tmac/mdoc/doc-common b/tmac/mdoc/doc-common
index 6c9093a876..29ee7f8c7b 100644
--- a/tmac/mdoc/doc-common
+++
Hello Branden.
G. Branden Robinson wrote in
<20220906205844.xbo54jzk2v7jscvf@illithid>:
|At 2022-09-06T16:22:42+0200, Steffen Nurpmeso wrote:
...
|Thanks, Steffen. I have applied this to my working copy.
It would be _tremendous_ if \X'tty: link' would get the
possibility t
Oh!
Steffen Nurpmeso wrote in
<20220906224118.jh2ju%stef...@sdaoden.eu>:
|G. Branden Robinson wrote in
| <20220906205844.xbo54jzk2v7jscvf@illithid>:
||At 2022-09-06T16:22:42+0200, Steffen Nurpmeso wrote:
...
|It would be _tremendous_ if \X'tty: link' would get the
Ac
Steffen Nurpmeso wrote in
<20220906231824.-4way%stef...@sdaoden.eu>:
...
|(Actually my less(1) pull request will not find the IDs my mdocmx
|produces via your grotty thing because of it. Hm. Well, we break
|out if we cannot find the = in the K=V, and ;: is an empty
|parameter. Si
P.S.:
Steffen Nurpmeso wrote in
<20220906232237.izz2i%stef...@sdaoden.eu>:
|Steffen Nurpmeso wrote in
| <20220906231824.-4way%stef...@sdaoden.eu>:
...
||(Actually my less(1) pull request will not find the IDs my mdocmx
...
I updated the pull request with an additional fix commi
201 - 300 of 330 matches
Mail list logo
