[Bashburn-info] A change in the configure menu.
Brought to you by:
bashburn
|
From: Steven W. O. <st...@sy...> - 2008-09-02 02:11:11
|
I want to do this but I'm too tired to do it now. I just rode my bike for 47 miles and I'm beat. Here's the deal: The configure menu is just stoopid. It gives us 21 options to change something. Then the last three options are apply changes, apply defaults, and Back. If you make a change then it is altered in your namespace but not 'committed' to your .bashburnrc. If you want to say back then you have no way to revert to what it was. It doesn't make sense. Here's what I want to do: When you make a change, the change will be reflected in the menu but your variables will *not* be changed. The apply changes option will actually change the values of the affected variables AND write out the new .bashburnrc . If the changes have not yet been committed then the menu display will show the value you selected with a * at the end of the line to show that it was modified but not saved. (I think emacs does it that way too. ;-) So you would see either | 4) Speed (-1) or | 4) Speed (-2)* And your actions will look (something) like this: Back will simply discard the changes if they have not been applied. |-(Actions) |- # 22) Apply changes |- # 23) Apply defaults |- # 23) Revert changes | 0) Back One more thing: NO ONE is referencing BBISCONF. Unless anyone cares, I'm discarding it. There are probably more but that one is looking at me. (Did I mention I'm dog tired?) -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |