public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "tee at sgi dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/693] mishandled '\B'
Date: Tue, 25 Jan 2005 13:53:00 -0000	[thread overview]
Message-ID: <20050125135329.12049.qmail@sourceware.org> (raw)
In-Reply-To: <20050125103144.693.kasal@ucw.cz>


------- Additional Comments From tee at sgi dot com  2005-01-25 13:53 -------
If the '\B' funtionality is fixed, then the man page will also need to be updated.
It currently says that '\B' "matches the empty string within a word."  Also, I
noticed that '\b' is not documented in the man page at all.

Thank you.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tee at sgi dot com


http://sources.redhat.com/bugzilla/show_bug.cgi?id=693

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2005-01-25 13:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 10:32 [Bug regex/693] New: " kasal at ucw dot cz
2005-01-25 13:53 ` tee at sgi dot com [this message]
2005-01-25 14:08 ` [Bug regex/693] " jakub at redhat dot com
2005-01-25 17:11 ` karl at freefriends dot org
2005-01-26 13:44 ` arnold at skeeve dot com
2005-01-26 17:33 ` jakub at redhat dot com
2005-01-30 12:09 ` arnold at skeeve dot com
2005-01-30 13:33 ` paolo dot bonzini at lu dot unisi dot ch
2005-01-31  5:40 ` kasal at ucw dot cz
2005-01-31  7:54 ` arnold at skeeve dot com
2005-02-16  4:19 ` roland at gnu dot org
2005-02-16 11:09 ` cvs-commit at gcc dot gnu dot org

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=20050125135329.12049.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs-regex@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).