| 1 |
On 14/04/2013 12:52, Tom Wijsman wrote: |
| 2 |
> If people don't agree with this apporach, we may want to solve the |
| 3 |
> actual problem in a different manner; one could write `eselect elog` |
| 4 |
> just like we have `eselect news`, that would force them to process |
| 5 |
> through the log messages and just not simply ignore them. Listing that |
| 6 |
> there are unread elog messages upon the next emerge may be interesting. |
| 7 |
|
| 8 |
Speaking as a long time Gentoo user: |
| 9 |
|
| 10 |
I like this idea of displaying an elog summary reminder at the end of |
| 11 |
emerge. It's analogous to the preserved-rebuild, blocker, and failed |
| 12 |
emerge notices that are already there. There are insanely useful - |
| 13 |
emerge inside screen, reconnect later and just know the important stuff |
| 14 |
I need to tend to is right there on the screen. |
| 15 |
|
| 16 |
If possible I'd like to see categories of messages; some are pointless |
| 17 |
to me now like the mention of the kernel upgraded guide after installing |
| 18 |
kernel sources. I'd like to filter those out whilst keeping important |
| 19 |
stuff in (like all the recent udev spam) |
| 20 |
|
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Alan McKinnon |
| 25 |
alan.mckinnon@×××××.com |
Archives