tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: mdocml: Have exprcomp() accept a string instead of an array-pointer.
Date: Mon, 14 Nov 2011 12:37:47 +0100	[thread overview]
Message-ID: <20111114113747.GA27815@iris.usta.de> (raw)
In-Reply-To: <201111141007.pAEA76W0013878@krisdoz.my.domain>

Hi Kristaps,

oh well, i must have been asleep when looking at this yesterday;
sorry for providing a premature OK.  I just realized then following
when doing final tests before committing the merge to OpenBSD.

Isn't this going to break the difference between

  apropos UNIX manual

(which is supposed to search for all pages containing at least one
of the strings "UNIX" or "manual" in Nm or Nd), and

  apropos "UNIX manual"

(which is supposed to search for those containing "UNIX manual"
as one single string)?

And look here:

  $ apropos " .h "
  h2ph (1) - convert .h C header files to .ph Perl header files
  h2xs (1) - convert .h C header files to Perl extensions
  ischwarze@isnote $ apropos .h | wc -l
    11

How are you going to preserve these differences?

Is it really required to throw away the argument splitting done
by the shell, then start over, potentially breaking all the
quoting?

I'm holding off on the merge for a minute...
Maybe this has to be reverted?  :-(

Yours,
  Ingo

P.S.
Besides, you missed my small fix regarding trailing blanks.


kristaps@mdocml.bsd.lv wrote on Mon, Nov 14, 2011 at 05:07:06AM -0500:

> Log Message:
> -----------
> Have exprcomp() accept a string instead of an array-pointer.  Also, collapse
> the arguments in apropos(1) into a single string passed to exprcomp().  Ok
> schwarze@.
> 
> Modified Files:
> --------------
>     mdocml:
>         apropos.c
>         apropos_db.c
>         apropos_db.h
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

           reply	other threads:[~2011-11-14 11:37 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <201111141007.pAEA76W0013878@krisdoz.my.domain>]

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=20111114113747.GA27815@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=tech@mdocml.bsd.lv \
    /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 NNTP newsgroup(s).