On Sunday 30 January 2011 20:38:15 Eli Barzilay wrote: > Yesterday, Christopher Roy Bratusek wrote: > > On Saturday 29 January 2011 21:44:03 Eli Barzilay wrote: > > > Earlier today, Christopher Roy Bratusek wrote: > > > > SawfishPager from GIT does work with Sawfish GIT. > > > > > > Where is the git repo? -- When I tried the advertised link it didn't > > > work. > > > > The advertised link shows the browsable version -- clone: > > > > git clone git://git.tuxfamily.org/gitroot/sawfishpager/pager.git > > It would be helpful to put this link up at > > http://sawfish.wikia.com/wiki/Download#GIT
... I thought it was ... but no, I'll add it now. > with the other examples. (Especially if tuxfamily is disorganized > enough to have no direct way to tell the above link -- I tried the > obvious of replacing `http' with `git', then I tried looking for git > links at http://tuxfamily.org/sawfishpager/ then > http://tuxfamily.org/.) Tuxfamily stores all info at the Wiki. http://faq.tuxfamily.org/Welcome/En But you're right I'll request that their GIT-Browser does display a clonable link. > > In general, it might be a good idea to make it more accessible through > the wikia page too. Here's the route that I went through: > > * Google search gets me to: > http://sawfish.wikia.com/wiki/Third-party_software > > * That page leads me to: > http://sawfish.wikia.com/wiki/SawfishPager > > * And from there I get to: > http://www.nanolx.org/home/item/60-sawfish-pager I'll update the link. > which isn't working > > * So I go to the top: http://www.nanolx.org/ and look there, getting > me a link to http://www.nanolx.org/newssawfish/sawfishpager which is > not working too. (Actually, looks like nothing there is working > ATM.) Temporary Server-Problem. > * And only then I went to the sawfish page and looked for git links. I'm sorry... when we moved to TF where will be an organized infopage which displays all links at once. > > > > Also the issue with the non- showing windows doesn't occur here. > > > > > > The window does show -- but looking at the code I don't see anything > > > where it waits for the window to appear, so it looks like something > > > that might work on a system that would pop the window up fast enough. > > > In other words, a real bug. > > > > Hmm... With *window* you mean the pager, right? Oh, then I > > missunderstood you. This is a issue related to the > > autohiding-functionality added in 0.90.0 and should be fixed in GIT > > / 0.90.1. > > Yes -- that looks like it's working. > > Also, here's a minor patch to make RPM builds work: > > > diff --git a/sawfish-pager.spec.in b/sawfish-pager.spec.in > index fc577d7..21a89a4 100644 > --- a/sawfish-pager.spec.in > +++ b/sawfish-pager.spec.in > @@ -38,7 +38,7 @@ rm -rf $RPM_BUILD_ROOT > %files > %defattr(-,root,root,-) > %doc COPYING NEWS README TODO > -%{_libdir}/sawfish/%{sawfish_ver}/*/pager > +%{_libdir}/sawfish/%{sawfish_ver}/*/sawfishpager > %{_datadir}/sawfish/%{sawfish_ver}/lisp/sawfish/wm/ext/ Thanks. Chris
