public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Oosthoek <simon-Hf+EfML1qzhUecB6AVeNQA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: Jan Christiaan van Winkel
	<jc-I2/4/b2VdYhUecB6AVeNQA@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: regex.7 manpage is awful
Date: Mon, 12 Jan 2009 11:30:03 +0100	[thread overview]
Message-ID: <200901121130.03675.simon@atcomputing.nl> (raw)
In-Reply-To: <cfd18e0f0901120208v48551ce7i2268226bd9fbb1bd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Monday 12 January 2009 11:08, Michael Kerrisk wrote:
> Simon,
>
> [...]
>
> > Anyway, the point of this e-mail:
> > - the current page is awful, hard to read and ambiguous
> > - the implied POSIX decision to obsolete basic REs is bad
> > - I would not recommend this manpage to anyone trying to understand
> >  REs
> >
> > If possible I'd like to change the world ;-) but failing that, a
> > less ambiguous (and easier to read) version of the regex(7) manpage
> > would be greatly appreciated!
>
> You are not the first to note that the regex(7) page could be better.
> But so far, no one has done the work to make it better.  My time is
> limited, so I'm unlikely to get to it in a hurry.  Help would be
> greatly appreciated...

I understand, the same goes for me, but if I can get some time in, I'll 
try to get something going...
Petr's suggestions are a good start I think.

I'll keep it in the back of my mind for when I get some time... (I'll try 
to get to it sooner rather than later)

Cheers

Simon
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-01-12 10:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 10:22 regex.7 manpage is awful Simon Oosthoek
     [not found] ` <20090109102208.GA22747-earCsCjlB1dYz1uS2RbbqIS2ikGnqaxS@public.gmane.org>
2009-01-09 11:38   ` Petr Baudis
     [not found]     ` <20090109113852.GB21648-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>
2009-01-12 10:17       ` Michael Kerrisk
2009-01-12 10:29       ` Simon Oosthoek
2009-01-12 10:08   ` Michael Kerrisk
     [not found]     ` <cfd18e0f0901120208v48551ce7i2268226bd9fbb1bd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-12 10:30       ` Simon Oosthoek [this message]

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=200901121130.03675.simon@atcomputing.nl \
    --to=simon-hf+efml1qzhuecb6avenqa@public.gmane.org \
    --cc=jc-I2/4/b2VdYhUecB6AVeNQA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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