public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lascania at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug manual/14695] Wrong printf("%3s"...) Example --- manual subsection "12.12.6 Other Output Conversions"
Date: Wed, 10 Oct 2012 12:16:00 -0000 [thread overview]
Message-ID: <bug-14695-131-ynMLpGKGFh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14695-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14695
R N Alx <lascania at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #9 from R N Alx <lascania at gmail dot com> 2012-10-10 12:15:26 UTC ---
Mr Schwab
You said,
printf ("%.3s%-.6s", "no", "where") does not produce " nowhere "
You said,
printf ("%.3s%-.6s", "noOoO", "whereEeEeEeE") does not produce " noOwhereE "
THEY BOTH PRODUCE, " nowhere " RESPECTIVELY " noOwhereE "
Are you able too see pictures on your computer, or are you still using an old
text-screen terminal ?
My bug is about
R N Alx 2012-10-10 10:28:12 UTC
http://sourceware.org/bugzilla/show_bug.cgi?id=14695#c2
If you do not understand, please let other people have a look at the images,
and decide on this subject !
Do no longer stamp my bug as RESOLVED INVALID !
Thank You Sir !
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-10-10 12:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 9:39 [Bug manual/14695] New: " lascania at gmail dot com
2012-10-10 9:43 ` [Bug manual/14695] " lascania at gmail dot com
2012-10-10 9:46 ` lascania at gmail dot com
2012-10-10 10:01 ` schwab@linux-m68k.org
2012-10-10 10:28 ` lascania at gmail dot com
2012-10-10 10:42 ` schwab@linux-m68k.org
2012-10-10 10:58 ` lascania at gmail dot com
2012-10-10 11:00 ` lascania at gmail dot com
2012-10-10 11:06 ` aj at suse dot de
2012-10-10 11:16 ` lascania at gmail dot com
2012-10-10 11:59 ` schwab@linux-m68k.org
2012-10-10 12:16 ` lascania at gmail dot com [this message]
2012-10-10 12:33 ` schwab@linux-m68k.org
2012-10-11 11:31 ` lascania at gmail dot com
2012-10-11 11:53 ` schwab@linux-m68k.org
2012-10-11 13:18 ` aj at suse dot de
2012-10-11 14:57 ` lascania at gmail dot com
2012-10-11 15:04 ` lascania at gmail dot com
2012-10-11 16:15 ` schwab@linux-m68k.org
2012-10-11 16:51 ` ldv at altlinux dot org
2012-10-11 17:02 ` schwab@linux-m68k.org
2012-10-12 12:16 ` lascania at gmail dot com
2012-10-12 16:22 ` [Bug manual/14695] no example on printf precision " ldv at altlinux dot org
2014-06-17 4:04 ` fweimer at redhat dot com
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=bug-14695-131-ynMLpGKGFh@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).