From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: <zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: Re: completion problem with filename including # (and pathmax stuff)
Date: Fri, 4 Aug 2000 14:47:30 +0400 [thread overview]
Message-ID: <000301bffe01$63aa22a0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1000804071658.ZM23782@candle.brasslantern.com>
>
> There are a couple of things we could do.
>
> 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.
>
> Two, we could cause zpathmax() to lop off the tail of the path and call
> itself until it actually does find a maximum path length, then add the
> tail back on and repeat the strlen() test. That might be a good thing
> to have for the general case anyway.
>
> Or we could do both of the above.
>
Or fall back to _POSIX_PATH_MAX (if system supports pathconf(), it rorbably
suports it as well):
PATH_MAX
Maximum number of bytes in a pathname, including the terminating null
character. Minimum Acceptable Value: _POSIX_PATH_MAX
-andrej
next prev parent reply other threads:[~2000-08-04 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-04 7:01 Sven Wischnowsky
2000-08-04 7:16 ` Bart Schaefer
2000-08-04 7:38 ` Bart Schaefer
2000-08-04 10:47 ` Andrej Borsenkow [this message]
2000-08-04 13:35 ` Clint Adams
-- strict thread matches above, loose matches on Subject: below --
2000-08-04 7:42 Sven Wischnowsky
2000-08-04 13:38 ` Clint Adams
2000-08-03 13:30 Sven Wischnowsky
2000-08-03 14:38 ` Clint Adams
2000-08-03 14:53 ` Clint Adams
2000-08-04 21:51 ` Tanaka Akira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000301bffe01$63aa22a0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).