Stephen Berman wrote:
|Does groff permit characters besides hyphen-minus (ASCII 45) and soft
|hyphen (octal 255) for displaying hyphenation in man pages? I'm asking
I have been convinced that soft hyphen is a control character and
not something visual, it should be used as a «break-indicator»
Happy new (Christian++) year everybody.
Tadziu Hoffmann wrote:
|> [...] and also supports five different builtin styles for
|> verbatim output instead of only a silly numbered one.
|
|Okay, I'm curious. What different styles apart from numbering
|could there possibly be? (I can't think of
Volker Wolfram wrote:
|Hi all groffers,
|
|in fact I'm a newbie on groff tools and macros. But these \
|tools are the BEST I've used EVER. I enjoy groff so much, I've developed my
I fully agree -- after almost going stony because of loosing
system content _and_ the backups (forgotten PGP pass
Doug McIlroy wrote:
|I must be missing something in the discussion about random
|numbers. Why does groff need them? In the offered example
|tmp="$d/eqn2graph$groff_rand"
|the "random number" serves only to make a (supposedly) unique
|name. But of course, if the number is truly random, it
Werner LEMBERG wrote:
|Regarding the abandoning of ChangeLog files: There is an interesting
|thread right now about this topic in the emacs-devel mailing list.
|Attached you can find one of the messages, and I agree with Eli.
|However, other people might think differently...
I never used Chan
(blush) really nice bicycles..
Original Message
Date: Thu, 2 Jan 2014 09:49:27 -0500
From: Mike Bianchi
To: Steffen Nurpmeso
Subject: Re: Re: [Groff] [PATCH] Use bash for several contrib scripts
On Thu, Jan 02, 2014 at 03:03:48PM +0100, Steffen Nurpmeso wrote:
> :
> Imh
Ralph Corderoy wrote:
|Hi Steffen,
|
|> I'd really rather do something like the below instead.
|...
|> -tmp=$d/eqn2graph$$-$RANDOM
|> +tmp=$d/eqn2graph$$-${RANDOM:-${$}}
|
|That's assuming the environment doesn't contain a RANDOM from somewhere.
ph!
|:-)
|
|Cheers, Ralph.
Colin Watson wrote:
|I suppose it isn't a fatal incompatibility, since $RANDOM just expands
|to the empty string on other shells and mkdir will probably fail; maybe
|we could just leave it alone since the above is really no better than
|that.[.]
yes of course.
It was just me seeing /bin/bash,
Happy new year.
Colin Watson wrote:
|+2014-01-02 Colin Watson
|+
|+ * contrib/eqn2graph/eqn2graph.sh: Use bash rather than sh; $RANDOM
|+ is a bashism.
|+ * contrib/grap2graph/grap2graph.sh: Likewise.
|+ * contrib/pic2graph/pic2graph.sh: Likewise.
I'd really rather do so
Werner LEMBERG wrote:
|> (I've mailed sinuhe AT gnu.org to update the webpage.)
|
|Anyways, I've updated the web page. It won't win a beauty contest,
|but the info should be accurate now.
It seems you sometimes have to deal with asholes in such an
unlimited forum.
...and a beer in a tree...
Heinz-Jürgen Oertel wrote:
|Am Sonntag, 22. Dezember 2013, 18:34:01 schrieb Steffen Daode Nurpmeso:
|> Heinz-Jürgen Oertel wrote:
|>|What would be the repository address for a git clone?
|>
|> git://git.savannah.gnu.org/groff.git
|
|all steps OK
Good!
(I've mailed sin
Heinz-Jürgen Oertel wrote:
|What would be the repository address for a git clone?
git://git.savannah.gnu.org/groff.git
The webpage still mentions CVS only.
Ciao,
--steffen
Walter Alejandro Iglesias wrote:
|Searching for how implement crop marks with groff I've found this:
[.]
|I would appreciate some clue or a point to some documentation.
Well i have no crop marks but used "fold marks" for letters and
when punchers had to be adjusted, but you can paint whatever
Hello,
i couldn't update my repo:
AuthReply: cvs: unrecognized option
'--allow-root-regexp=^/srv/cvs/sources/.*$'
What can be done about that?
--steffen
Keith Marshall wrote:
|On 13/04/13 14:52, Werner LEMBERG wrote:
|>> Any comments?
|
|Some projects do commit configure, others don't. IMO, it is better if
|it is *not* committed, but IIRC it has been there, in groff's CVS, for
|as long as I've been associated with the project. I would be
I'm talking about the attached version of the hyphenation rules.
--steffen
hyphen.de.gz
Description: GNU Zip compressed data
Hello,
i'm looking at a rather current (Add a shell command to the file
MANIFEST.., 2013-01-24) version of the GNU (t)roff repo and i see
that hyphen.de was imported into groff:
Author: wl
Date: 2006-12-19 08:02:52 +
Add support for German. For activation, simply use -mde or -m
Werner LEMBERG wrote:
|Macros called with \* is indeed nothing new. However, having
|arguments like
|
| \*[foo arg1 arg2 ...]
|
|is what I've added some years ago.
It'll allow me to rewrite terrible code.
|Werner
--steffen
Tadziu Hoffmann wrote:
|[snip]
|> do i have to change my version check [...] to 1.20 for this to work?
|
|This has worked for ages already in Unix troff (because macros and
|strings share the same namespace), and my guess is in groff as well.
|It might just not have been documented.
It defi
Werner LEMBERG wrote:
|> i.e., let me write \*[ITEM] even if that was a macro not a string.
|> (Or has something adorable happened since then.)
|
|I don't understand your (probably sarcastic?) comment. That \*[ITEM]
|can call either a macro or a string is a feature which can be useful
|some
"Bernd Warken" wrote:
|I will not follow that line. A roff that accepts only 2-letter-macros
|today has no chance to survive.
|
|The original RUNOFF had very long command names, for example
|.ADJUST
|
|Each command had an abbreviation of 2 letters, with the lang name as the
|standard. But
21 matches
Mail list logo
