Jim Pryor | 1 Aug 02:12 2009
Picon

Re: Awesome git compilation errors in Archlinux

Renaming common/signal.h to signal2.h (and changing the include line in
common/luaclass.h from "common/signal.h" to "common/signal2.h" allows
the compile to succeed). So I think something like this is the problem.
Is something wrong with my build or cmake setup?

On Fri, Jul 31, 2009 at 12:15:19PM -0400, Jim Pryor wrote:
> I'm also seeing these difficulties. I haven't tracked down the exact
> cause yet, but I notice that a package library common/signal.h was
> recently added, and that the variables that the compile is failing
> because of are defined in /usr/include/signal.h (actually in a file that
> this sources). Is the package-level signal.h masking the system-level
> one? I don't understand cmake enough to know how. But it seems like this
> is related to the problem.
> 
> Here are the build instructions I'm using. Any feedback on them would be
> welcome. $pkgdir is the Arch installation root.
> 
> 
> function build() {
> 
>     # irrelevant stuff, like synching against git..., then:
> 
> 	sed 's!usr/local/lib!usr/lib!g' -i awesomeConfig.cmake #-i CMakeFiles/awesome.dir/link.txt ||
return 1
> 
>     cmake -DCMAKE_INSTALL_PREFIX=/usr -DSYSCONFDIR=/etc || return 1
>     make || return 1
>     make DESTDIR=$pkgdir install || return 1
> 
> 	 install -Dm644 ${srcdir}/awesome.desktop ${pkgdir}/usr/share/xsessions/awesome.desktop
(Continue reading)

giggz | 1 Aug 13:37 2009
Picon

warning in my .xsession-errors : luaA_keystore:1005: there's no keysym named "F#10"

Hi,

I just take a look to my .xsession-errors and i'm seeing some warnings
like this :
W: awesome: luaA_keystore:1005: there's no keysym named "F#10"
W: awesome: luaA_keystore:1005: there's no keysym named "F#11"
W: awesome: luaA_keystore:1005: there's no keysym named "F#12"
W: awesome: luaA_keystore:1005: there's no keysym named "F#13"
W: awesome: luaA_keystore:1005: there's no keysym named "F#14"
W: awesome: luaA_keystore:1005: there's no keysym named "F#15"
W: awesome: luaA_keystore:1005: there's no keysym named "F#16"
W: awesome: luaA_keystore:1005: there's no keysym named "F#17"
W: awesome: luaA_keystore:1005: there's no keysym named "F#18"

How can I suppress them ?
should I post my rc.lua ?

Best regards,
Guillaume

Julien Danjou | 3 Aug 09:32 2009

Re: warning in my .xsession-errors : luaA_keystore:1005: there's no keysym named "F#10"

At 1249126630 time_t, giggz wrote:
> How can I suppress them ?

Stop using F#x as key, since they do not exist?

Cheers,
--

-- 
Julien Danjou
// ᐰ <julien <at> danjou.info>   http://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD
// This is the end of my signature.
giggzounet | 3 Aug 09:45 2009
Picon

Re: warning in my .xsession-errors : luaA_keystore:1005: there's no keysym named "F#10"

Julien Danjou a écrit :
> At 1249126630 time_t, giggz wrote:
>> How can I suppress them ?
> 
> Stop using F#x as key, since they do not exist?
> 
> Cheers,

Ok. But what are these keys ??? Are they F1,F2,F3... ?

Thx for your answer.
Guillaume

--

-- 
To unsubscribe, send mail to awesome-unsubscribe <at> naquadah.org.

Julien Danjou | 3 Aug 09:52 2009

Re: warning in my .xsession-errors : luaA_keystore:1005: there's no keysym named "F#10"

At 1249285541 time_t, giggzounet wrote:
> Ok. But what are these keys ??? Are they F1,F2,F3... ?

I don't know, you wrote your config. If you want to use F1, F2... these
are the names. :)

--

