On Mar 24, 2010, at 1:57 AM, Werner LEMBERG wrote:
This line *does* work:
. nop \\$*\h'0'\R'toc:horiz \\n[.k]'
In other words, forcing a zero horizontal motion flushes the single
word out and sets the .k register properly. Is this expected
behavior, and if so, is \h'0' the correct way to
Larry McVoy wrote:
.if !\n[EULA]=0 \{\
.if !\n[EULA]=1 \{\
.if !\n[EULA]=2 \{\
.if !\n[EULA]=3 \{\
.ab No EULA defined
.\}
.\}
.\}
If I remember correctly, EULA will return 0 if not previously
defined, so you'll never reach the abort. You can do this in one line:
.if !rEULA .ab No EULA de
Larry McVoy wrote:
On Wed, May 26, 2010 at 05:09:23PM +1000, Greg 'groggy' Lehey wrote:
There's currently a discussion going on in the FreeBSD project about
replacing groff (which is part of the base system, mainly to process
man pages) with a specialized man page processor, and relegate groff
Ralph Corderoy wrote:
Hi Charlie,
All they're doing is putting mdocml in base to handle manpages.
http://mdocml.bsd.lv/
DESCRIPTION
mdocml is a suite of tools compiling "-mdoc", the roff macro
package
of choice for BSD manual pages, and "-man", the predominant
histo
Meg McRoberts wrote:
Does anyone know the history of mmx? When I started, mmx was the
command we used to produce formatted ASCII text from source that
used the *roff macros. I got the idea that it was an older tool which
was being linked to nroff at about that time...
I seem to remember rea
I'm not sure when this started happening, or why, but I can reproduce it in
1.19.3 and in the CVS version.
Following is an example. Note that there's no .TS H/.TH pair.
mac-lkollar:/tmp lkollar$ cat test.n
.\" begin example
.\" format with groff -ms -t test.n >test.ps
.LP
This is a t
I'm seeing this in both the release and this morning's CVS versions. A test
file that illustrates the issue:
mac-lkollar:/tmp lkollar$ cat -n test.t
1 .nr NCS 1
2 .nr SIP 1
3 .LP
4 This is a test,
5 .if \n[NCS]&!\n[SIP] .nop NCS only.
6 .if !\n[NCS]&\n[SIP] .no
Werner LEMBERG wrote:
>> 5 .if \n[NCS]&!\n[SIP] .nop NCS only.
>>
>> test.t:5: warning: numeric expression expected (got `!')
>
> I suspect that for backwards compatibility with AT&T troff only a
> `leading' exclamation mark – this is, at the very beginning of an
> expression within `.if',
> Can you suggest a fix to groff.texinfo to document this better?
I've attached a patch that updates both groff.texinfo and groff.man (groff.7).
-- Larry
bang.patch
Description: Binary data
Mike Bianchi wrote:
> On Fri, Sep 10, 2010 at 09:35:54PM +0100, Ted Harding wrote:
>> :
>> One has the feeling that one could reach out and grasp it, but it
>> always seems to be just a few inches further away than the length
>> of one's arm ...
>
> “Ah, but a man's reach should exceed his
I've been successfully using pdfmark to generate PDFs with bookmarks for some
time now, no problem. Now I'm trying to make my cross-references into actual
PDF links, and that's where I'm running into trouble. Part of the problem, I
suppose, is the part of the pdfmark documentation I need has not
Got it! It took a while for my brain to sharpen up a little bit, but it's
making sense. Mostly.
> Multiple pre-processing passes are required... to locate any PDF reference
> marks
That got me wondering. I use a two-pass scheme to get cross-refs right; the
very first time it gets run it might
Cedric Sodhi wrote:
> I use the ms.tmac macros as a "lightweight" and focused alternative
> to the full fledged me.tmac. On a sidenode, I'm rather new to groff, so
> if someone could correct me on that assumption that me is nothing but
> a completer version of ms, please do so.
The ms, me, an
In my continued attempts to get PDF links working properly, I'm now running
into one of the most frustrating aspects of any troubleshooting job: the
intermittent error. Cross-reference links that work in one place don't work in
the other, and I haven't yet found a pattern. Looking at the referen
As a follow-up, I think I may have finally identified the problem. The syntax
for my XREF macro is:
.XREF type dest [trailing]
And (depending on the type) the resulting command looks something like:
.pdfhref L -D \\$2 -A \\$3 {stored xref text}
All the dropped links have no third argument. Set
Sergio Villone wrote:
> Hello everybody...
> I wonder if anywhere is available the groff source for a user
> manual... I'm new to groff and the like and an exampl
> would be really welcome, in particular for the cover page
> and the toc ;-)
> thank you in advance...
The groff source distribution
brian m. carlson wrote:
> On Fri, Dec 17, 2010 at 04:49:43PM -0500, Timothy Groves wrote:
>> Has anyone come up with filters, macros, etc., to produce an ePub
>> file from groff source?
>
> Since ePub is basically XHTML in a zip file, you could create one with
> -Txhtml. The problem with using
Petr Man wrote:
> I am unable to figure out how to make groff/pdfroff with pdfmark to
> produce clickable TOC out of a mom document. From the mailing list
> archives it seemed to me, that pdfroff should be able to do that, but
> I end up with the same document twice in the file instead as
> http:
Hi Ralph,
One of my co-workers was a co-author of "Preparing Documents with Unix" and I
don't see it in the "Books about troff" list. The following Amazon link has a
shot of the book cover to borrow, too.
http://www.amazon.com/Preparing-Documents-Unix-Constance-Brown/dp/013699976X
Good to know
Minimal example:
.PS
box xslanted 0.1 yslanted 0.5;
.PE
% groff -ms -p junk.pic > junk.ps
pic:junk.pic:2: there is no variable `xslanted'
pic:junk.pic:2: giving up on this picture
%
Am I doing this wrong?
-- Larry
Hi all,
I'm in sudden need of a hyphenation file for Portuguese (Brazilian if it
matters). One of my work projects is going to the translators, and that's the
only missing piece I'm aware of at the moment.
Thanks!
-- Larry
On Jan 8, 2012, at 4:35 PM, Doug McIlroy wrote:
> I have a paper composed in notrivial groff (uses pic,
> eqn, tbl, and .PSPIC), which I'd like to submit to a
> journal that takes any kind of digital text--as
> long as it's Word or RTF. I haven't been able to find
> any tool that offers much hel
On Jan 22, 2012, at 12:36 AM, Siteshwar Vashisht wrote:
> Is there any option in groff to parse only a specifiec section of man page
> ? For e.g. when I say
>
> groff -X -P -resolution -P100 -man passwd
>
> It parses and shows me the whole page. What if I want to parse only OPTIONS
> section ?
Timothy Groves wrote:
> Is there a way to move the footer up within the footer margin when using ms?
> By default, groff+ms places the footer halfway down the footer margin, which
> is not what I want, but any attempt to move it up by inserting a .sp -x in
> .BT either results in an error [ f
Cedric Sodhi wrote:
> I recently decided to use mm instead of ms because it appeared that mm
> offered far more but I'm having a hard time getting it to do what I
> want.
>
> In particular, I'm missing the information about which macro has to be
> invoked when, where and in which context togethe
Anton Shepelev wrote:
> I think, groff and TeX macro packages do provide a
> means for structural mark-up, and, considering the
> example above, it is of course possible to redefine
> the macro .B to achieve the desired result? For
> clarity, it could also be renamed as "EMPH".
>
> I
Peter Schaffter wrote:
> It does no good to emphasize the universal portability of groff
> documents, for reasons I know too well: if the publisher I send
> a work of fiction to is a Wordie--they all are--I have no choice
> but to provide them with MSWord documents.
Not that traditional publishe
Clarke Echols wrote:
> I have a potential client who needs copy in DOC/Word format, and I'm
> on Linux. ...
>
> Last time I tried anything of the sort, I produced a doc file from
> OpenOffice Writer, but when I read it using Word on a PC, the tables
> were mangled beyond anything remotely useful
On Aug 17, 2012, at 12:42 PM, "Cedric Sodhi" wrote:
> I converted a PNG image to EPS with sam2p and tried to include it with the
> PSPIC macro. However, I get a meaningless error saying
>
> grops:test2.eps (result.groff):15: not an integer
Does the output look OK? I get spurious warnings when
On Sep 4, 2012, at 2:10 PM, Michael Parson wrote:
How long ago was that? OpenOffice has improved over the last couple years.
>>
>> I have just tried the groff-->PS-->PDF-->OpenOffice route.
>>
>> When given the PDF file to open, OO Writer took a while, and then
>> came up with a screen tha
Sorry about the long-delayed response, guys. I've been up to my eyeballs with
both fiction and reality this month. I must be crazy to have agreed to launch
two novellas two weeks apart. :-P
I'll apply the Chapter 9 patch, as the patched groff is unlikely to be
universal any time soon. In the m
Werner LEMBERG wrote:
.FONT I text1 R text2 I text3 R text4
is equivalent to .IR text1 text2 text3 text4
>>>
>>> I don't particularly like the idea; changing the font for
>>> individual strings is very low level manipulation. Groff does have
>>> established syntax for that
>
> I d
On Jan 6, 2014, at 2:20 AM, Werner LEMBERG wrote:
>> Up to now I was able to friendly ignore it as long as groff wasn't
>> affected. [...]
>
> I'm very sorry that I've inadvertently written to the list; it should
> have been a private reply. Bernd, I apologize for `talking behind
> your back',
> Steve Izma wrote:
>
> On Tue, Jan 20, 2015 at 07:57:25PM -0500, Doug McIlroy wrote:
>> I recoil from text infected with capital pox, and don't see
>> small caps as much improvement. They do make sense in all-caps
>> text, but sporadic S\s-2MALL\s0 C\s-2APS\s0 or anything like
>> it is not a cu
> Steffen Nurpmeso wrote:
>
> Heinz-Jürgen Oertel wrote:
> |Am Montag, 9. Februar 2015, 16:19:51 schrieb Peter Schaffter:
> |> Groffers --
> |>
> |> I don't see any mention of this in the list archives, and it's too
> |> wonderful to miss. If you want a glimpse of days gone by, have a
> |> lo
> On Mar 2, 2015, at 6:01 PM, SGT. Garcia wrote:
>
> is it possible to use fontconfig font families with groff? google is
> failing to find anything.
I think not. Groff (and other *roff variants) have their own directories and
special file formats for font metrics—the data that determines how
Ingo Schwarze wrote:
>
> G. Branden Robinson wrote on Wed, Aug 11, 2021 at 01:16:45AM +1000:
>
>> but I reckon I should actually step up and try to improve one of the
>> generator tools, like pod2man
>
> That would be a noble deed because pod2man(1) is a very useful tool
> and produces almost
> Alejandro Colomar (man-pages) wrote:
>
> On 3/20/22 10:36, G. Branden Robinson wrote:
>> Yes, something about this should become part of groff(7). In
>> groff_man_style(7), I have restricted the discussion to advising people
>> to use the \(dq special character (also spellable as \[dq]).
>
Ingo Schwarze wrote:
>
> Alejandro Colomar (man-pages) wrote on Sat, Mar 19, 2022 at 05:07:09PM +0100:
>
>> While fixing style issues in the man-pages project,
>> I'm finding a few recurrent issues that I think you could warn about:
>>
>> Unnecessary quotations:
>>
>> [
>> .I "foo bar"
>> .I
Ingo Schwarze wrote:
>>> 2. The concept of encoding names and versions of all operating
>>> systems is not sustainable in the long run.
>
>> This was probably a product of its times; there was BSD, only one BSD,
>> and then there was System V, and the importance of that conflict caused
>>
JM Marcastel wrote:
> I would like to investigate the possibility of using Markdown as an alternate
> format for UNIX man-pages.
> (Cf. https://github.com/marcastel/marcastel/discussions/7)
>
> Rather than re-inventing the wheel I would ideally like this to become part
> of an existing tool
James K. Lowden wrote:
>
> gromunity:
>
> In working with my GUI man page viewer (not ready for its first
> audition yet) I found myself asking how indexes could be implemented in
> current and future man systems, and what groff would have to produce
> for a viewer to provide an index affordanc
> On Aug 21, 2019, at 8:45 AM, Mikkel Meinike Nielsen wrote:
>
> No haven't done any prosper "homework" before asking. Just wanted to here
> your opinion. Actually what I won't is a text box or a very specificly
> placed column of text.
Much can be found by doing “man groff_ms” (assuming your
301 - 343 of 343 matches
Mail list logo
