> In many ways it is, a user might wish to do things like playing a > specific melody on a bell event, or beep instead of flashing the > screen.
Already possible (or possible with minimal changes - not sure if the feature is accessibel through options right now). How would you play "Hey sokoÅy" on a bell event? Changing the code to add the melody doesn't count. > Maybe adding a mode-line that displays information about the > current VC, adding a way to change events without having to > restart the console, etc etc. An "On Screen Display" which allows information and configuration is something I have always considered from the very start. To bring up more points against using guile here, how would you configure that "on screen display" on a system basis? What about per user? Or running a bit of code on a screen update to show that you have mail? > I have already started playing with it, and it won't add > "significant bunch of code" from the looks. I'd say that the > changes are going to be minimal. It will add libguile, which is significant (up to 500 KB from the looks). I thought you meant code that would be added to the console client, but in this case I will counter that with: but it needs glibc which is about 100MiB from the looks, and all those Hurd libraries, and... Well, you get the idea. _______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
