Re: [eloli@hotmail.com: Blackbox web site]
> Date: Mon, 22 Jul 2002 13:05:43 -0400 > From: Jan Schaumann <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: [[EMAIL PROTECTED]: Blackbox web site] > > "Mr. Brigham Young" <[EMAIL PROTECTED]> wrote: > > Originally I understood the use of "Un*x" was to protect against > > lawsuits from AT&T during the great BSD Freedom wars. > > Yes; and IIRC "UNIX" (ie all upper-case) is still a trademark of > AT&T/Bell Labs, no? no, it belongs to The Open Group (http://www.opengroup.org/) -- FreeBSD 4.6-STABLE 12:01PM up 6 days, 22:20, 10 users, load averages: 0.12, 0.08, 0.03
Re: "Emulating" a right-click on the root window
> Subject: Re: "Emulating" a right-click on the root window > Date: Mon, 15 Jul 2002 10:55:59 -0400 > From: Roy Wood <[EMAIL PROTECTED]> > To: "blackbox" <[EMAIL PROTECTED]> > > >Is there anyway to send an event/atom/whatever to the > >root window to say "hey buddy, someone right-clicked > >on you, handle it" ?? > > I've done just that by patching bbkeys. I'm getting the patch ready to > submit to the bbkeys folks, but here's the basic idea: > > > I added the following actions to bbkeys: > > MouseUp - move cursor up > MouseDown - move cursor down > MouseLeft - move cursor left > MouseRight - move cursor right > > MouseButton1 - send button 1 click to front window > MouseButton2 - send button 2 click to front window > MouseButton3 - send button 3 click to front window > > RootMouseButton1 - send button 1 click to root window > RootMouseButton2 - send button 1 click to root window > RootMouseButton3 - send button 1 click to root window unfortunately (with respect to the root menu navigation w/ keyboard) this is more of a hack than a solution. two reasons: 1) you typically won't want to send "i've just clicked the lmb", but "show me the menu". for this to work, blackbox would have to have keybindings, which is not the case... kinda chicken and egg. 2) moving the cursor like that is probably useful if you're forced to work on a laptop, but is completely unusable (imo) for menu navigation. i've used such an emulation in menus once, and it was major pain. preferrable behavior (skip to the next/prev item / open/close submenu) would require keybindings. don't take me wrong, i'd myself love to be able to open the menu with a keypress, and navigate it with hjkl... > The only annoying bit is mouse movement-- particularly how far to move > the mouse for each keystroke. I actually made that a parameter in the > .bbkeysrc file, though it is not very elegant (you cannot currently set > different movement amounts for different keybindings, so you cannot have > alt-KP_8 move the mouse up 20 pixels and KP_8 move it up 10 pixels). -- FreeBSD 4.6-STABLE 5:01PM up 2 days, 7:15, 2 users, load averages: 0.00, 0.02, 0.00
Re: [bbkeys] X error: BadWindow
> Date: Mon, 15 Jul 2002 11:44:31 +0200 > From: Roman Neuhauser <[EMAIL PROTECTED]> > To: blackbox <[EMAIL PROTECTED]> > Subject: [bbkeys] X error: BadWindow > > blackbox-0.65.0beta2 > bbkeys-HEAD I forgot to mention the ./configure lines: blackbox: ./configure \ --prefix=/home/roman/blackbox-0.65.0beta2/ \ --enable-debug \ --disable-nls bbkeys: ./configure \ --prefix=/home/roman/blackbox-0.65.0beta2/ \ --enable-debug \ --disable-nls btw would be nice if both apps created config.nice files -- FreeBSD 4.6-STABLE 12:01PM up 2 days, 2:16, 2 users, load averages: 0.05, 0.01, 0.00
[bbkeys] X error: BadWindow
blackbox-0.65.0beta2 bbkeys-HEAD :r .xinitrc cd xmodmap ~/.xmodmaprc & /home/roman/blackbox-0.65.0beta2/bin/bbkeys -i -c ~/.blackbox/bbkeys & exec /home/roman/blackbox-0.65.0beta2/bin/blackbox -rc ~/.blackbox/blackboxrc :r blackbox.log XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 4.5 i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Mon Jul 15 11:42:32 2002 (==) Using config file: "/etc/X11/XF86Config" Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! loaded ->36<- instructions. Could not open blackbox style file Could not open config file: /home/roman/.blackbox/bbkeys BScreen::BScreen: managing screen 0 using visual 0x21, depth 16 Blackbox::process_event(): MapRequest for 0x8e BlackboxWindow::BlackboxWindow(): creating 0x8e /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 12/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 12/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 12/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 12/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 2/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/blackbox-0.65.0beta2/bin/blackbox: X error: BadWindow (invalid Window parameter)(3) opcodes 29/0 resource 0x0 /home/roman/black
Re: grouping windows
> Date: Mon, 15 Jul 2002 01:49:56 -0700 (PDT) > From: "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: grouping windows > My stance may cost this project a few users. But then again, leaving > out pixmap support for the widgets loses us users too. Every choice > is a balancing act. In the end it is about what Brad and I want and > are willing to code and support. Please, do not bring up plugins > around him, please (-: His day job at Trolltech has forced him to > code support for plugins in Qt. On the subject he has many comments > not all of them fit for typing. > > Plugins are nifty, they solve some problems. However that is not what > Blackbox is all about. > > At the same time do not take my comments to mean we are ignoring user > requests. Much of the work over the last 8 months has been user > driven and this will continue. We are just willing to say no now and > then. given that i started this thread i think it's time for me to apologize for doing so. :) grouping windows wasn't probably such a good idea (and i did *not* mean tabbing, for god's sake!), but i just don't understand why every (seemingly) simple enhancement idea swiftly ends in discussions where most people seem to agree that all we need as another kde/gnome nonsense. ugh. -- FreeBSD 4.6-STABLE 10:53AM up 2 days, 1:07, 2 users, load averages: 0.03, 0.01, 0.00
Re: new NETWM key grabber
> Date: Mon, 15 Jul 2002 02:14:20 +0200 > From: Roman Neuhauser <[EMAIL PROTECTED]> > To: blackbox <[EMAIL PROTECTED]> > Subject: Re: new NETWM key grabber > > > Date: Sun, 14 Jul 2002 19:49:44 -0400 > > From: Scott Furt <[EMAIL PROTECTED]> > > To: blackbox <[EMAIL PROTECTED]> > > Subject: Re: new NETWM key grabber > > > > Es Bee Ex wrote: > > >It would be less painful if, instead of having to switch between modes > > >like vi, you could use a single key combo to enter COMMAND mode, and as > > >soon as you do something in COMMAND mode, it returns automatically to > > >INSERT mode. > > > > IIRC, CTL+O in vi will let the user enter one command, > > then revert back to insert mode. > > YRC (you remember correctly) actually, no. that's just vim (which is what many lunix distros call vi) -- FreeBSD 4.6-STABLE 2:18AM up 1 day, 16:32, 10 users, load averages: 0.16, 0.12, 0.29
Re: new NETWM key grabber
> Date: Sun, 14 Jul 2002 19:49:44 -0400 > From: Scott Furt <[EMAIL PROTECTED]> > To: blackbox <[EMAIL PROTECTED]> > Subject: Re: new NETWM key grabber > > Es Bee Ex wrote: > >It would be less painful if, instead of having to switch between modes > >like vi, you could use a single key combo to enter COMMAND mode, and as > >soon as you do something in COMMAND mode, it returns automatically to > >INSERT mode. > > IIRC, CTL+O in vi will let the user enter one command, > then revert back to insert mode. YRC (you remember correctly) -- FreeBSD 4.6-STABLE 2:13AM up 1 day, 16:28, 10 users, load averages: 0.24, 0.17, 0.39
grouping windows
Sorry if this is a complete nonsense, but is it possible now / after some coding to have blackbox treat several windows as one? It would've saved me a few seconds (and writing this email :) right now if I could somehow move several windows across the screen at once. -- FreeBSD 4.6-STABLE 12:40PM up 2:55, 6 users, load averages: 0.10, 0.06, 0.02
Re: new NETWM key grabber
> From: Robert <[EMAIL PROTECTED]> > Date: Sat, 13 Jul 2002 08:45:01 +0100 > To: [EMAIL PROTECTED] > Subject: Re: new NETWM key grabber > > On Sat, 13 Jul 2002, [EMAIL PROTECTED] wrote: > > On Wed, Jul 10, 2002 at 10:16:18PM -0500, Ben Jansens wrote: > >> Do you use the window list cycling currently found in bbkeys? > > > > Yes > > As a counterbalance to all the yes'es, I don't, I use > Prev/NextWorkspace a lot and tend to keep a window a workspace I do use the alt-tab magic, and also the Mod4-tab magic (cycling workspaces). What I miss from it is the same behavior window cycling has: switching the order of the two topmost workspaces on the stack. -- FreeBSD 4.6-STABLE 10:20AM up 34 mins, 6 users, load averages: 0.00, 0.00, 0.00
changes in 0.65
Hi there, sorry if I'm going to ask questions already answered on the list (or elsewhere), I wasn't subscribed for ~.5y, and searching the ML archive didn't turn up anything relevant. I was running 0.62.1pre0 for quite some time. I've switched to 0.65.0beta1 yesterday. What bothers me is that there seems to be a change in the bbpager I can't get rid of. I have this config: BottomToTop/LeftToRight/RowSmartPlacement, bbpager.position: +80--1 bbpager.rows: 1 bbpager.raised: True bbpager.bevelWidth: 1 bbpager.desktop.width: 21 bbpager.desktop.height: 17 This used to give me the first window on a desktop at the bottom left corner of the screen, just above bbpager and toolbar. But in the beta1, the window is placed with it's bottom left corner just right from bbpager, this happens *on the first workspace only*. Looks like the bbpager window has a 1px border on the 1st wspace or what. Is this something I can remedy in my config/style files? Now, one thing that has been discussed quite some time ago: what are the plans for the "don't want focus. never" window property? cursor over the window-list window still prevents switching windows with bbkeys, and bbpager still shows up in the window list on the firts workspace. Anyway, thanks everyone for this great piece of software! -- FreeBSD 4.6-STABLE 9:00AM up 4 days, 6 hrs, 12 users, load averages: 1.12, 1.11, 0.96
Re: slit functionality...
> From: Kevin Geiss <[EMAIL PROTECTED]> > Date: Thu, 4 Apr 2002 22:01:59 -0700 > To: [EMAIL PROTECTED] > Subject: Re: slit functionality... > > check out xtoolwait! where can we get it? -- FreeBSD 4.4-STABLE 10:50AM up 11 days, 17:35, 31 users, load averages: 0.12, 0.06, 0.02
Re: goofy blackbox/bbkeys interaction
> Date: Wed, 27 Feb 2002 04:03:02 -0800 > From: David Terrell <[EMAIL PROTECTED]> > To: blackbox <[EMAIL PROTECTED]> > Subject: Re: goofy blackbox/bbkeys interaction > > On Wed, Feb 27, 2002 at 11:30:26AM +0100, Roman Neuhauser wrote: > > > Date: Tue, 26 Feb 2002 14:19:45 -0800 > > > From: David Terrell <[EMAIL PROTECTED]> > > > To: blackbox <[EMAIL PROTECTED]> > > > Subject: goofy blackbox/bbkeys interaction > > > > > > I have focusNewWindows set to true and focusLastWindow set to False. > > > (I don't know if these settings are germane to my problem...) When > > > I alt-tab in bbkeys and the window list popup happens to be under > > > the mouse cursor, focus always ends up in the window where the mouse > > > cursor is after I release alt, regardless of where I alt-tabbed to. > > > > A known problem. > > Any plans for a workaround? ISTR there *is* a workaround: you can turn the menu off IIRC. I don't remember the "command" (if there is actually one: hallucinating cannot be ruled out). -- FreeBSD 4.4-STABLE 1:29PM up 5 days, 19:54, 14 users, load averages: 0.10, 0.11, 0.06
Re: goofy blackbox/bbkeys interaction
> Date: Tue, 26 Feb 2002 14:19:45 -0800 > From: David Terrell <[EMAIL PROTECTED]> > To: blackbox <[EMAIL PROTECTED]> > Subject: goofy blackbox/bbkeys interaction > > I have focusNewWindows set to true and focusLastWindow set to False. > (I don't know if these settings are germane to my problem...) When > I alt-tab in bbkeys and the window list popup happens to be under > the mouse cursor, focus always ends up in the window where the mouse > cursor is after I release alt, regardless of where I alt-tabbed to. A known problem. -- FreeBSD 4.4-STABLE 11:30AM up 5 days, 17:55, 16 users, load averages: 0.13, 0.07, 0.01
Re: cvs on sf.net
> Date: Thu, 7 Feb 2002 20:35:27 +0100 > From: Mads Martin J?rgensen <[EMAIL PROTECTED]> > To: "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> > Cc: David Terrell <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > Subject: Re: cvs on sf.net > > * Sean 'Shaleh' Perry <[EMAIL PROTECTED]> [Feb 07. 2002 20:24]: > > > Are you planning on letting other people commit to the cvs tree > > > on sf directly? > > > > not really. why? what benefit does this arrangement bring to the BB community? > > Blackbox has never been in CVS before. so? > > I use CVS as a safe database for code storage. If something bad > > happens, I can always find the releases there. Granted, this is not > > a common usage in the open source community. But this is not a > > distributed project with 10s or 100s of contributors. how is this related? even a one-man-show project benefits from a versioning system. > Lets keep this like the kernel. One guy gets all the patches, and > decides what goes in or not. I like the BSD way. > If you write good code for the project, does it then matter if you > send the patches to him or put them directly in CVS anyway? yes, it does. I, as someone who has a potential patch might want to have access to the latest-and-greatest code. I don't have that today. I might want to submit improvements to the BB documentation. I can't do it today. It wouldn't clash with the code 90% of time, but I'd still have to bother Sean with any patches I might have: because there's no repository of the code. -- FreeBSD 4.4-STABLE 9:53PM up 18 days, 4:16, 15 users, load averages: 0.11, 0.03, 0.01
Re: bb and transient windows
> Date: Wed, 6 Feb 2002 21:05:22 -0500 > From: Jan Schaumann <[EMAIL PROTECTED]> > To: E-mail <[EMAIL PROTECTED]> > Subject: Re: bb and transient windows > > Sean 'Shaleh' Perry <[EMAIL PROTECTED]> wrote: > > Personally, I would rather people use the tarballs I release. > > Frankly the need to download code just because it is new has never > > made sense to me. Yesterday CVS did not even compile. > > If it doesn't, the people checking it out might actually make it work. > If somebody wants to stay up to date, a system like CVS (or 'arch' or > 'subversion') only makes sense to me. CVS can *save* you time and energy. Like the patch for bbkeys I sent to the list a few days ago: since Jason uses CVS, I could easily check whether the bug is still there, and send a diff against uptodate code. Not that it would matter in this case (the patch was a oneliner, and in a stable piece of code), but these two virtues of CVS are very much apreciated. -- FreeBSD 4.4-STABLE 11:49AM up 17 days, 18:13, 11 users, load averages: 1.04, 0.97, 0.59
Re: bb and transient windows
> Date: Wed, 6 Feb 2002 17:46:41 -0500 > From: Jan Schaumann <[EMAIL PROTECTED]> > To: "BlackBox (E-mail)" <[EMAIL PROTECTED]> > Subject: Re: bb and transient windows > > Sean 'Shaleh' Perry <[EMAIL PROTECTED]> wrote: > > > > > > Um. I don't see why you would discourage help so quickly. At very least > > > more people means more eyes and more ideas. Heck, even having people > > > bug testing, trying to break things, can only help. > > > > > > > I have always released pre releases whenever they would compile. This will > > continue. Umm, why did you say you don't use CVS? -- FreeBSD 4.4-STABLE 12:21AM up 17 days, 6:45, 11 users, load averages: 0.01, 0.02, 0.00
Re: bb and transient windows
> Date: Wed, 06 Feb 2002 13:15:15 -0800 (PST) > From: "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> > To: "Asviyan, Anatoly" <[EMAIL PROTECTED]> > Subject: RE: bb and transient windows > Cc: "BlackBox (E-mail)" <[EMAIL PROTECTED]> > > On 05-Feb-2002 Asviyan, Anatoly wrote: > >> From: Sean 'Shaleh' Perry [mailto:[EMAIL PROTECTED]] > >> The team is working on getting NET WM support in blackbox > > I'd like to help with it. how can I join? who is team/work > > coordinator? > > We do not require help, just time. The issue is we have to redesign > the guts of blackbox in a few places. More people will not help this. > Thanks though. Sean, are you sure you want to fend off other people from any stage of the development of blackbox? -- FreeBSD 4.4-STABLE 11:02PM up 17 days, 5:26, 11 users, load averages: 0.01, 0.03, 0.00
Re: program launching method mismatch in blackbox and bbkeys
> Date: Tue, 05 Feb 2002 16:11:04 -0500
> From: Kyle Donaldson <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: program launching method mismatch in blackbox and bbkeys
>
> On Tue, 5 Feb 2002, Roman Neuhauser wrote:
> > blackbox spawns programs (from the root menu) via execl(), while bbkeys
> > uses execve() (or vice versa, don't remember). this leads to, on both of
> > my machines at least, terminals with different characteristics (see
> > below). could you guys agree on a program launching method that will
> > allow the terminals to to be the same? TIA.
> >
>
> Unless you're on some system where execl() and execve() are unrelated,
> execl() calls execve() to do the work. Therefore, there should be no
> difference when the same program is launched by both calls.
>
> Are you sure that they are under the *exact* same configuration? One slight
> change could throw it off completely.
Yes, I'm sure. If it's not the functions themselves, then it must be
the way they're used.
.blackbox/menu:
[exec] (rxvt) {rxvt}
.blackbox/bbkeysrc
KeyToGrab(a), WithModifier(Mod4), WithAction(ExecCommand), DoThis(rxvt)
.Xdefaults:
rxvt.termName: rxvt
rxvt.backspacekey:
rxvt.deletekey:
rxvt.scrollBar_right: True
rxvt.background: black
rxvt.foreground: grey70
rxvt.foreground: grey95
rxvt.inheritPixmap: True
rxvt.cursorColor: chocolate
rxvt.saveLines: 500
rxvt.visualBell: True
rxvt.scrollTtyKeypress: True
rxvt.scrollTtyOutput: False
rxvt.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-2
--
FreeBSD 4.4-STABLE
11:40AM up 16 days, 18:04, 9 users, load averages: 0.16, 0.16, 0.08
program launching method mismatch in blackbox and bbkeys
blackbox spawns programs (from the root menu) via execl(), while bbkeys uses execve() (or vice versa, don't remember). this leads to, on both of my machines at least, terminals with different characteristics (see below). could you guys agree on a program launching method that will allow the terminals to to be the same? TIA. rxvt started from the root menu: roman@roman ~ > stty all speed 38400 baud; 24 rows; 80 columns; lflags: icanon isig iexten echo echoe echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff -ixany imaxbel -ignbrk brkint -inpck ignpar -parmrk oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret cflags: cread cs8 -parenb -parodd -hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf discard dsusp eof eol eol2erase erase2 intrkill ^O ^Y ^D^H ^H ^C ^U lnext min quitreprint start status stopsusptime ^V 1 ^\ ^R ^Q ^T ^S ^Z 0 werase ^W rxvt started from bbkeys with KeyToGrab(a), WithModifier(Mod4), WithAction(ExecCommand), DoThis(rxvt) roman@roman ~ > stty all speed 38400 baud; 24 rows; 80 columns; lflags: icanon isig iexten echo echoe echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff -ixany imaxbel -ignbrk brkint -inpck ignpar -parmrk oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret cflags: cread cs8 -parenb -parodd -hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf discard dsusp eof eol eol2erase erase2 intrkill ^O ^Y ^D^? ( ^C ^U lnext min quitreprint start status stopsusptime ^V 1 ^\ ^R ^Q ^G ^S ^Z 0 werase ^W -- FreeBSD 4.4-STABLE 2:47PM up 15 days, 21:11, 9 users, load averages: 0.02, 0.03, 0.00
PATCH - a small bug in option handling
looks like there's a typo in src/main.cc: bitwise OR instead of logical
one.
--
FreeBSD 4.4-STABLE
11:35AM up 15 days, 17:58, 9 users, load averages: 0.00, 0.04, 0.04
Index: src/main.cc
===
RCS file: /cvsroot/bbkeys/bbkeys/src/main.cc,v
retrieving revision 1.3
diff -u -r1.3 main.cc
--- src/main.cc 2002/01/13 18:59:39 1.3
+++ src/main.cc 2002/02/05 10:22:34
@@ -85,7 +85,7 @@
exit(2);
};
options.bbkeysrc=argv[i];
- } else if ((!strcmp(argv[i], "-nobb")) | (!strcmp(argv[i], "-n"))) {
+ } else if ((!strcmp(argv[i], "-nobb")) || (!strcmp(argv[i], "-n"))) {
options.nobb_config = True;
} else if ((!strcmp(argv[i], "-v"))
|| (!strcmp(argv[i], "-version"))) {
Re: website, let's get the decision made
> Date: Sat, 26 Jan 2002 08:28:09 -0800 (PST) > From: "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: website, let's get the decision made > > 1) http://www.planetquake.com/lvl/blackbox > 2) http://www.threadbox.net/blackbox > 3) http://www.threadbox.net/blackbox/lightgfx.html > 4) http://speed.seas.upenn.edu/~rarya/bb2/ > 5) http://speed.seas.upenn.edu/~rarya/bb/index.html > 6) http://furt.com/blackbox Of the available contestants (couldn't get to #4 and #5): 1.-2. place: #1 and #3 5.-6. place: #2 and #6 -- FreeBSD 4.4-STABLE 8:59PM up 6 days, 3:23, 14 users, load averages: 0.01, 0.03, 0.00
Re: OT: Quirky problems on a laptop
> Subject: OT: Quirky problems on a laptop > From: "Jamin W. Collins" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: 16 Jan 2002 12:26:18 -0600 > > My wife has a laptop that does some very strange things. From time to > time, certain programs will refuse to start. However, in many cases a > reboot will correct one or more of the applications. > > Most frequently, Evolution and GKrellM fail to start with a > "Segmentation fault". In some cases Blackbox fails to start (not sure > error), but this is normally corrected by a restart. Anything suspicious in dmesg? What does df say about free space? I've seen various apps do various (nasty) things when the space on /var got all used... Stuff like this is usual suspects, but you haven't mentioned what you *have* tried to identify the problem, so.. > Anyone got any ideas, or places/lists for more information on how to > look into something like this? System information included below. Well, surely looks like a HW-related prob, doesn't it? You could try http://www.memtest86.com/, I've seen it touted on freebsd-questions@ more than once. > PCG-SR7K (http://www.ita.sel.sony.com/products/pc/notebook/pcgsr7k.html) > RH 7.2 > > Blackbox 0.61.1 > Evolution 1.0.1 > GKrellM 1.2.2 -- FreeBSD 4.4-STABLE 7:48PM up 3 days, 23:46, 22 users, load averages: 0.12, 0.09, 0.02
Re: nl_NL@euro can't find catalog.
> Date: Mon, 14 Jan 2002 23:03:04 -0800 (PST) > From: "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> > To: "Jeremy C. Reed" <[EMAIL PROTECTED]> > Subject: Re: nl_NL@euro can't find catalog. > Cc: bb <[EMAIL PROTECTED]> > > On 15-Jan-2002 Jeremy C. Reed wrote: > > On Mon, 14 Jan 2002, Sean 'Shaleh' Perry wrote: > > > >> > Can't blackbox use gettext and *.mo files like may other projects or > >> > would that add too many dependencies? > >> > >> I honestly do not know why Brad chose catgets (foo.m) over gettext > >> (foo.po). I am mailing him to ask. > > > > Maybe because catgets(3) is BSD licensed and comes by default on the BSD > > systems that blackbox was developed on. gettext is GPL'd which by its > > nature takes away some benefits of the BSD license. Yes. Catgets is used probably because of license problems. IANAL, but libintl got LGPL'd only recently (being GPL'd until that), and that means that BB would have to be GPL'd too. I'm glad it was not, because that made me try it. > gcc is gpl'ed, should i not use it to compile blackbox? Well, GPL hasn't been tried yet (not to my knowledge), but it's pretty much possible that all the output of gcc (like the blackbox binary you run) *is* covered by GPL. > My point is not to start a license war, rather to point out that gpl > tools do not affect the output. Just because I use gettext does not > mean I must have a GPL licensed app. That's not true. If the library your application depends on (libintl) is GPL'd, you can only use it in GPL'd applications. If, however, your application *doesn't* depend on that library (like through --without-gettext or something), then you *might* be able to prevent GPL infecting the app. As I said, IANAL. > That is also not to say I intend on switching to gettext. Good. -- FreeBSD 4.4-STABLE 8:35AM up 2 days, 12:32, 17 users, load averages: 0.06, 0.04, 0.00
Re: Blackbox Web Design
> Subject: Re: Blackbox Web Design > From: "Jamin W. Collins" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: 08 Jan 2002 15:09:08 -0600 > > On Tue, 2002-01-08 at 08:39, xOr wrote: > > Well, my vote still holds with http://speed.seas.upenn.edu/~rarya/bb2/ > > It's got, and had my vote from the beginning. Good use of space in all > browsers from what I can see. > > Jamin W. Collins me too -- FreeBSD 4.4-STABLE 10:39AM up 13 days, 21:17, 18 users, load averages: 0.13, 0.07, 0.01
Re: Blackbox Web Design
> Date: Mon, 7 Jan 2002 23:31:50 -0500 > From: Thread <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: Blackbox Web Design > > Man, some browsers just suck. The design rendered beautifully in the > brosers I developed it with, but ie, and apparently others, choked on it > as some folks reported it not being variable width. It was, in fact, > designed to be variable width. > > Should be all good now, though. > > http://www.threadbox.net/blackbox > > Thanks > > -Thread This doesn't look very well IMO. In a 80x24 term the page is divided into three equal-width cols, middle one running much longer than the other two, of course. It's ridiculous amount of wasted space, not to mention that it's not comfortable to read. -- FreeBSD 4.4-STABLE 10:40AM up 12 days, 21:18, 17 users, load averages: 0.11, 0.03, 0.01
Re: Code Commenting
> Date: Sun, 06 Jan 2002 11:11:52 -0800 (PST)
> From: "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]>
> To: "Jamin W. Collins" <[EMAIL PROTECTED]>
> Subject: Re: Code Commenting
> Cc: [EMAIL PROTECTED]
>
> On 06-Jan-2002 Jamin W. Collins wrote:
> > How do you folks feel about someone commenting the BB code?
> >
> > I'm thinking of rather heavy descriptive commenting for every section,
> > to help explain what's being done in each area. Partially for my own
> > understanding but also for future maintenance. I know this somewhat
> > goes hand in hand with the previous list request for a "Blackbox
> > Walkthrough" and most of it could probably be lifted right from the
> > level of comments I'm thinking about. However, I'd like to see the
> > comments in the code.
> >
> > Jamin W. Collins
>
> xOr has done this a bit for the Window.{cc,hh} files. I agree there should be
> more comments. Howevever the code will changing a good deal so anyone who
> spends time now adding proper comments will just see their time wasted.
Well, the code should have been commented right when it was written,
and this should be valid for any new code, even that which isn't
expected to last for very long, since what is written as a temporary
hack to "fix" a bug before it get's fixed correctly may last for
months, or longer.
--
FreeBSD 4.4-STABLE
8:26PM up 11 days, 7:04, 16 users, load averages: 0.10, 0.09, 0.08
Re: website - _basic_ design available
> From: scott <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: website - _basic_ design available > Date: Wed, 2 Jan 2002 10:43:10 -0500 > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thursday 03 January 2002 07:56, Jamin W. Collins wrote: > > I'm no HTML guru, but is there a way that we can combine these two ideas > > to gain the best of both of these? > > > > Jamin W. Collins > > Well, there's no way that i know to get a side nav bar other than tables > or "fancy" DHTML stuff or layers and positioning (and the latter two > would almost definately not work in text-only browsers) > > Is there something wrong with the use of tables on the > http://furt.com/blackbox/ site? Tables are properly handled in 'links', > which i used as my test for a text-only compatible browser, so i figured > that most text-only browsers had learned how to cope with rudimentary > table handling. There's nothing wrong with tables or side menus. But in a 80x24 xterm, the other site uses the space more efficiently IMO. -- FreeBSD 4.4-STABLE 12:38PM up 8 days, 23:16, 17 users, load averages: 0.09, 0.08, 0.03
Re: New epistrophy pre-release
> Date: Fri, 21 Dec 2001 16:02:10 -0500 > From: Scott Moynes <[EMAIL PROTECTED]> > To: blackbox mailing list <[EMAIL PROTECTED]> > Subject: New epistrophy pre-release > > A new version of epistrophy has been uploaded to > http://nexus.carleton.ca/~smoynes/epistrophy.tar.gz > > Notable changes include better signal handling (no more children dying > when you kill epist) and ability to specify the location of the rcfile > on the command line: > # epist /location/to/epistrc > The default is ~/.epistrc > > You can send SIGUSR1 to clear the Atom cache. Currently, SIGHUP does > not reconfigure epistrophy, but it shouldn't be too hard for users > just to restart it. > > Now, when epistrophy starts, it forks to the background. > > I am still working towards a full release with a handful of useful > features, and some better documentation. The most useful feature (or bugfix FMPOV) would be if epistrophy worked with Num_Lock on. Other than that, it looks good. -- FreeBSD 4.4-STABLE 7:26AM up 4 days, 3:56, 6 users, load averages: 0.05, 0.02, 0.00
Re: blackbox pre9
> Date: Wed, 26 Dec 2001 04:06:18 +0100 > From: "joh.n-do" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: blackbox pre9 > > I want to install blackbox 0.80 pre9 > wher is possible to download it? http://www.sf.net/projects/blackboxwm -- FreeBSD 4.4-STABLE 5:06AM up 4 days, 1:36, 5 users, load averages: 0.05, 0.03, 0.01
Re: pre7 uploaded
> Subject: Re: pre7 uploaded > From: "Jamin W. Collins" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: 22 Dec 2001 21:31:57 -0600 > > On Sat, 2001-12-22 at 18:11, Sean 'Shaleh' Perry wrote: > > pre7 is up. Been stable here for a few days. Any issues, please let > > me know. > > Would it be possible to get the installation routine to not overwrite > the "menu" file if it exists, or at least prompt for the overwrite? > I've lost my system-wide custom menu one system a few times when > reinstalling Blackbox. I realize this is my own fault, just a thought. It might be your fault given the warning in the data/README file, but it's nevertheless a badness. Overwriting config files is a no-no. As a side note, you might try setting the immutable flag on the file. chflags(1) on *BSD, chattr(1) on Linux. -- FreeBSD 4.4-STABLE 5:29AM up 1 day, 1:59, 10 users, load averages: 0.00, 0.00, 0.00
Re: pre7 uploaded
> Date: Sat, 22 Dec 2001 16:11:57 -0800 (PST) > From: "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: pre7 uploaded > > pre7 is up. Been stable here for a few days. Any issues, please let > me know. Hi Sean, thanks for your work, but I have a plea: could you append the url? I know there's the archive and all, but it'd be nice. :) -- FreeBSD 4.4-STABLE 2:09AM up 22:39, 8 users, load averages: 0.02, 0.04, 0.00
Re: try it, love it, live it, pound it, tell us what breaks
> Date: Sat, 15 Dec 2001 00:08:40 + > From: David Thor Bragason <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: try it, love it, live it, pound it, tell us what breaks > > Cheers to that! Definitely. BTW, has sf.net stopped counting downloads? The page still shows 0 even though I fetch it about 30 minutes ago. -- FreeBSD 4.4-STABLE 12:20AM up 52 days, 11:03, 13 users, load averages: 0.33, 0.14, 0.07
Re: E-mail clients
> Date: Tue, 11 Dec 2001 11:46:50 -0800 > From: Eric Davis <[EMAIL PROTECTED]> > To: "Jamin W. Collins" <[EMAIL PROTECTED]> > Cc: Blackbox <[EMAIL PROTECTED]> > Subject: Re: E-mail clients > > I've been using mutt and IMAP for well over a year now with > *no* problems. Note that you have to use a development version > (i.e. currently 1.3.23). It really isn't beta... rock solid. 1.3.24, actually. :) -- FreeBSD 4.4-STABLE 9:05PM up 49 days, 7:48, 13 users, load averages: 0.02, 0.04, 0.05
Re: E-mail clients
> Subject: Re: E-mail clients > From: "Jamin W. Collins" <[EMAIL PROTECTED]> > To: Blackbox <[EMAIL PROTECTED]> > Date: 11 Dec 2001 12:12:50 -0600 > > On Tue, 2001-12-11 at 11:43, Jim Knoble wrote: > > You must mean 'telnet'. The user interface isn't spectacular, but it's > > great for command-line users: > > > > telnet imaphost.example.com imap > > > > The commands are standard and are listed in RFC-2060 > > (http://www.faqs.org/rfcs/rfc2060.html). > > > > If you want to use IMAP over SSL, you should probably use the > > SSL-enabled mail client 'stunnel' (http://stunnel.mirt.net/). > > There's always a smart-ass in the bunch somewhere. > > Jamin W. Collins Well, there's always someone who gets offended, but I spent some time ROTFLing after reading that mail. :) -- FreeBSD 4.4-STABLE 7:27PM up 49 days, 6:10, 13 users, load averages: 0.01, 0.06, 0.07
slit keeps reconfiguring to CenterRight Vertical
Hi there, I think this will be a bit long-winded, so accept my apologies... I'm using blackbox-0.61.1 with bbpager-0.3.0. bbpager is started from my .xinitrc. yesterday I looked at the option of having it swallowed by the slit. this turned out to be problematic, as blackbox seems to keep reconfiguring itself to display slit with CenterRight Vertical: whatever values I put in my .blackboxrc, this is what is there after I restart blackbox: session.screen0.slit.placement: CenterRight session.screen0.slit.direction: Vertical Is this a known problem? -- FreeBSD 4.4-STABLE 11:56AM up 28 days, 22:39, 27 users, load averages: 0.00, 0.04, 0.07
Re: bbconf & freebsd
> From: [EMAIL PROTECTED] > Date: Mon, 19 Nov 2001 11:46:20 -0500 > To: [EMAIL PROTECTED] > Subject: Re: bbconf & freebsd > > On 11/19/2001 at 01:16 PM, Roman Neuhauser <[EMAIL PROTECTED]> said: >has > anyone built bbconf on freebsd? I'm no expert on the GNU build tools, >but > it looks to me like the bbconf_LDADD lines in > >bbconf-1.2/bbconf/(Makefile.am|Makefile.in) are hosed: hardcoding those > >libs in beats the purpose of configure. FreeBSD has dlopen() in libc, and > >qt-2.3.1 installed libqt2.so, not libqt.so. This together lead to > >breakage with "cannot find -ldl", although configure correctly found that > >-ldl is not needed for dlopen() to work. Anyone knows how to fix this > >correctly? > > I've been able to build on FreeBSD 4.4-RELEASE without too many problems. > Unless you have a need for Qt 1.4, symlink libqt.so to libqt2.so. (IMHO, > libqt2.so should have been the original library name, because of crap like > this) It will help with other packages that aren't in the massive ports > tree. I have both Qt-1.4 and Qt-2.3.1 in /usr/X11R6. Might as well remove the 1.4, but I was wondering why the Makefile.(am|in) files in bbconf-1.2/bbconf have those libs hardcoded. That IMO beats the purpose of ./configure. > Maybe I should start work on a new set of (autocrap-type) tools that > aleviate these problems. (And it could probably be done in less code than > the autostools.) When the auto(conf|make) files are written correctly, they work just fine. -- FreeBSD 4.4-STABLE 6:27PM up 27 days, 5:10, 13 users, load averages: 0.07, 0.09, 0.12
bbconf & freebsd
Hi there, has anyone built bbconf on freebsd? I'm no expert on the GNU build tools, but it looks to me like the bbconf_LDADD lines in bbconf-1.2/bbconf/(Makefile.am|Makefile.in) are hosed: hardcoding those libs in beats the purpose of configure. FreeBSD has dlopen() in libc, and qt-2.3.1 installed libqt2.so, not libqt.so. This together lead to breakage with "cannot find -ldl", although configure correctly found that -ldl is not needed for dlopen() to work. Anyone knows how to fix this correctly? ./bbconf/Makefile.am:bbconf_LDADD = -ldl -lqt -lXext -lX11 $(LIBSOCKET) ./bbconf/Makefile.in:bbconf_LDADD = -ldl -lqt -lXext -lX11 $(LIBSOCKET) -- FreeBSD 4.4-STABLE 1:09PM up 26 days, 23:52, 9 users, load averages: 0.05, 0.05, 0.05
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
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
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? TIA -- FreeBSD 4.4-STABLE 4:13PM up 21 days, 2:56, 17 users, load averages: 0.20, 0.25, 0.19
