and this is a nice long comment that stretches lots....................................................................................................................................................................................................................................................................................................................................................................

ok, that wasn't a long comment, it was a long word (which will in fact stretch an email. lets see how it copes when pasting some typical bug data....
./configure --with-apxs=/etc/httpd/bin/apxs --enable-track-vars --enable-ftp --with-gd=../gd-1.8.4 --prefix=/etc/php --sysconfdir=/etc/php --with-imap=../imapServer

What you are describing is normal behaviour.

The way exec() works is that it executes the first argument, and then returns all the output to the second argument as an array. Finally, any status the command returns is sent to the third argument, if specified. 

You may find these pages informative:

http://www.php.net/manual/en/function.exec.php
http://www.php.net/manual/en/ref.array.php

Previous Comments:

ok, i'll stop hijacking this bug for now.

more testing.

Bleh

I love weeeeeeeeed!

Blegh from Lynx

mmmm, the submit button at the bottom would help a lot for me, a lynx user.

Derick

I'M NOT FROM VL-SRM.NET!!!!!!!!! :)

Ene mene muh und draussen there you are.

greetings from the usergroup meeting cologne!

Testing on two platforms, in parallel.  Sorry.

Simply adding another comment for testing purposes.

Sorry.

<?php
  /* How does it do on code?
  */
?>

<?php
  # I can't type a TAB, but what if I paste it?
	$date = date('M d Y');
	$query = "select album_title, inventory.quantity, 
band_name, email_address, fname, lname ";
?>

blah blah blah.

hmm.

hop hop... Weed is weird. For my wedding I'll have a magic cauldron with weed in it. Lots of it. Magic, that is.

Does it support <b>some</b> <i>HTML</i> ?

Or even (<script

language="JavaScript"><!-- // alert('JavaScript !'); //--></script>JavaScript) ?

what about the <pre>
&lt;pre&gt; tag ?





























































</pre> ?

May I suggest to use the two following functions.
The first one is to get rid of JavaScript and unwanted stuff before storing to the database ; the second one for automagic formatting while displaying the stored message. It's useful to have two functions for cases when one can edit the message.

function msgClean($txt) {
 
    /* SCRIPT PATTERN MATCHING */
    $txt = preg_replace("/<script([\n\r]*.*)>([\n\r]*|[^>]*.*)<\/script>/i",'',$txt);
 
    /* STRIP UNWANTED HTML TAGS */
    $txt = strip_tags($txt,"<b></b><i></i><u></u>");
 
    return $txt;
}
function msgFormat($txt) {
 
    /* PLEASE KEEP THAT IN ORDER -- how */

    /* LINK MATCHING PATTERN */
    $txt = preg_replace("/([[:alpha:]]+):\/\/([\w\d-#\?=\/&]+[^\s_]+)(?<![,.:;])/i",'<a href="\1://\2">\1://\2</a>',$txt)

    /* EMAIL MATCHING PATTERN */
    $txt = preg_replace("/(?!mailto:)([[:alnum:]-.]+)@([[:alnum:]-.]+\.[[:alnum:]]{1,3})(?<![,.:;])/i",'<a href="mailto:\

    /* PARAGRAPH MATCHING PATTERN */
    $txt = preg_replace("/(\r\n\r\n|\n\n)/i",'<p>',$txt);
 
    /* SINGLE LINE MATCHING PATTERN */
    $txt = preg_replace("/(\r\n|\n)/i",'<br />',$txt);
 
    return  $txt;
}

looks pretty good, but the metadata at the top (bug #, status, etc) is 
somewhat mangled in w3m. Looks better in links, and (ironically) best in lynx.

oh, and the submit button between the mailaddress input and the textarea on 
this page is IMO placed badly -- it'll result in lots of empty comments.

it would only result in lots of empty comments if we didn't check to make sure a comment was submitted. :)

this should look a little more tolerable in netscape 4. making sure it still works.

This bug is crazy, I like!







a lot.

Shoudn't we make this bug a bogus so it doesn't show up in the stats???

just testing.

oops, the from address wasn't quite right. take 2.

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

The bug system is not the appropriate forum for asking support
questions. For a list of a range of more appropriate places to ask
for help using PHP, please visit http://www.php.net/support.php

The bug system is not the appropriate forum for asking support
questions. For a list of a range of more appropriate places to ask
for help using PHP, please visit http://www.php.net/support.php

this should go through.

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".


should go through.