[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnulib broken on systems lacking fchdir

From: Ben Pfaff
Subject: Re: gnulib broken on systems lacking fchdir
Date: Thu, 30 Nov 2006 08:58:29 -0800
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)

Bruno Haible <address@hidden> writes:

> Huh? I think there is a misunderstanding. The GNU standards don't want
> 'pathname' to occur in the documentation in the sense as POSIX uses it,
> because of the PATH variable and the concept of search paths. Paul then
> doesn't want to use 'pathname' in code either, so that there are less
> differences between the code and user documentation. But 'filename' and
> 'file' are fine according to everyone.

The standards.info I have here says that "file name" should be
two words, not one:

       Please do not use the term "pathname" that is used in Unix
    documentation; use "file name" (two words) instead.  We use the term
    "path" only for search paths, which are lists of directory names.
"MONO - Monochrome Emulation
 This field is used to store your favorite bit."
--FreeVGA Attribute Controller Reference

reply via email to

[Prev in Thread] Current Thread [Next in Thread]