-- 
Julien Danjou
// ᐰ <julien <at> danjou.info>   http://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD
// The more we fly, the more we climb, the more we know that heaven is a lie.
giggzounet | 3 Aug 10:12 2009
Picon

Re: warning in my .xsession-errors : luaA_keystore:1005: there's no keysym named "F#10"

Julien Danjou a écrit :
> At 1249285541 time_t, giggzounet wrote:
>> Ok. But what are these keys ??? Are they F1,F2,F3... ?
> 
> I don't know, you wrote your config. If you want to use F1, F2... these
> are the names. :)
> 

:)
oki oki...I will delete all my keys and add them one by one...

Bye
Guillaume

--

-- 
To unsubscribe, send mail to awesome-unsubscribe <at> naquadah.org.

Felix | 4 Aug 06:30 2009
X-Face
Picon

Re: Awesome git compilation errors in Archlinux

Seems the fix is in git now. Good spotting Jim.

On Fri, Jul 31, 2009 at 08:12:01PM -0400, Jim Pryor wrote:
> Renaming common/signal.h to signal2.h (and changing the include line in
> common/luaclass.h from "common/signal.h" to "common/signal2.h" allows
> the compile to succeed). So I think something like this is the problem.
> Is something wrong with my build or cmake setup?
> 
> 
> 
> On Fri, Jul 31, 2009 at 12:15:19PM -0400, Jim Pryor wrote:
> > I'm also seeing these difficulties. I haven't tracked down the exact
> > cause yet, but I notice that a package library common/signal.h was
> > recently added, and that the variables that the compile is failing
> > because of are defined in /usr/include/signal.h (actually in a file that
> > this sources). Is the package-level signal.h masking the system-level
> > one? I don't understand cmake enough to know how. But it seems like this
> > is related to the problem.
> > 
> > Here are the build instructions I'm using. Any feedback on them would be
> > welcome. $pkgdir is the Arch installation root.
> > 
> > 
> > function build() {
> > 
> >     # irrelevant stuff, like synching against git..., then:
> > 
> > 	sed 's!usr/local/lib!usr/lib!g' -i awesomeConfig.cmake #-i CMakeFiles/awesome.dir/link.txt ||
return 1
> > 
(Continue reading)

Jean-Philippe Braun | 4 Aug 16:14 2009

Gimp and floating mode

Hello,

I'm wondering why all gimp toolboxes are set in floating mode while gimp
isn't listed as a "floatapp" in my configuration

I also can't turn off floating mode on this windows manually (through
awful.client.floating.toggle)

Whatever I try only the main window can be set as a floating or title
window

Best regards,

Rodrigo Bistolfi | 4 Aug 18:05 2009
Picon

Re: Gimp and floating mode

On Tue, Aug 04, 2009 at 04:14:39PM +0200, Jean-Philippe Braun wrote:
> Hello,
> 
> I'm wondering why all gimp toolboxes are set in floating mode while gimp
> isn't listed as a "floatapp" in my configuration

The Gimp guys changed the hint for the toolbox. You have to use Edit,
Preferences, Window Management and change hint for windows to "Normal".

-- 
| Rodrigo Bistolfi                | (·)>
| Using the Mutt mail client      | /|\
| Vector Linux 6.0 Light Edition  | \_/_
                                    /

--

-- 
To unsubscribe, send mail to awesome-unsubscribe <at> naquadah.org.

eeeeeeee | 4 Aug 19:18 2009
Picon

awesome-git titlebar problems

I seem to be having a problem displaying titlebars in the most recent awesome-git. The error i'm getting is W: awesome: luaA_dofunction:93: error running function: /usr/share/awesome/lib/awful/titlebar.lua:188: attempt to call local 'button' (a userdata value).

my rc.lua can be found at http://pastebin.com/m3e07f879 and my titlebar.lua can be found at http://pastebin.com/m75a915ce

i appreciate any help, thanks.


Gmane