Re: updated dialog(1) replacement for ports

2010-12-02 Thread Eitan Adler
On Thu, Dec 2, 2010 at 12:58 PM, Chip Camden wrote: > Quoth Eitan Adler on Thursday, 02 December 2010: >> Thank you for your comments >> >> > Every keystroke causes the screen to completely repaint. >> This can't be fully helped. Any valid key stroke is going to cause >> this. However I did make i

Re: updated dialog(1) replacement for ports

2010-12-02 Thread Chip Camden
Quoth Eitan Adler on Thursday, 02 December 2010: > Thank you for your comments > > > Every keystroke causes the screen to completely repaint. > This can't be fully helped. Any valid key stroke is going to cause > this. However I did make invalid keystrokes skip the repainting. Ugh -- I haven't lo

Re: updated dialog(1) replacement for ports

2010-12-02 Thread Eitan Adler
Thank you for your comments > Every keystroke causes the screen to completely repaint. This can't be fully helped. Any valid key stroke is going to cause this. However I did make invalid keystrokes skip the repainting. > If I accidentally leave off --port name, it core dumps. Heh - I didn't test

Re: updated dialog(1) replacement for ports

2010-12-02 Thread Chip Camden
Quoth Eitan Adler on Thursday, 02 December 2010: > I've been working on a dialog(1) replacement as used in the ports system. > The goal is to replace both the options and the license screen with a > single binary. It also features long descriptions, mutually exclusive > options, and some other nice

updated dialog(1) replacement for ports

2010-12-01 Thread Eitan Adler
I've been working on a dialog(1) replacement as used in the ports system. The goal is to replace both the options and the license screen with a single binary. It also features long descriptions, mutually exclusive options, and some other nice features. The source code be found here along with some