On 6/11/2012 2:03 PM, Warren Block wrote:
> On Sat, 9 Jun 2012, Warren Block wrote:
>
That's a nice idea, how do you make it work with dialog?
>>>
>>> No idea, this is still the design phase. :) Actually, a message I
>>> now can't find suggested that dialog may be able to do it unchanged.
>>
On Mon, 11 Jun 2012, Warren Block wrote:
Here is a patch to do it.
To use, apply patch. Pick a port and edit the option descriptions to be
longer than 49 characters. Then run 'make config'.
Notes:
This patch only does descriptions for the plain options right now. Changes to
the multi and
On Sat, 9 Jun 2012, Warren Block wrote:
That's a nice idea, how do you make it work with dialog?
No idea, this is still the design phase. :) Actually, a message I now
can't find suggested that dialog may be able to do it unchanged.
Followup:
dialog --item-help \
--checklist "Contrived op
On Sun, Jun 10, 2012 at 01:00:05PM +0300, Vitaly Magerya wrote:
> Baptiste Daroussin wrote:
> > There was a PR[1] to use some dialog(1) feature to expose it to
> > the user, would be nice if that extended description could
> > implemented that way (using help button from dialog(1)) I do not
> > pl
Baptiste Daroussin wrote:
> There was a PR[1] to use some dialog(1) feature to expose it to
> the user, would be nice if that extended description could
> implemented that way (using help button from dialog(1)) I do not
> plan to work on this now if someone want to do it that will be
> great
>
> 1
On Sat, 9 Jun 2012, Warren Block wrote:
On Sat, 9 Jun 2012, Doug Barton wrote:
On 06/09/2012 17:54, Warren Block wrote:
On Sat, 9 Jun 2012, Doug Barton wrote:
On 06/06/2012 22:27, Dave Hayes wrote:
Personally, a 'pkg-options-descr' text file would suit me just fine.
For those on -ports,
On 06/09/2012 18:10, Warren Block wrote:
>> That's a nice idea, how do you make it work with dialog?
>
> No idea, this is still the design phase. :) Actually, a message I now
> can't find suggested that dialog may be able to do it unchanged.
We have a solution that unquestionably will work, now.
On Sat, 9 Jun 2012, Doug Barton wrote:
On 06/09/2012 17:54, Warren Block wrote:
On Sat, 9 Jun 2012, Doug Barton wrote:
On 06/06/2012 22:27, Dave Hayes wrote:
Personally, a 'pkg-options-descr' text file would suit me just fine.
For those on -ports, the context is, "How do we provide more in
On 06/09/2012 17:54, Warren Block wrote:
> On Sat, 9 Jun 2012, Doug Barton wrote:
>
>> On 06/06/2012 22:27, Dave Hayes wrote:
>>> Personally, a 'pkg-options-descr' text file would suit me just fine.
>>
>> For those on -ports, the context is, "How do we provide more information
>> about what the va
On Sat, 9 Jun 2012, Doug Barton wrote:
On 06/06/2012 22:27, Dave Hayes wrote:
Personally, a 'pkg-options-descr' text file would suit me just fine.
For those on -ports, the context is, "How do we provide more information
about what the various options mean?" This idea seems reasonable to me,
w
On Sat, Jun 09, 2012 at 09:35:12AM -0700, Doug Barton wrote:
> On 06/06/2012 22:27, Dave Hayes wrote:
> > Personally, a 'pkg-options-descr' text file would suit me just fine.
>
> For those on -ports, the context is, "How do we provide more information
> about what the various options mean?" This i
On 06/09/2012 11:35 AM, Doug Barton wrote:
On 06/06/2012 22:27, Dave Hayes wrote:
Personally, a 'pkg-options-descr' text file would suit me just fine.
For those on -ports, the context is, "How do we provide more information
about what the various options mean?" This idea seems reasonable to me
On 06/06/2012 22:27, Dave Hayes wrote:
> Personally, a 'pkg-options-descr' text file would suit me just fine.
For those on -ports, the context is, "How do we provide more information
about what the various options mean?" This idea seems reasonable to me,
what do others think?
Doug
--
This
13 matches
Mail list logo
