Re: [Groff] End of file processing

2014-01-02 Thread Werner LEMBERG
> When a diversion that doesn't fit on the last page of a document and > has to be deferred to the next (ie a float) is followed by a few > lines of type that don't reach the bottom margin, processing stops > at the end of the text and the diversion is never output. [...] Minimum example, please

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Peter Schaffter
On Thu, Jan 02, 2014, Mike Bianchi wrote: > How is someone attempting to understand a #!/bin/sh script to know what the > writer intended if there is no documented way to interpret the syntax? #!/bin/sh # This script is written for the bash shell. See bash(1). Or is that just too obvious? --

[Groff] End of file processing

2014-01-02 Thread Peter Schaffter
I've hit a conundrum to which I cannot seem to find a solution. When a diversion that doesn't fit on the last page of a document and has to be deferred to the next (ie a float) is followed by a few lines of type that don't reach the bottom margin, processing stops at the end of the text and the di

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Mike Bianchi
On Thu, Jan 02, 2014 at 04:07:20PM +, Roger Leigh wrote: > On Thu, Jan 02, 2014 at 05:00:04PM +0100, Ingo Schwarze wrote: > > Hi Mike, > > > > Mike Bianchi wrote: > > > > > There is no man page for sh(1) . > > > There is no executable for /bin/sh . On Debian ... > > > > Sorry if that answ

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Ingo Schwarze
Hi, Tethys wrote on Fri, Jan 03, 2014 at 12:06:31AM +: > Colin Watson writes: >>Perhaps just: >> >> tmp=$d/eqn2graph$${$RANDOM:+-$RANDOM} >> >>then? That, or just tmp=$d/eqn2graph$$-`date +%Y%m%d%H%M%S` A collision is not dangerous in terms of security, and we are only talking about a f

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Tethys
Colin Watson writes: >Perhaps just: > > tmp=$d/eqn2graph$${$RANDOM:+-$RANDOM} > >then? Since it's not guaranteed to be present, why not just ignore $RANDOM and use our own randomly generated integer instead? Something like: groff_rand=$(dd if=/dev/urandom bs=8 count=1 2>/dev/null | sum

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Ingo Schwarze
Hi, Roger Leigh wrote on Thu, Jan 02, 2014 at 04:07:20PM +: > It isn't broken. It's just a minimal POSIX shell. It will work > fine with any script, providing you aren't using any non-standard > bash, ksh or zsh extensions. There might possibly be some new > POSIX shell standard features w

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Roger Leigh
On Thu, Jan 02, 2014 at 05:00:04PM +0100, Ingo Schwarze wrote: > Hi Mike, > > Mike Bianchi wrote: > > > There is no man page for sh(1) . > > There is no executable for /bin/sh . On Debian ... > > Sorry if that answer seems blunt, but it is not groff's > problem if the shell is broken in Debia

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Ingo Schwarze
Hi Mike, Mike Bianchi wrote: > There is no man page for sh(1) . > There is no executable for /bin/sh . On Debian ... Sorry if that answer seems blunt, but it is not groff's problem if the shell is broken in Debian. > For those reasons, I think #!/bin/sh should be outlawed! Hilarious. :-D

[Groff] Fwd: Re: Re: [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Daode
(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

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Daode
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.

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Daode
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,

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Colin Watson
On Thu, Jan 02, 2014 at 03:03:48PM +0100, Steffen Nurpmeso wrote: > 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. > |+ * con

Re: [Groff] [PATCH] '+' isn't a regex metacharacter in sed by default

2014-01-02 Thread Colin Watson
On Thu, Jan 02, 2014 at 02:52:42PM +0100, Werner LEMBERG wrote: > You have now write access :-) Thanks! > Please submit, together with a proper ChangeLog entry. Yes, I realised I'd forgotten ChangeLog shortly after sending. Done. -- Colin Watson [cjwat...

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Ralph Corderoy
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. :-) Cheers, Ralph.

Re: [Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Daode
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

[Groff] [PATCH] Appease "groff -wmac" when using eqn or pic

2014-01-02 Thread Colin Watson
* src/preproc/eqn/main.cpp: Define EQ and EN if they are not already defined, to appease "groff -wmac". * src/preproc/pic/main.cpp: Likewise for PS and PE. Fixes: http://bugs.debian.org/495713 --- ChangeLog| 8 src/preproc/eqn/main.cpp | 2 ++ src/preproc/pic/main.cpp | 4

Re: [Groff] [PATCH] '+' isn't a regex metacharacter in sed by default

2014-01-02 Thread Werner LEMBERG
> This is based on an old patch from Fumitoshi UKAI > in the Debian groff packaging, cleaned up and > extended to cover all fonts by me. You have now write access :-) Please submit, together with a proper ChangeLog entry. Werner

[Groff] [PATCH] Use bash for several contrib scripts

2014-01-02 Thread Colin Watson
--- ChangeLog| 7 +++ contrib/eqn2graph/eqn2graph.sh | 2 +- contrib/grap2graph/grap2graph.sh | 2 +- contrib/pic2graph/pic2graph.sh | 2 +- 4 files changed, 10 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index abf7534..33c5175 100644 --- a/Cha

[Groff] [PATCH] '+' isn't a regex metacharacter in sed by default

2014-01-02 Thread Colin Watson
This is based on an old patch from Fumitoshi UKAI in the Debian groff packaging, cleaned up and extended to cover all fonts by me. --- font/devascii/Makefile.sub | 4 ++-- font/devcp1047/Makefile.sub | 4 ++-- font/devhtml/Makefile.sub | 4 ++-- font/devlatin1/Makefile.sub | 4 ++-- font/devut

Re: [Groff] Where do we go from here?

2014-01-02 Thread Colin Watson
On Wed, Dec 11, 2013 at 01:51:49PM +, Colin Watson wrote: > I expect I'd switch the Debian packaging over to git once there's an > upstream tree to base it on. Money, putting where mouth is, etc.: http://anonscm.debian.org/gitweb/?p=users/cjwatson/groff.git The recent history is probably s

Re: [Groff] Where do we go from here?

2014-01-02 Thread Eric S. Raymond
Werner LEMBERG : > Umm, this blog entry is two years old. There is still some activity > on the bzr side, AFAICS – for example, version 2.6.0 has been released > in August 2013. Indeed. But I've seen more recent comments on the retrospective implying that the project is barely ticking over, and

Re: [Groff] Where do we go from here?

2014-01-02 Thread Werner LEMBERG
> I have learned recently that the bzr project is stalled out and > disintegrating. One of its senior devs has written a very > interesting elegy to it: > > http://www.stationary-traveller.eu/pages/bzr-a-retrospective.html Umm, this blog entry is two years old. There is still some activity on t

Re: [Groff] groff 1.22.2: typo in texinfo file?

2014-01-02 Thread Werner LEMBERG
> there seems to be a typo in the texinfo file for the current version > of groff. In my opinion "-Tdef" should rather read "-Tdev". Applied to git repository, thanks. Werner

Re: [Groff] Where do we go from here?

2014-01-02 Thread Eric S. Raymond
Colin Watson : > > You say you're happy with bzr's UI. Does it not seem to you that bzr is > > deeply confused about what its unit of work is? I tried learning bzr > > in order to work on Emacs and found that the distinction between repos > > and detached branches made my head hurt a lot. > >