Chet Ramey wrote in
<2fd2ed52-3272-3433-6179-164bc5122...@case.edu>:
...
|> At 2023-07-26T10:47:05+0200, Thomas ten Cate wrote:
|>> In the bash manual page (`man bash`), the ASCII tilde character '~'
|>> (0x7e) is replaced by the Unicode character '˜' (U+02DC SMALL TILDE):
|>>
|>> $ ma
Steffen Nurpmeso wrote in
<20230729002703.lasps%stef...@sdaoden.eu>:
|Chet Ramey wrote in
| <2fd2ed52-3272-3433-6179-164bc5122...@case.edu>:
| ...
||> At 2023-07-26T10:47:05+0200, Thomas ten Cate wrote:
||>> In the bash manual page (`man bash`), the ASCII tilde characte
G. Branden Robinson wrote in
<20221227232513.6zeaunnqaywtrxvw@illithid>:
...
|I haven't looked at it
Buddy, it is where you got your _idea_ from.
So do not mind i unsubscribe to stop you spamming my inbox with
your shit, Mr. infinitely scaling intellectual.
When s-roff will ever spring into ex
Ralph Corderoy wrote in
<2022122714.845141f...@orac.inputplus.co.uk>:
|Hi Steffen,
...
|Deri means you.
Dunno, Ralph.
Thanks,
--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks hims
G. Branden Robinson wrote in
<20221227095728.c7oo2iolmg6hl4nw@illithid>:
|At 2022-12-24T23:39:07+, Deri wrote:
|>> "o" for the former.
|>> 'That said, https://ftp.sdaoden.eu/code-mailx-1.pdf (beware:
|>> 1MB!), realized with newest minor of mdocmx on groff
|>> 1.23.0.rc1.2915-c6d7,
|
|T
Ralph Corderoy wrote in
<20221224090607.7dbb222...@orac.inputplus.co.uk>:
|Hi Deri,
|
|> You may need to open the outline pane on the left, which acts like a
|> table of contents.
|
|Is it mandatory that a PDF viewer must supply this mechanism to be
|worthy of the name? Off-hand, I don't r
G. Branden Robinson wrote in
<20221214002919.gy56muresenofizt@illithid>:
|Some people might find the following messages, first from Nils-Peter
|Nelson and then Liam R. E. Quin, of interest. They're posts from 1996
|to the comp.text USENET group. (Je me souviens, DejaNews!)
Thanks for posting
Alejandro Colomar wrote in
<20221205223936.8290-1-...@kernel.org>:
...
|--- a/src/roff/troff/input.cpp
|+++ b/src/roff/troff/input.cpp
|@@ -7892,7 +7892,7 @@ void do_macro_source(bool quietly)
|MACRO_POSTFIX, sizeof(MACRO_POSTFIX) - 1) == 0) {
|char *s = new char[fnlen + sizeof(MACRO
G. Branden Robinson wrote in
<20221126035253.pli53qzgfx6tbax5@illithid>:
|At 2022-11-25T18:18:46-0800, Paul Eggert wrote:
...
|> If we did that, Groff would set a source string like "\*-\*-help" as
|> "−−help", with two instances of U+2212 MINUS SIGN instead of U+002D
|> HYPHEN-MINUS. Therefo
DJ Chase wrote in
:
|On Sat Sep 17, 2022 at 3:30 PM EDT, Steffen Nurpmeso wrote:
|> P.S.: with the help from people of IRC i have now tested LuxiMono,
|> IBMPlexMono, and NotoMono, and only LuxiMono gets it somehow right
|> (but looks terrible as a monospace font imho).
...
|JetBr
Steffen Nurpmeso wrote in
<20220917165637.pmpud%stef...@sdaoden.eu>:
|Steffen Nurpmeso wrote in
| <20220917162423.trkch%stef...@sdaoden.eu>:
||Steffen Nurpmeso wrote in
|| <20220917152906.uhdto%stef...@sdaoden.eu>:
|||Ralph Corderoy wrote in
||| <2
Steffen Nurpmeso wrote in
<20220917162423.trkch%stef...@sdaoden.eu>:
|Steffen Nurpmeso wrote in
| <20220917152906.uhdto%stef...@sdaoden.eu>:
||Ralph Corderoy wrote in
|| <20220917105400.a3f1121...@orac.inputplus.co.uk>:
|||> ` U+0060, GRAVE ACCENT, "backtick&qu
Steffen Nurpmeso wrote in
<20220917152906.uhdto%stef...@sdaoden.eu>:
|Ralph Corderoy wrote in
| <20220917105400.a3f1121...@orac.inputplus.co.uk>:
||> ` U+0060, GRAVE ACCENT, "backtick"
||>
||> is displayed as
||>
||> ‘ U+2018, LEFT SINGLE QUOTATI
Steffen Nurpmeso wrote in
<20220917155426.f4zgu%stef...@sdaoden.eu>:
...
|I am out.
Well a bit harsh. But other than that, not.
I see people using copy+paste with code examples and, even worse,
configuration examples, and getting lots of trouble because of
character mappings which res
G. Branden Robinson wrote in
<20220917005135.3sy2ri22dhvlnvq5@illithid>:
|At 2022-09-17T01:00:26+0200, Steffen Nurpmeso wrote:
|> G. Branden Robinson wrote in
|> <20220916223236.lmkf3brdwotdn2fd@illithid>:
|>|At 2022-09-16T23:56:58+0200, Steffen Nurpmeso wrote:
|>|
Hello Ralph.
Ralph Corderoy wrote in
<20220917105400.a3f1121...@orac.inputplus.co.uk>:
|> ` U+0060, GRAVE ACCENT, "backtick"
|>
|> is displayed as
|>
|> ‘ U+2018, LEFT SINGLE QUOTATION MARK
|>
|> which in Liberation Mono (at least!) this reverses the direction of
|> the tick.
|
|Thi
G. Branden Robinson wrote in
<20220916223236.lmkf3brdwotdn2fd@illithid>:
|At 2022-09-16T23:56:58+0200, Steffen Nurpmeso wrote:
..
|> i=`echo '~/home^run'`
|>
|> becomes
|>
|> i=‘‘echo ’˜/homeˆrun’‘’
|>
|> How is anyone supposed to document a
Steffen Nurpmeso wrote in
<20220916213112.5dabw%stef...@sdaoden.eu>:
|Hello.
|
|Letting aside the hyphen-minus -> hyphen thing that i fixed for me
|locally, there is also the problem that
|
| ` U+0060, GRAVE ACCENT, "backtick"
|
|is displayed as
|
| ‘ U+2018, LE
Hello.
Letting aside the hyphen-minus -> hyphen thing that i fixed for me
locally, there is also the problem that
` U+0060, GRAVE ACCENT, "backtick"
is displayed as
‘ U+2018, LEFT SINGLE QUOTATION MARK
which in Liberation Mono (at least!) this reverses the direction
of the tick.
I was loo
Ralph Corderoy wrote in
<20220914071616.2e89021...@orac.inputplus.co.uk>:
|Hi Steffen,
|
|>>> En dash would look nice, i could imagine.
|>>
|>> Those ASCII ‘-’ above should be rendered as a hyphen in nicely
|>> typeset output. An en-dash is far too big. Oh, there's another
|>> one!
|...
Dave Kemper wrote in
:
How about [12066c659ea454a663483a12181a0c33cf416b22].
This looks promising.
Thank you.
--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Ger
Ralph Corderoy wrote in
<20220913084152.0211621...@orac.inputplus.co.uk>:
|Hi Steffen,
|
|> Hyphen is good at the end of line when a word is hyphenated, otherwise
|> it is misplaced.
|
|Not in English. A hyphen may be used to join compound adjectives, as a
|two-minute Google would show. :
G. Branden Robinson wrote in
<20220913053400.7lmdp2qpxb6zweei@illithid>:
|At 2022-09-12T23:41:34+0200, Steffen Nurpmeso wrote:
|> This is not a hyphenated word.
|[rearranging this a bit]
|> En dash would look nice, i could imagine.
|
|Then use en dashes in your input.
|
| on\
Dave Kemper wrote in
:
|On 9/12/22, Steffen Nurpmeso wrote:
...
|Groff has converted an input U+002D to a proper hyphen in typeset
|output for decades. It has done so in UTF-8 output since at least
|groff 1.19.2.
...
This is not true. I never have seen anything but hyphen-minus on
my
Hello Branden.
G. Branden Robinson wrote in
<20220912144641.q2r65kkfpiej4u2u@illithid>:
|At 2022-09-12T15:43:00+0200, Steffen Nurpmeso wrote:
|> I have problems with the UTF-8 device, it shows
|>
|> on‐main‐loop‐tick
|> instead of
|> on-main-loop-tock
|>
Hello!
I have problems with the UTF-8 device, it shows
on‐main‐loop‐tick
instead of
on-main-loop-tock
ie U+2010 instead of hyphen-minus U+002D.
The above does not feel right, and searching is impossible!
I would expect U+2010 HYPHEN in hyphenation, but not as a regular
combiner aka delimiter
Eh sorry folks.
Steffen Nurpmeso wrote in
<20220909164816.rzev-%stef...@sdaoden.eu>:
|Steffen Nurpmeso wrote in
| <20220909163015.7zdu0%stef...@sdaoden.eu>:
| ...
||so it seems to me .nr registers can no longer contain a "#" in
||their name! That would totally boom my
Steffen Nurpmeso wrote in
<20220909163015.7zdu0%stef...@sdaoden.eu>:
...
|so it seems to me .nr registers can no longer contain a "#" in
|their name! That would totally boom my macro package(s)! Is not
However, i also have
. nr mx#t-d#n1 0
. while (\n[mx#t-d#n
Hello.
During testing (still not done because i massively improved the
less pull request, not yet pushed, but now even ^O^N and ^O^P work
totally graceful regarding repaints and _every_ move around)
i stumbled over certain number registers i use do not work no more
like they should, so if i instru
Hello Branden,
..again, and sorry, for the noise..
Steffen Nurpmeso wrote in
<20220907210913.drf4v%stef...@sdaoden.eu>:
|P.S.:
...
|||(Actually my less(1) pull request will not find the IDs my mdocmx
...
|I updated the pull request with an additional fix commit that
...
|I would
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
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
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
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
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
+++
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
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
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
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
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
:
|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
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.
|>>>
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
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
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
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.
|| ...
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
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
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
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.
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
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
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
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
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
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
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
|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
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
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?
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
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-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
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
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
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
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
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/
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;
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
--- 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
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
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
|>
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 <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.
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
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
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
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
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
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
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
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
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) & (\
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
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
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
|>
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
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
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 '-':
|
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
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
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 \
|
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
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:
> |
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.
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
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
|
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
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
1 - 100 of 330 matches
Mail list logo
