public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Another USE question
Date: Wed, 27 May 2009 11:30:11 +0300	[thread overview]
Message-ID: <gvitm0$7n5$1@ger.gmane.org> (raw)
In-Reply-To: <200905271015.07336.volkerarmin@googlemail.com>

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.




  reply	other threads:[~2009-05-27  8:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 22:52 [gentoo-user] Another USE question KH
2009-05-26 22:59 ` Alan McKinnon
2009-05-26 23:06   ` KH
2009-05-27  7:05     ` Alan McKinnon
2009-05-26 23:03 ` [gentoo-user] " Nikos Chantziaras
2009-05-26 23:07   ` KH
2009-05-26 23:33     ` Keith Dart
2009-05-26 23:52       ` Peter Humphrey
2009-05-27  0:02         ` Keith Dart
2009-05-27  1:16           ` Peter Humphrey
2009-05-27  1:19             ` Dale
2009-05-27  1:20             ` Keith Dart
2009-05-27  1:41               ` Dale
2009-05-27  2:23                 ` Keith Dart
2009-05-27  7:01                   ` Alan McKinnon
2009-05-27  8:00       ` Stroller
2009-05-27  8:15         ` Volker Armin Hemmann
2009-05-27  8:30           ` Nikos Chantziaras [this message]
2009-05-27  9:11             ` Volker Armin Hemmann
2009-05-27  9:31               ` Nikos Chantziaras
2009-05-27  9:39                 ` Volker Armin Hemmann
2009-05-27 12:45               ` Stroller
2009-05-27  9:44             ` Neil Bothwick
2009-05-27 12:26           ` Stroller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gvitm0$7n5$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox