Hi Werner,
On 11/11/2014 08:18 PM, Werner LEMBERG wrote:
[Please always address queries to the groff mailing list.]
Thanks for reposting. Yeah, it is better and without noise in your mail.
From: Jan Chaloupka
Subject: groff 1.22.3 not building on Fedora 22
Date: Tue, 11 Nov 2014 16:45:34 +
Hi Ingo
On 11/11/2014 08:51 PM, Ingo Schwarze wrote:
Hi Werner and Jan,
Werner LEMBERG wrote on Tue, Nov 11, 2014 at 08:18:13PM +0100:
Jan Chaloupka wrote:
I was trying to update groff to 1.22.3 [1].
But Makefile is failing me :)
There is the following error:
make[2]: *** No rule to make tar
Eli Zaretskii wrote:
|> Date: Tue, 11 Nov 2014 13:50:48 +0100
|> From: Steffen Nurpmeso
|>
|> Doug McIlroy wrote:
|>|* For a ludicrous example, when I type my own name,
|>| M. Douglas McIlroy
|>|at the beginning of a line--as for a signature or author line--
|>|Open Office thinks that I
Hi all,
> On Wed, Oct 08 2014 at 11:34:26 AM, Werner LEMBERG wrote:
>>> Also, how will we proceed when we will consider that this automake
>>> migration is ready for merge into master? The normal process would
>>> be to squash all the commits into a single one on master, but given
>>> the high n
> cc: Eli Zaretskii
> Date: Tue, 11 Nov 2014 20:12:13 +
> From: Ralph Corderoy
>
> Hi Keith,
>
> > > Hmm, does that mean the argv[] processing in groff's code is a place
> > > to transliterate when it's known to be a filename?
> >
> > How can that possibly be known? When argv[] processing
> Date: Tue, 11 Nov 2014 19:46:22 +
> From: Keith Marshall
> CC: groff@gnu.org
>
> Perhaps Eli's explanation is overly simplistic. In reality, cmd.exe
> doesn't process those directory separators, no matter whether they are
> specified as slashes, (as POSIX and $DEITY mandate), or reversed
>
> cc: groff@gnu.org
> Date: Tue, 11 Nov 2014 19:20:19 +
> From: Ralph Corderoy
>
> > > and so wrappers around the code that's cooking up the a\b\c in the
> > > first place could transliterate there without caring where the a/b/c
> > > is later to be used?
> >
> > The problem with this approa
Hi Keith,
> > Hmm, does that mean the argv[] processing in groff's code is a place
> > to transliterate when it's known to be a filename?
>
> How can that possibly be known? When argv[] processing is performed,
> all we see is a sequence of strings; they have no semantic meaning.
At some point,
Hi Werner and Jan,
Werner LEMBERG wrote on Tue, Nov 11, 2014 at 08:18:13PM +0100:
> Jan Chaloupka wrote:
>> I was trying to update groff to 1.22.3 [1].
>> But Makefile is failing me :)
>> There is the following error:
>>
>> make[2]: *** No rule to make target
>> '/builddir/build/BUILD/groff-1.22
On 11/11/14 19:20, Ralph Corderoy wrote:
> Hi Eli,
>
> Thanks for the explanation.
>
>>> Am I right in thinking that Windows' API is as happy with a/b/c as
>>> a\b\c
>>
>> That's correct.
>>
>>> and so wrappers around the code that's cooking up the a\b\c in the
>>> first place could transliterate
Hi Eli,
Thanks for the explanation.
> > Am I right in thinking that Windows' API is as happy with a/b/c as
> > a\b\c
>
> That's correct.
>
> > and so wrappers around the code that's cooking up the a\b\c in the
> > first place could transliterate there without caring where the a/b/c
> > is later
[Please always address queries to the groff mailing list.]
From: Jan Chaloupka
Subject: groff 1.22.3 not building on Fedora 22
Date: Tue, 11 Nov 2014 16:45:34 +0100
> I was trying to update groff to 1.22.3 [1]. But Makefile is failing
> me :) There is the following error:
>
> make[2]: *** No
> Date: Tue, 11 Nov 2014 13:50:48 +0100
> From: Steffen Nurpmeso
>
> Doug McIlroy wrote:
> |* For a ludicrous example, when I type my own name,
> | M. Douglas McIlroy
> |at the beginning of a line--as for a signature or author line--
> |Open Office thinks that I've begun a paragraph numbered
> Date: Mon, 10 Nov 2014 19:08:00 +
> From: Ralph Corderoy
>
> One thing I think I've missed: why has this come to light now?
Because I make a point of investigating any strange messages from the
program, while those who came before me didn't?
To put this in context, I bumped into this whe
> From: Doug McIlroy
> Date: Sun, 09 Nov 2014 11:54:51 -0500
Sorry to reply only now, but I don't subscribe to the list, so I don't
receive messages unless I'm explicitly CC'ed.
> It is safe to convert backslashes to slashes only when it is
> known that the literal string is indeed a file name.
|Ralph Corderoy wrote:
||> (For the list: mawk(1) requires a fflush("") in order to "getline <
||> NAME" a file NAME that has been written via "print >> NAME" before,
||> even though fflush("") is not standard and i cannot imagine a
||> situation where an awk(1) script would not like to see a
Ralph Corderoy wrote:
|> (For the list: mawk(1) requires a fflush("") in order to "getline <
|> NAME" a file NAME that has been written via "print >> NAME" before,
|> even though fflush("") is not standard and i cannot imagine a
|> situation where an awk(1) script would not like to see a fflus
Doug McIlroy wrote:
|* For a ludicrous example, when I type my own name,
| M. Douglas McIlroy
|at the beginning of a line--as for a signature or author line--
|Open Office thinks that I've begun a paragraph numbered with
|a Roman numeral, and proceeds to tack "MI." onto the beginning
|of th
Hallo Ingo, list,
Ingo Schwarze wrote:
|Steffen Nurpmeso wrote on Mon, Nov 10, 2014 at 03:21:36PM +0100:
|> Ok, but i really wonder now -- why? If it is normal that .Va and
|> other requests extend until the next macro switches the current
|> mode (the mdoc macros seem to transport significa
Hi Steffen,
> (For the list: mawk(1) requires a fflush("") in order to "getline <
> NAME" a file NAME that has been written via "print >> NAME" before,
> even though fflush("") is not standard and i cannot imagine a
> situation where an awk(1) script would not like to see a fflush("") on
> NAME be
20 matches
Mail list logo
