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 the original file, I added no comments, b
That seems very reasonable an explanation. Thank you. :)
I didn't know that the problem had something to do with EQN's inline
equation. It wasn't so obvious, but it makes sense nonetheless.
I also find it funny if I ever need to talk about money in dollars: a
dollar sign ($) is obviously needed
Hi,
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
quite nice in Troff -- a macro package that provides for something that
most macro packages I have so far known lack. I figured also that this is
ess, the concepts should be the same as it is
now, ergo it is kind of showable.
Stephanie
On Tue, Dec 5, 2017 at 3:45 PM, Pierre-Jean wrote:
> Stephanie Björk wrote:
>
> > The project is here: https://github.com/katt64/troff-lists (bul.tmac is
> the
> > beating heart of it al
e a good way of doing them. The package (not quite the
> latest version) is in
>
> http://www.oxytropis.plus.com/groff/markup-1.0.7a.tar.gz
>
> Denis
>
> On Tue, 5 Dec 2017 19:29:34 +0700
> Stephanie Björk wrote:
>
> > Thank you, Pierre-Jean.
> >
> > It&#
g languages able
to do this, but I do think there are a few like this that I've not heard of
yet.
On Wed, Dec 6, 2017 at 6:04 AM, Peter Schaffter wrote:
> On Tue, Dec 05, 2017, Stephanie Björk wrote:
> > as my macros really use weird, fancy stuff.
>
> I don't see anything
learning TROFF
from classical TROFF, so that kind of gives me a habit.
On Thu, Dec 7, 2017 at 2:07 AM, Stephanie Björk
wrote:
> > I don't see anything weird or fancy that hasn't been a part of groff
> > for at least fifteen years. To what are you referring? I'm
To Ralph,
You quoted the following in your email:
> Stephanie wrote:
> > However, Troff's ability to take values of a numerical register and
> > use it as a name to another register (.nr my_\na_\nb) intrigues me
> > very much.
>
> I do not know if that "feature" was an intentional design or an
>
According to Wikipedia:
In addition, the clause presented a legal problem for those wishing to
publish BSD-licensed software which relies upon separate programs using the
GNU GPL: the advertising clause is incompatible with the GPL, which does
not allow the addition of restrictions beyond those it
I think part of the reason why the release for Groff has been so slow and
sparse could be because of two things: the patches aren't ``significant''
enough for some degree of ``significant,'' there are not enough maintainers
and thus not enough motivation to publicly release or effect anything, this
Sorry if the context is out of the ordinary, but I would like to have some
specifications of the \(bs symbol, which does not seem to exist on Groff.
I am quite certain that it can be recreated using Troff's drawing
primitives, but I can't seem to get it quite right. Perhaps someone has
the exact o
Huh? Why does it look so different? The \(bs symbol looks more like a
black ball with a white shadow even on the original Troff manual, but the
link to Wikipedia looks like a bell in a circle.
On Wed, Jan 10, 2018 at 8:44 PM, Mike Bianchi wrote:
> > .char \(bs \X'ps: import ATandTlogo.ps 9 4 1
12 matches
Mail list logo
