"G. Vamsee Krishna" <[EMAIL PROTECTED]> writes:
> Well, if printf mimics C's printf, it's got to print 'A' :-)
POSIX also says that the argument for %c should be treated as a string,
not as a C constant.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux AG, Maxfeldstraße 5, 9
>From the documentation for coreutils:
,[ (coreutils)tail invocation ]
|On older systems, `tail' supports an obsolete option
| `-COUNTOPTIONS', which is recognized only if it is specified first.
| COUNT is a decimal number optionally followed by a size letter (`b',
| `k', `m') as in `-c',
I deleted it and added /usr/local/bin to my path. `printf "%c" 65'
is still outputting '6' but `/usr/local/bin/printf "%c" 65' is
giving 'A'. Any idea what's going wrong?
Shell builtin probobly.
If you are using GNU bash then the following will disable the printf
builtin:
enable -n prin
Hi,
On Wed, Jul 28, 2004 at 04:10:14PM -0700, Paul Eggert wrote:
> coreutils chown and chgrp mishandle some numeric uids and gids that
> have leading zeros. For example, "chown 010 file" is treated as
> "chown 8 file", where it should be like "chown 10 file". I discovered
> this while auditing f
Hi,
I'm using tail version "tail (coreutils) 5.2.1" and i can't use
# tail +2 foo
anymore.
# tail -n+2 foo
is ok. The "+n" Option seems to be a not documented feature of older tail
version, but it seems to be used quite often in the "demoscene". People in
the scene try to code a program with gr
Well, if printf mimics C's printf, it's got to print 'A' :-)
Also, I'm having some trouble with my patch. I've applied the patch and
did a "make". Now, in my coreutils/src/, I have the executables. "printf"
is working fine, as I expected it to work. Now, when I do a "make
install", it's getting
"G. Vamsee Krishna" <[EMAIL PROTECTED]> wrote:
> So, isn't `printf "%c" 65' supposed to print 'A' instead of '6'?
I agree that that would be the more useful behavior, but SUSv3 seems
to require "6".
paul
___
Bug-coreutils mailing list
[EMAIL PROTECTE
Hello,
The info page describes printf as
`printf' prints the FORMAT string, interpreting `%' directives and
`\' escapes in the same way as the C `printf' function.
So, isn't `printf "%c" 65' supposed to print 'A' instead of '6'? Please
let me know if it's a bug or not. Unable to sleep y'
Paul,
On Wed, 11 Aug 2004 11:08:02 -0700, Paul Eggert wrote:
>> Under ReliantUnix 5.43 wmemchr() and wmemcpy() are not in libc but in
>>libw.
>wmenchr and wmemcpy are in the C99 standard, so eventually they should
>be moved into the C Library on your platform.
ReliantUnix will be ceased by the
