cho...@jtan.com writes: > I vaguely recall coming upon this problem some time back and not > getting anywhere with it. Might it be worth including this information > in the port's readme? > > Matthew > >> > Small issue as I was using stumptray in my config, stumpwm >> > complains about the lack of xembed even after I updated my >> > stumpwm-contrib git folder from where stumpwmtray is loaded. >> >> Yeah, stumpmwm itself doesn't need xembed but contribs are external code >> which >> might need other libraries. The stumptray uses xembed so it needs to be >> loaded >> for it. >> >> You could add following to start of your stumwm init file: >> #-quicklisp >> (let ((quicklisp-init (merge-pathnames "quicklisp/setup.lisp" >> (user-homedir-pathname)))) >> (when (probe-file quicklisp-init) >> (load quicklisp-init))) >> >> (ql:quickload 'xembed) >> >> It should fix the stumptray issue.
I think the modules are pretty well covered by StumpWM documentation (info page / wiki / contrib repo readme). It seems a bit redundant to repeat the same info in pkg readme file. Timo
