>>>> "Jan" == Jan Rychter
Jan> BTW, it's a marvellously useful piece of code, perhaps worth
Jan> integrating as a package. Not very actively developed, but
Jan> works just fine.
Being package maintainer is pretty minimal. Say you want to do it,
take a hack at copying the relevant stuff from another package (see
also the Packages and Packaging nodes in the User's Manual and the
Lisp Reference), and when you get stuck ask for help. After the
initial investment of a couple of hours, an inactive package requires
no effort you wouldn't make any way. After that, Norbert Koch takes
care of most of the work of getting it distributed, with occasional
consultation if it's not clear how a generic change applies to your
Only problem is that packagized libraries have a habit of becoming
more actively developed as people become aware they exist. ;-) Of
course, if you're smooth, you can use my sales pitch and pass on the
work to one of the newbies!
Jan> You mean I should just write the resizing code in Lisp and
Jan> it'll work better? Hmm.
Up to you. I'll make no promises, but Mike Sperber might be willing
to buy you a beer if you report your success :-) here. Do report
failures too, of course.
Warning: initial frame is special (gets created before init.el is
run). So some things can be done more smoothly using X resources. If
they can't be done at all from Lisp, that's a bug.
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.