public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Another USE question
Date: Wed, 27 May 2009 10:15:07 +0200	[thread overview]
Message-ID: <200905271015.07336.volkerarmin@googlemail.com> (raw)
In-Reply-To: <2DD601F9-8CEF-480A-B945-A1988907ECF2@stellar.eclipse.co.uk>

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.



  reply	other threads:[~2009-05-27  8:15 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 [this message]
2009-05-27  8:30           ` Nikos Chantziaras
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=200905271015.07336.volkerarmin@googlemail.com \
    --to=volkerarmin@googlemail.com \
    --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