On Mittwoch 27 Mai 2009, Nikos Chantziaras wrote:
> Volker Armin Hemmann wrote:
> > 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.
>
> Nah, that just doesn't cut it. It's annoying as hell. It's far less
> annoying to simply "equery uses" on the USE flags you see during an
> "emerge -a" and edit make.conf by hand instead of doing the
> scroll-circus. You try to read text by constantly scrolling right and
> left. It doesn't work for me, and probably for the majority of others
> neither.
oh yeah, scrolling for a tenth of a second is so much slower than feeding
equery or euse and then open make.conf, type, check that you did not forget
something ....
