See the discussion December 2014:
https://lists.gnu.org/archive/html/bug-texinfo/2014-12/threads.html#00059
The DocBook output for @indentedblock is still (at least in 6.1) broken:
It just creates a with the contents.
On the other hand, @quotation creates a around the contents.
My suggestion
Sorry Gavin for the stupid email - one should not write emails before breakfast
and coffee.
--
Sent from my mobile device. Please excuse my brevity.
On Wed, 27 Apr 2016 06:45:05 +0900
Norbert Preining wrote:
> On Tue, 26 Apr 2016, Gavin Smith wrote:
> > "...the Bourne shell does not systematically split
> > variables and back-quoted expressions, in particular on
> > the right-hand side of assignments and in the argument
>
You cannot expect bash behaviour then.
It's bourne behavior not bash behavior. As you know, we go to great
lengths to avoid bash dependencies in texi2dvi (and in all other core
GNU shell scripts).
However, as I recall, there is a bug in some versions of bash that
require
case "$foo"
On Tue, 26 Apr 2016, Gavin Smith wrote:
> "...the Bourne shell does not systematically split variables and
> back-quoted expressions, in particular on the right-hand side of
> assignments and in the argument of case."
Gavin, texi2dvi starts with
/bin/sh
that means it can be *any* shell
On 25 April 2016 at 21:31, Mattias Andrée wrote:
> Fix support for whitespace in working directory.
>
> Keep me CC:ed, I'm not subscribed to the mailing-list.
I don't think this change does anything?
Reference
On Tue, 26 Apr 2016 22:35:36 +0100
Gavin Smith wrote:
> On 25 April 2016 at 21:31, Mattias Andrée
> wrote:
> > Fix support for whitespace in working directory.
> >
> > Keep me CC:ed, I'm not subscribed to the mailing-list.
>
> I don't think