On Mittwoch 27 Mai 2009, Stroller wrote:
> On 27 May 2009, at 00:33, Keith Dart wrote:
> >>> ...
> >>> USE_FOO="this n that"
> >>> USE_BAR="some more flags"
> >>> BLAH="whatever else there might be"
> >>>
> >>> USE="${USE_FOO} ${USE_BAR} ${BLAH}
> >>
> >> Thank's. That is exactly what I was looking for.
> >
> > But that will likely break, or render useless, the ufed tool.
> >
> > If you don't use that, you probably should.
>
> I'm really unconvinced by ufed.
>
> In a standard terminal window, 80 characters wide, the descriptions
> are too long and instead of wrapping around to the next line they fall
> off the end of the screen and you can't read them. Sure, I can resize
> the terminal window, but I don't want to have to do that manually each
> time I run ufed, then resize it back to my usual size again
> afterwards. ufed is about the only program I've used which doesn't
> seem right in my "standard" terminal window size of 50 rows x 80
> columns.or you can, you know, scroll it. Protip: arrow keys, left, right. > > ufed has seemed to me to behave unexpectedly on occasions. I have run > it, added only one USE flag and then when I re-run `emerge -pv world` > more than one additional USE setting has changed. WTF?!?! never happened here. But maybe you did more than just change one flag before you did the pv world - like emerge sync - and some default flag was changed? > > This is why I have arrived at the combination of euse (and now `equery > uses`) to view USE descriptions and flagedit for setting them. I think > that from a usability point of view these are easier than either ufed > or a text editor. except that you obviously did not use ufed.
