On Tue, Mar 03, 2015, SGT. Garcia wrote:
> Peter Schaffter: i noticed something odd. when i use .PDF_WWW_LINK and
> .DROPCAP in the same document, the .DROPCAPS letter turns up blue, the same
> colour as the link! i could send you the source file for further
> inspections if need be.
Please do. T
On Tue, Mar 03, 2015, SGT. Garcia wrote:
> just a note on the script which seems very old; back-ticks (`) are
> deprecated and also mkdir could use -p. first run failed for me
> but that's probably because groff in on my system (gentoo-linux)
> is installed under /usr as opposed to /usr/local.
Bac
On Mar 03 10:28 -0800, Dale Snell wrote:
> Peter Schaffter (creator of the mom macro package, which I _highly_
> recommend)
i used it today for the first time actually.
Peter Schaffter: i noticed something odd. when i use .PDF_WWW_LINK and
.DROPCAP in the same document, the .DROPCAPS letter turn
On Mar 03 15:31 -0500, Peter Schaffter wrote:
> If these directories do not exist, you may create them. The
> site-font directory is searched by groff so there's no need to set
> GROFF_FONT_PATH or use the -F flag. site-font is not overwritten by
> any new groff install, so your fonts are safe.
On Tue, Mar 03, 2015, SGT. Garcia wrote:
> thanks for clarifying. my question however is aiming at something
> different. i think i should have asked: is it possible to use any font
> other than the ones that come with groff. following some other pointer i
> came across heirloom project and some hi
On Tue, 3 Mar 2015 10:43:18 -0500, in message
20150303154318.GA3116@vpn.5665sherbrooke.house, SGT. Garcia wrote:
> thanks for clarifying. my question however is aiming at something
> different. i think i should have asked: is it possible to use any font
> other than the ones that come with groff.
Found a solution! In the sourced file, instead of
.char ∖ \[u005C]
use
.char \[u2216] \[u005C]
--d
On Monday, March 2, 2015 2:56 PM, "carsten.ku...@arcor.de"
wrote:
Dorai Sitaram wrote:
> I had the following
> .char ? \[u005C]
> in a file (the first ? is U+2216, or set-minus) an
On Mar 02 18:07 -0800, Dale Snell wrote:
> I don't know of a glossary, _per se_. The closest to one that
> I've seen is the Concept Index (Appendix K) in the Groff User's
> Manual. That said, you might want to read sections 5.5 and 5.6 of
> said manual. Those two sections cover requests and reg
Mike Bianchi wrote:
|On Tue, Mar 03, 2015 at 01:00:35AM -0500, Eric Andrew Lewis wrote:
|> In short, I'd like to make a program that does this:
|>
|> $ explain "rm -rf *"
|> rm -rf *
|> └── rm remove files or directories
|> ├── -r remove directories and their contents recursive
On Mar 03 03:06 +0100, Ingo Schwarze wrote:
> > for example, what's a request?
>
> A request is a command that is built into the the roff language,
> somewhat similar to a reserved word in a programming language,
> except that it can only occur after a leading dot or apostrophe
> at the beginning
thanks for clarifying. my question however is aiming at something
different. i think i should have asked: is it possible to use any font
other than the ones that come with groff. following some other pointer i
came across heirloom project and some hints here and there about TROFFONTS
environment va
Hi Eric,
Ralph Corderoy wrote on Tue, Mar 03, 2015 at 10:50:37AM +:
> Eric Andrew Lewis wrote:
>> $ explain "rm -rf *"
>> rm -rf *
>> ? rm remove files or directories
>> ? -r remove directories and their contents recursively
>> ? -f ignore nonexistent
On Tue, Mar 03, 2015 at 01:00:35AM -0500, Eric Andrew Lewis wrote:
> In short, I'd like to make a program that does this:
>
> $ explain "rm -rf *"
> rm -rf *
> └── rm remove files or directories
> ├── -r remove directories and their contents recursively
> ├── -f ignore nonexisten
Hi Eric,
> $ explain "rm -rf *"
> rm -rf *
> └── rm remove files or directories
> ├── -r remove directories and their contents recursively
> ├── -f ignore nonexistent files, never prompt
> └── *Remove (unlink) files matching this text pattern.
(The `text pattern' is actu
14 matches
Mail list logo
