-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 12/21/2008 5:51 PM:
>
> - element="Support for systems lacking POSIX:2001"
> + element="Support for systems lacking POSIX:200"
typo?
- --
Don't work too hard, make some time for fun as well!
Eric Blake e.
Part 5 of the doc change: Change the subtitles in the generated modules list.
2008-12-21 Bruno Haible
* MODULES.html.sh: Change section titles to refer to POSIX:2008.
--- MODULES.html.sh.orig2008-12-22 01:49:53.0 +0100
+++ MODULES.html.sh 2008-12-22 01:49:40.00
Jim Meyering wrote:
> Users expect tools like chmod -R, du and find to work even when run from
> an unreadable directory. Once you impose that requirement, you have
> admitted that save_cwd and restore_cwd are required. With them you must
> admit the possibility of restore_cwd failure. And opena
"James Youngman" wrote:
> On Mon, Dec 15, 2008 at 12:18 AM, Bruno Haible wrote:
>> However, for openat-die.c I don't see a good replacement. In particular, I
>> don't see a way how openat_restore_fail() could be handled in library code.
>> A program cannot simply continue when its current directo
Bruno Haible wrote:
>> openat emulation depends on save-cwd (GPL), which can call xgetcwd (GPL),
>> which
>> in turn can call xalloc_die (GPL)?
>
> openat() and the related system calls are not supposed to signal errors by
> themselves and exit the program. Is it possible to restructure the code
James Youngman wrote:
> only fchdir does have the
> advantage that we know that restoring the current directory can't fail.
Yes, this should work on Unix systems. On mingw, open (".", O_RDONLY) fails,
but that should be fixable by modifying lib/open.c and lib/fchdir.c.
But is that restriction -
On Mon, Dec 15, 2008 at 12:18 AM, Bruno Haible wrote:
> However, for openat-die.c I don't see a good replacement. In particular, I
> don't see a way how openat_restore_fail() could be handled in library code.
> A program cannot simply continue when its current directory is different from
> what it
Hi Jim,
> openat emulation depends on save-cwd (GPL), which can call xgetcwd (GPL),
> which
> in turn can call xalloc_die (GPL)?
openat() and the related system calls are not supposed to signal errors by
themselves and exit the program. Is it possible to restructure the code so that
they only re
Bruno Haible wrote:
> Part 4: New functions.
>
> Jim, some of these functions (fchmodat, fchownat, fdopendir, fstatat, mkdirat,
> openat, unlinkat) are provided by gnulib module 'openat'. Others (faccessat,
> linkat, mkfifoat, mknodat, readlinkat, renameat, symlinkat, utimensat) are
> not.
> What
Part 4: New functions.
Jim, some of these functions (fchmodat, fchownat, fdopendir, fstatat, mkdirat,
openat, unlinkat) are provided by gnulib module 'openat'. Others (faccessat,
linkat, mkfifoat, mknodat, readlinkat, renameat, symlinkat, utimensat) are not.
What do you think about
- splitting t
Part 2: Updating the references to POSIX to refer to the new spec.
2008-12-14 Bruno Haible
Update doc for POSIX:2008.
* doc/posix-functions/*.texi: Update URL of POSIX specification.
--- doc/posix-functions/FD_CLR.texi.orig2008-12-14 14:36:13.0
+0100
+++ doc/p
Eric Blake wrote:
> POSIX 2008 is now freely available at:
> ...
> http://www.opengroup.org/onlinepubs/9699919799/toc.htm
I'm starting to update the gnulib documentation. Part 1: Handling of
functions that were removed.
2008-12-14 Bruno Haible
Update doc for POSIX:2008.
* doc/
Ben Pfaff <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>> Do any of you know of a pdf-to-text converter that is better than
>> pdftotxt? pdftotxt does not preserve line breaks, table formatting,
>> displayed code, etc. Even the official .txt version of the previous
>> rel
Jim Meyering <[EMAIL PROTECTED]> writes:
> Do any of you know of a pdf-to-text converter that is better than
> pdftotxt? pdftotxt does not preserve line breaks, table formatting,
> displayed code, etc. Even the official .txt version of the previous
> release of POSIX had many conversion-artifact
Eric Blake wrote:
> POSIX 2008 is now freely available at:
>
> http://www.opengroup.org/bookstore/catalog/c082.htm
>
> which, once you accept a cookie, redirects to:
>
> http://www.opengroup.org/onlinepubs/9699919799/toc.htm
With this patch, the generated MODULES.html file refers to the new POS
Hi Jim,
> Do any of you know of a pdf-to-text converter that is better than
> pdftotxt? pdftotxt does not preserve line breaks, table formatting,
> displayed code, etc. Even the official .txt version of the previous
> release of POSIX had many conversion-artifact errors.
I would use a good html
Eric Blake <[EMAIL PROTECTED]> wrote:
> POSIX 2008 is now freely available at:
>
> http://www.opengroup.org/bookstore/catalog/c082.htm
>
> which, once you accept a cookie, redirects to:
>
> http://www.opengroup.org/onlinepubs/9699919799/toc.htm
>
> [My favorite page - the new examples section for t
On Tuesday 09 December 2008 17:02:51 Eric Blake wrote:
> POSIX 2008 is now freely available at:
>
> http://www.opengroup.org/bookstore/catalog/c082.htm
>
> which, once you accept a cookie, redirects to:
>
> http://www.opengroup.org/onlinepubs/9699919799/toc.htm
wonder if the canonical link will be
POSIX 2008 is now freely available at:
http://www.opengroup.org/bookstore/catalog/c082.htm
which, once you accept a cookie, redirects to:
http://www.opengroup.org/onlinepubs/9699919799/toc.htm
[My favorite page - the new examples section for touch(1):
http://www.opengroup.org/onlinepubs/969991
19 matches
Mail list logo
