Re: PATCH: Re: completion problem with filename including # (and pathmax stuff)

[Sven Wischnowsky <wischnow@informatik.hu-berlin.de>]

Bart Schaefer wrote:

> On Aug 4,  7:16am, Bart Schaefer wrote:
> } Subject: Re: PATCH: Re: completion problem with filename including # (and 
> }
> } One, we could pitch out the path length test and simply let domkdir()
> } fail -- and perhaps test the value of errno to decide whether to break
> } or continue as a result.
> 
> Sorry, that doesn't work if the goal is that no directories in the path
> get created if the whole path can't be created.  So that leaves us to
> dig around for a max path length.
> 
> I suspect the True64 pathconf() is actually broken in this respect, Sven.

It probably depends on how one defines `broken'. It *is*
documented. From the manual:


  For pathconf(), the path parameter points to the pathname of a file or
  directory.  Read, write, or execute permission of the	named file is not
  required, but	all directories	in the path leading to the file	must be
  searchable.

  ...

  If name is an	invalid	value, both pathconf() and fpathconf() return -1 and
  errno	is set to indicate the error.


And if mkdir calls pathconf on the name it should create...

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de