On Wed, Jul 7, 2010 at 9:24 PM, Sami Samhuri wrote:
> (sent to the list instead of just Dan this time, sorry Dan, gmail user fail)
> I opened the original bug report on this, and it was resolved a day or two
> ago. The committed patch sets COMMAND_MODE=unix2003. I'm not sure if one
> approach is b
(sent to the list instead of just Dan this time, sorry Dan, gmail user fail)
I opened the original bug report on this, and it was resolved a day or two
ago. The committed patch sets COMMAND_MODE=unix2003. I'm not sure if one
approach is better or more portable than the other, just letting you know
Hi Seth,
I've submitted your patch to Bugzilla:
https://issues.basho.com/show_bug.cgi?id=355
The development team will review the information and decide whether or not
to make the proposed change.
Thanks,
Dan
Daniel Reverri
Developer Advocate
Basho Technologies, Inc.
d...@basho.com
On Wed, Ju
On Sat, Jul 3, 2010 at 5:52 PM, Andrew Tunnell-Jones wrote:
> Hi Seth,
>
> That option is supported by OS X however it is only enabled if COMMAND_MODE
> is set as unix2003. This is set by default in Apple's Terminal application
> but not in iTerm:
That's quite interesting. I still think it mak
Hi Seth,
That option is supported by OS X however it is only enabled if COMMAND_MODE is
set as unix2003. This is set by default in Apple's Terminal application but not
in iTerm:
Last login: Sun Jul 4 00:40:36 on ttys002
~
$ ps -f
ps: illegal option -- f
usage: ps [-AaCcEefhjlMmrSTvwXx] [-O fmt
