| 1 |
On Sat, Dec 5, 2009 at 9:16 PM, daid kahl <daidxor@×××××.com> wrote: |
| 2 |
>> On 12/4/2009 10:21 PM, Dale wrote: |
| 3 |
>>> |
| 4 |
>>> Thanks goodness for Konsole and being able to scroll up. |
| 5 |
>> |
| 6 |
>> Where I come from, we use " | less" :p |
| 7 |
> |
| 8 |
> Meh, just > into /tmp and use anything you want to view it if you |
| 9 |
> really want to be hardcore. |
| 10 |
> |
| 11 |
> Less is really crappy for emerges at console-login. It requires you |
| 12 |
> to hold down the page-down button pretty much (unless there is some |
| 13 |
> option I don't know about? Does captial G do it like in vi?) I also |
| 14 |
> don't like that less makes my colors disappear. Sure, it's not really |
| 15 |
> important, but I mostly say this so someone can tell me I'm wrong and |
| 16 |
> how to fix it. |
| 17 |
|
| 18 |
In less, pressing F will put it in "follow" mode, to act like tail. |
| 19 |
Not sure how that'd work for monitoring emerges and such on the fly |
| 20 |
(never really used that feature, just know of it), but less is, in |
| 21 |
general, very handy for sifting through emerge --pretend. |
| 22 |
|
| 23 |
"emerge --color y ..." will override disabling color when the output |
| 24 |
isn't a tty (which is the default because it doesn't know whether |
| 25 |
you're piping to something that can handle the color codes or not). |
| 26 |
|
| 27 |
> This matters sometimes if I'm doing work at console to unbreak my |
| 28 |
> system and I'm getting an emerge error (not the colors, but the lack |
| 29 |
> of auto-refresh or tailing). |
| 30 |
|
| 31 |
Color's sometimes helpful too, since it provides added visual queues |
| 32 |
so you can process what you're looking at just a hair faster ;) |
| 33 |
|
| 34 |
> Regards, |
| 35 |
> daid |
| 36 |
|
| 37 |
-- |
| 38 |
Poison [BLX] |
| 39 |
Joshua M. Murphy |
Archives