1 |
* [Dec 12, 2002] Bob Thomas <gtg663h@×××××××××××.edu>: |
2 |
> Gustavo Felisberto wrote: |
3 |
> > |
4 |
> > |
5 |
> > > option in portage to output a beep (char 7) when it is finished |
6 |
> > > with an |
7 |
> > |
8 |
> > |
9 |
> > How about: |
10 |
> > emerge beep |
11 |
> > and then |
12 |
> > emerge whatever; beep -r 2 |
13 |
> > Or a small script that dos it for you? |
14 |
> |
15 |
> Well, if you were going to put something on every line linke that, you |
16 |
> could put emerge whatever; echo -e \\7. I was thinking of something |
17 |
> that wouldn't involve the extra typing, it would just beep when the |
18 |
> emerge finished without having to type something extra every time you |
19 |
> emerged something. In retrospect, it's not a big enough deal to modify |
20 |
> Portage over. |
21 |
|
22 |
You can simulate the effect you're going after with a quick bash |
23 |
function: |
24 |
|
25 |
function emerge { |
26 |
/usr/bin/emerge $@; echo -e \\7 |
27 |
} |
28 |
|
29 |
That way, there's no extra typing needed nor installing other packages, |
30 |
and it works right now. I suppose you could also swap the echo |
31 |
statement with aplay and have it play some kind of compile is finished |
32 |
sound. Seems kind of interesting. |
33 |
|
34 |
-- |
35 |
/* |
36 |
* Bob Phan <bob@××××××××××××××××.net,rphan@××××.com> |
37 |
* Computational Chemistry Informatics |
38 |
* Neurogen Corporation |
39 |
* (203)488-8201 x4645 |
40 |
* |
41 |
* To understand recursion, you must first understand recursion. |
42 |
* http://www.endlessrecursion.net/ |
43 |
*/ |
44 |
|
45 |
-- |
46 |
gentoo-dev@g.o mailing list |