help with bbrb-0.2.1 and imlib
I am trying to install bbrb-0.2.1 (the background changer for BlackBox).
However, as I try to configure it for installation ("./configure") I get
a message stating that my imlib verion is lower than 1.9.8. However, I
just installed the source version of imlib 1.9.10, and imlib-config can
be located at /usr/local/bin/imlib-config.
Is there any work around for this?
BTW, the message I get at the end of the "./configure" command is the
following:
checking for imlib-config... no
checking for IMLIB - version >= 1.9.8... no
*** The imlib-config script installed by IMLIB could not be found
*** If IMLIB was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the IMLIB_CONFIG environment variable to the
*** full path to imlib-config.
Thanks for any advice. :)
- Andres Montiel
Re: help with bbrb-0.2.1 and imlib
* Andres Montiel <[EMAIL PROTECTED]> [Nov 15. 2001 15:23]:
> I am trying to install bbrb-0.2.1 (the background changer for BlackBox).
> However, as I try to configure it for installation ("./configure") I get
> a message stating that my imlib verion is lower than 1.9.8. However, I
> just installed the source version of imlib 1.9.10, and imlib-config can
> be located at /usr/local/bin/imlib-config.
Is /usr/local/bin in the PATH?
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogic, with just a little bit more effort."
-- A. P. J.
bbkeys configuration [was: Re: iconized bbkeys]
> Date: Tue, 13 Nov 2001 16:29:13 +0100 > From: Roman Neuhauser <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: iconized bbkeys > > Hi there, > > bbkeys-0.3.6 started from .xinitrc with "bbkeys -i &" doesn't capture the > keypresses. Is there a way to make it work without cluttering the desktop? > > Or rather, since I just realized that the current version is 0.8.3, is this > fixed in the newer versions? To answer my own question, and so that it's archived: the keymap file (.bbkeysrc) is not the same as the style file (bbtools/bbkeys.bb). Looks like the -c switch is meant for the latter one, and bbkeys doesn't respond to any mapped keypresses if you point it at .bbkeysrc with -c. This leads me to a question or two: could the location of .bbkeysrc be made configurable? I don't really like to have to wade thru dozens of rc files in my ~. Patching bbkeys to look for the file seems to be truly trivial (I found two places where the file is referenced in the source, and one of those was in bbkeysconf IIRC), but I'd like to see this accepted in the source. Would such a change be welcome? If so, I can try to come up with a patch. There is one glitch I can see: currently, bbkeysconf and the like don't have to look where the actual keymap file resides: it's hardcoded as ~/.bbkeysrc. This could be solved like this: the path to the keymap file would be specified in the style file, and bbkeysconf would look for it there. If the style file doesn't contain the directive, just dump it to the standard place. Which (I said I don't like having my ~ cluttered with lots of dotfiles) would be really sweet to change to a patch in ~/.blackbox. I switched to BB from AfterStep, and I'm so happy you wouldn't believe it. But BB has one disadvantage compared to AS: the AS config files all live in a tree rooted in one directory in my ~. Sweet. (Other than that, the AS configuration is an atrocity, but that's another story.) To sum this up: thank you for BB to everyone involved in the development, and please, try to centralize the location of the rc files. Oh, the bbkeys docs are full of stuff like "the other config file". As you might have noticed, changing the terminology to "keymap file" and "style file" could help get rid of this confusion. -- FreeBSD 4.4-STABLE 7:47PM up 23 days, 6:30, 8 users, load averages: 0.07, 0.04, 0.03
Re: bbkeys configuration [was: Re: iconized bbkeys]
* Roman Neuhauser ([EMAIL PROTECTED]) wrote: > To answer my own question, and so that it's archived: > the keymap file (.bbkeysrc) is not the same as the style file > (bbtools/bbkeys.bb). Looks like the -c switch is meant for the latter > one, and bbkeys doesn't respond to any mapped keypresses if you point > it at .bbkeysrc with -c. A few days ago I created just such a patch, and should be in the mailing list archives by now. It has been accepted for inclusion in the next release of bbkeys which, from what I hear, should happen any day now. If you can't wait, it's in the CVS tree, which seems to be pretty stable right now, so feel free to grab the newest tree. > There is one glitch I can see: currently, bbkeysconf and the like don't > have to look where the actual keymap file resides: it's hardcoded as > ~/.bbkeysrc. This could be solved like this: the path to the keymap file > would be specified in the style file, and bbkeysconf would look for it > there. If the style file doesn't contain the directive, just dump it > to the standard place. vanRijn, the author of bbkeys, told me he was in the process of changing that. However, I don't think it will be changed in bbkeysconf. I think that configurator has been superceded by bbconf; look for the changes there. > Oh, the bbkeys docs are full of stuff like "the other config file". As > you might have noticed, changing the terminology to "keymap file" and > "style file" could help get rid of this confusion. This, perhaps, is the reason why the newest release of bbkeys hasn't hit the press yet. Feel free to modify the docs if you like, and submit the changes. I'm sure every developer would like to see the contribution of documentation. :) scott -- Copyleft (c) 2001, Scott Moynes msg03818/pgp0.pgp Description: PGP signature
Re: bbkeys configuration [was: Re: iconized bbkeys]
On Thursday 15 November 2001 14:36, Scott Moynes wrote:
> * Roman Neuhauser ([EMAIL PROTECTED]) wrote:
> > To answer my own question, and so that it's archived:
> > the keymap file (.bbkeysrc) is not the same as the style file
> > (bbtools/bbkeys.bb). Looks like the -c switch is meant for the latter
> > one, and bbkeys doesn't respond to any mapped keypresses if you point
> > it at .bbkeysrc with -c.
>
> A few days ago I created just such a patch, and should be in the
> mailing list archives by now. It has been accepted for inclusion in
> the next release of bbkeys which, from what I hear, should happen any
> day now. If you can't wait, it's in the CVS tree, which seems to be
> pretty stable right now, so feel free to grab the newest tree.
As Scott said above, this has been included in bbkeys-0.8.4. BBkeys will now
allow command-line configurability of where its look-and-feel config file
comes from as well as where its keybindings config file comes from. I'm not
quite done with what I want in there for 0.8.4 yet, so if you're so inclined,
please pull bbkeys down from CVS and give it a whirl. One thing to be
noted, though, is that this will most probably cause some issues down the
road when blackbox has rudimentary keybindings built into it, as blackbox
proper will by default look in ~/.bbkeysrc for its own limited keybindings.
>
> > There is one glitch I can see: currently, bbkeysconf and the like
> > don't have to look where the actual keymap file resides: it's hardcoded
> > as ~/.bbkeysrc. This could be solved like this: the path to the keymap
> > file would be specified in the style file, and bbkeysconf would look for
> > it there. If the style file doesn't contain the directive, just dump it
> > to the standard place.
>
> vanRijn, the author of bbkeys, told me he was in the process of
> changing that. However, I don't think it will be changed in
> bbkeysconf. I think that configurator has been superceded by bbconf;
> look for the changes there.
Um. There's no way I want to even think about putting bbkeys.conffile: into
style files. bbkeys will look for its keybindings in two places: either you
tell it otherwise in the command line with "-rc " or it looks in
~/.bbkeysrc. Either way, if it can't open it, you'll hear about it in
STDERR.
Also, bbkeysconf (the QT bbkeys-only configurator) has been dropped from my
list of things I care about. It's dead. So is bbkeysConfigGtk. So is
bbkeysConfigC, thank God. Going forward from the 0.8.4 release of bbkeys,
bbkeys will have a very nifty perl script (correctly auto-detected of
course), thanks to Damien Tougas, that does a MUCH better job of
interactively configuring your bbkeys file. And the bbconf plugin for
blackbox keybindings will also be kept up-to-date with these changes as well.
And you're right--bbkeysconf.pl and bbconf will have to have some smarts
added for "open another file" and "save as" for its settings.
>
> > Oh, the bbkeys docs are full of stuff like "the other config file".
> > As you might have noticed, changing the terminology to "keymap file" and
> > "style file" could help get rid of this confusion.
>
> This, perhaps, is the reason why the newest release of bbkeys hasn't
> hit the press yet. Feel free to modify the docs if you like, and
> submit the changes. I'm sure every developer would like to see the
> contribution of documentation. :)
>
> scott
Actually, it's other reasons, but by ALL means, I'd love patches to the
man-pages and documentation. Hell, just send me the new files and I'll pull
them in, most probably.
--
%<--%<
Jason Kasper (vanRijn)
bash$ :(){ :|:&};:
Numbers 6:24-26
Re: bbkeys configuration [was: Re: iconized bbkeys]
> From: Jason vanRijn Kasper <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: bbkeys configuration [was: Re: iconized bbkeys] > Date: Thu, 15 Nov 2001 16:20:27 -0500 > > On Thursday 15 November 2001 14:36, Scott Moynes wrote: > > * Roman Neuhauser ([EMAIL PROTECTED]) wrote: > > > To answer my own question, and so that it's archived: > > > the keymap file (.bbkeysrc) is not the same as the style file > > > (bbtools/bbkeys.bb). Looks like the -c switch is meant for the latter > > > one, and bbkeys doesn't respond to any mapped keypresses if you point > > > it at .bbkeysrc with -c. > > > > A few days ago I created just such a patch, and should be in the > > mailing list archives by now. It has been accepted for inclusion in > > the next release of bbkeys which, from what I hear, should happen any > > day now. If you can't wait, it's in the CVS tree, which seems to be > > pretty stable right now, so feel free to grab the newest tree. > > As Scott said above, this has been included in bbkeys-0.8.4. BBkeys will now > allow command-line configurability of where its look-and-feel config file > comes from as well as where its keybindings config file comes from. I'm not > quite done with what I want in there for 0.8.4 yet, so if you're so inclined, > please pull bbkeys down from CVS and give it a whirl. One thing to be > noted, though, is that this will most probably cause some issues down the > road when blackbox has rudimentary keybindings built into it, as blackbox > proper will by default look in ~/.bbkeysrc for its own limited keybindings. As I'm really new to this list (have been lurking for a week or so, but not paying much attention), why should BB have its own keybindings, when bbkeys does the job so well? > > > There is one glitch I can see: currently, bbkeysconf and the like > > > don't have to look where the actual keymap file resides: it's hardcoded > > > as ~/.bbkeysrc. This could be solved like this: the path to the keymap > > > file would be specified in the style file, and bbkeysconf would look for > > > it there. If the style file doesn't contain the directive, just dump it > > > to the standard place. > > > > vanRijn, the author of bbkeys, told me he was in the process of > > changing that. However, I don't think it will be changed in > > bbkeysconf. I think that configurator has been superceded by bbconf; > > look for the changes there. > > Um. There's no way I want to even think about putting bbkeys.conffile: into > style files. bbkeys will look for its keybindings in two places: either you > tell it otherwise in the command line with "-rc " or it looks in > ~/.bbkeysrc. Either way, if it can't open it, you'll hear about it in > STDERR. Ok. I was just concerned about other tools (bbconf) editing the wrong file. If this is not an issue, I'm fine with the commandline switch. > Also, bbkeysconf (the QT bbkeys-only configurator) has been dropped from my > list of things I care about. It's dead. So is bbkeysConfigGtk. So is > bbkeysConfigC, thank God. Going forward from the 0.8.4 release of bbkeys, > bbkeys will have a very nifty perl script (correctly auto-detected of > course), thanks to Damien Tougas, that does a MUCH better job of > interactively configuring your bbkeys file. And the bbconf plugin for > blackbox keybindings will also be kept up-to-date with these changes as well. > And you're right--bbkeysconf.pl and bbconf will have to have some smarts > added for "open another file" and "save as" for its settings. Can't wait to see this happen. :) > > > Oh, the bbkeys docs are full of stuff like "the other config file". > > > As you might have noticed, changing the terminology to "keymap file" and > > > "style file" could help get rid of this confusion. > > > > This, perhaps, is the reason why the newest release of bbkeys hasn't > > hit the press yet. Feel free to modify the docs if you like, and > > submit the changes. I'm sure every developer would like to see the > > contribution of documentation. :) > > > > scott > > Actually, it's other reasons, but by ALL means, I'd love patches to the > man-pages and documentation. Hell, just send me the new files and I'll pull > them in, most probably. I just did. :) -- FreeBSD 4.4-STABLE 10:39PM up 23 days, 9:22, 10 users, load averages: 0.09, 0.07, 0.01
Re: bbtools
tp40 <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm having troubles with bbtools ... bbtime, bbdate, and bbweather all > ignore configuration files and show up as little black rectangles with > black text that is impossible to see. I have no idea what's going on > ... it's probably some lib that has to be updated or something ... any > ideas? bbweather currently doesn't support a different config-file than the default (my bad, I will change this when I find the time). The others, IIRC, provide a switch to load an alternate file. How's your root-menu? If you can read that fine, the other bbtools should work as well, as they read the same file (don't they?). -Jan
Re: bbtools
everything else works fine, just not bbtools ... and not all of them, just bbtime, bdate, and bbweather. bbsload and bbrun work just fine. the ones that display text just have a black background and black text over it ... this is starange. On Thu, 15 Nov 2001, Jan Schaumann wrote: > tp40 <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > I'm having troubles with bbtools ... bbtime, bbdate, and bbweather all > > ignore configuration files and show up as little black rectangles with > > black text that is impossible to see. I have no idea what's going on > > ... it's probably some lib that has to be updated or something ... any > > ideas? > > bbweather currently doesn't support a different config-file than the > default (my bad, I will change this when I find the time). The others, > IIRC, provide a switch to load an alternate file. > > How's your root-menu? If you can read that fine, the other bbtools > should work as well, as they read the same file (don't they?). > > -Jan > Timofei Piatenko [EMAIL PROTECTED]
Re: help with bbrb-0.2.1 and imlib
Do you mean "/.configure --prefix=/usr/local/bin" ? (I'm a bit new to Linux)
- Andres Montiel
Mads Martin Joergensen wrote:
> * Andres Montiel <[EMAIL PROTECTED]> [Nov 15. 2001 15:23]:
>
>> I am trying to install bbrb-0.2.1 (the background changer for BlackBox).
>> However, as I try to configure it for installation ("./configure") I get
>> a message stating that my imlib verion is lower than 1.9.8. However, I
>> just installed the source version of imlib 1.9.10, and imlib-config can
>> be located at /usr/local/bin/imlib-config.
>
>
> Is /usr/local/bin in the PATH?
>
size of application window
I need a bit of help. I installed Linux Commander and plan to use it as
my graphical file manager. However, everytime I open it, it opens as a
1024 x 780 application. My monitor (laptop lcd) has a maximum resolution
of 800 x 600.
Is it possible to have Linux Commander open as a 800 x 600 window?
I tried "[exec] (File Manager) {linuxcmd -geom 40x94+1+382 &}" (just a
wild guess) but it didn't work.
- Andres Montiel
Re: size of application window
On 16-Nov-2001 Andres Montiel wrote:
> I need a bit of help. I installed Linux Commander and plan to use it as
> my graphical file manager. However, everytime I open it, it opens as a
> 1024 x 780 application. My monitor (laptop lcd) has a maximum resolution
> of 800 x 600.
>
> Is it possible to have Linux Commander open as a 800 x 600 window?
>
> I tried "[exec] (File Manager) {linuxcmd -geom 40x94+1+382 &}" (just a
> wild guess) but it didn't work.
>
> - Andres Montiel
A VERY quick reading of the source shows that it seems to ignore any command
line options other than the ones gtk_init() itself deals with. My guess is
somewhere in the code the author specifies how big the window should be.
