Hello everyone Awesome,
I wrote this little module yesterday and I think some users will like it:
https://github.com/Elv13/retrograde
It allow you to setup layout using a declarative syntax again,
something I missed since the 3.4.* days. It is rare I consider a
module as complete and ready for t
Quoting Fred (2013-01-11 08:05:57)
> Le dim. 06 janv. 2013 17:33:40 CET, Fred a écrit :
>
> >…
> > I've started to learn keyboard shortcuts, but faced a problem : some
> > shortcuts doesn't work. I thought at first about a syntax problem in
> > rc.lua, but actually found that many of « client » k
Le dim. 06 janv. 2013 17:33:40 CET, Fred a écrit :
>…
> I've started to learn keyboard shortcuts, but faced a problem : some
> shortcuts doesn't work. I thought at first about a syntax problem in
> rc.lua, but actually found that many of « client » keyboard shortcuts
> didn't work... I was unable
Hello,
I'm trying to learn using Awesome on a Debian Squeeze system :
- awesome Debian package, version 3.4.6-1
- with Gnome-session (2.30...)
I use a specific rc.lua, mainly because I use an unusual french dvorak
keyboard setup called Bépo, and got a rc.lua sample here :
http://bepo.fr
Patch to fix the luadoc build, with lua 5.1.
Without this you get a nil error out of luadoc.
Signed-off-by: Robin H. Johnson
--- ../awesome-3.5-rc1/lib/naughty.lua.in.orig 2012-11-24 05:51:33.0
-0800
+++ ../awesome-3.5_rc1/lib/naughty.lua.in 2012-11-24 13:17:14.025201211
-0800
@
Hi guys,
it's never too late to release ;)
Anyway: can someone prepare a debian package?
Thanks and kind regards,
Andre
--
Andre Klärner
smime.p7s
Description: S/MIME cryptographic signature
Thanks a lot guys :)
] awesome
3.4-rc1 released)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi everyone,
On 11.09.2009 14:05, Julien Danjou wrote:
> With a good month late, here comes 3.4-rc1.
With a good two years late, here comes 3.5-rc1.
> There's an amazing number of changes, but many are interna
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi everyone,
On 11.09.2009 14:05, Julien Danjou wrote:
> With a good month late, here comes 3.4-rc1.
With a good two years late, here comes 3.5-rc1.
> There's an amazing number of changes, but many are internals ones, so you
> won't notice them.[
Just wanted to say thanks for all the help! I can finally get my
Awesome setup the way I want it. :)
Hong Pak
On Fri, May 4, 2012 at 2:37 PM, Uli Schlachter wrote:
> On 04.05.2012 19:57, Hong Shick Pak wrote:
>> I'm new to mailing lists so I don't think my last reply (the following
>> message) g
On 04.05.2012 19:57, Hong Shick Pak wrote:
> I'm new to mailing lists so I don't think my last reply (the following
> message) got through. Here's me reposting it.
>
> From what I take it, I need to create a wibox.layout, define custom
> margins and stick my widget in it?
>
> I'm new to lua and a
I'm new to mailing lists so I don't think my last reply (the following
message) got through. Here's me reposting it.
>From what I take it, I need to create a wibox.layout, define custom
margins and stick my widget in it?
I'm new to lua and awesome so I'm again lost at what to do...
I did give it
On 03.05.2012 21:42, dodo wrote:
> On 2 May 2012 22:24, Uli Schlachter wrote:
>> Hi,
>>
>> On 02.05.2012 22:03, Hong Shick Pak wrote:
>>> I am currently using awesome-git-20120214-1 and there are changes with
>>> the config that I can't find documented. I have tried to read the git
>>> commit logs
On 2 May 2012 22:24, Uli Schlachter wrote:
> Hi,
>
> On 02.05.2012 22:03, Hong Shick Pak wrote:
>> I am currently using awesome-git-20120214-1 and there are changes with
>> the config that I can't find documented. I have tried to read the git
>> commit logs and its a bit cryptic for me. I've run i
>From what I take it, I need to create a wibox.layout, define custom
margins and stick my widget in it?
I'm new to lua and awesome so I'm again lost at what to do...
I did give it my best shot though:
local membar_wibar = wibox.layout.flex.horizontal()
wibox.layout.margin.set_margins(membar_wibar
Hi,
On 02.05.2012 22:03, Hong Shick Pak wrote:
> I am currently using awesome-git-20120214-1 and there are changes with
> the config that I can't find documented. I have tried to read the git
> commit logs and its a bit cryptic for me. I've run into 2 issues
> specifically. What happened to widget
2012/5/2 Hong Shick Pak :
> I am currently using awesome-git-20120214-1 and there are changes with
> the config that I can't find documented.
http://awesome.naquadah.org/wiki/Awesome_3.4_to_git_master
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
I am currently using awesome-git-20120214-1 and there are changes with
the config that I can't find documented. I have tried to read the git
commit logs and its a bit cryptic for me. I've run into 2 issues
specifically. What happened to widget.layouts? set_gradient_colors
also seem to be gone. Are
Hello all,
I gave up :)
Unfortunately but current state of Displaylink driver or Xinerama is
unusable for me with Awesome and pretty any WM (including KDE). The
only one working was XFCE but this is not what I want.
I will keep trying and if I find it working for me as I want I will report.
Tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02.09.2011 21:16, Piotr Adamus wrote:
> I am just wondering. How is that possible if I run Xorg only on Intel
> and two physical monitors Awesome somehow can recognize them and set
> tag list separate per each monitor (so I use only one screen per
You may also want to look here:
http://lists.freedesktop.org/archives/libdlo/2011-June/000946.html
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
W dniu 2 września 2011 21:16 użytkownik Piotr Adamus
napisał:
> I am just wondering. How is that possible if I run Xorg only on Intel
> and two physical monitors Awesome somehow can recognize them and set
> tag list separate per each monitor (so I use only one screen per
> xorg.conf).
>
> And if I
Hello Pawel,
I am just wondering. How is that possible if I run Xorg only on Intel
and two physical monitors Awesome somehow can recognize them and set
tag list separate per each monitor (so I use only one screen per
xorg.conf).
And if I use two screens (Intel and Displalink) awesome cannot
recog
Hello Pawel,
perhaps this is Linux- that's why it works beyond physics :)
Thank you for your help- maybe new update to libdlo and udlfb will
change that behaviour.
With kind regards.
Piotr.
On Wed, Aug 31, 2011 at 10:35 PM, Paweł wrote:
> 2011/8/31 Piotr Adamus :
>> Hi Pawel,
>>
>> Xinerama m
2011/8/31 Piotr Adamus :
> Hi Pawel,
>
> Xinerama must be disabled- otherwise udlfb won't work at all. I spent
> a whole week trying to figure it out how to get it working. It
> eventually works, I can't complain but it could be even better :)
>
> I am attaching my current Xorg.0.log from working I
OK, thanks. Could you post Xorg.0.log?
I supposed that there must be Xinerama enabled somewhere, but it seems
to be disabled - I'm shocked it still works somehow.
greetings,
Paweł
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Hello,
attached.
Piotr.
On Wed, Aug 31, 2011 at 8:43 PM, Paweł wrote:
> OK, can you post your xorg.conf?
>
> Paweł
>
xorg.conf
Description: Binary data
OK, can you post your xorg.conf?
Paweł
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Yes it is. To get Displaylink working I need to have xorg.conf configured.
Piotr.
On Wed, Aug 31, 2011 at 8:38 PM, Paweł wrote:
> 2011/8/31 Piotr Adamus :
>> Hi Pawel,
>>
>> if I remove xorg.conf then I won't be able to attach xorg to
>> Displaylink- simply xorg will attach to Intel driver only.
2011/8/31 Piotr Adamus :
> Hi Pawel,
>
> if I remove xorg.conf then I won't be able to attach xorg to
> Displaylink- simply xorg will attach to Intel driver only.
You mean that after removing xorg.conf and doing 'xrandr -q' you dont
get any info about DL output, only about Intel?
Because it is the
Hi Pawel,
if I remove xorg.conf then I won't be able to attach xorg to
Displaylink- simply xorg will attach to Intel driver only.
Piotr.
On Wed, Aug 31, 2011 at 8:21 PM, Paweł wrote:
> 2011/8/31 Piotr Adamus :
>> Hello all,
>>
>> just one question. Is it possible to split a screen like in scrot
2011/8/31 Piotr Adamus :
> Hello all,
>
> just one question. Is it possible to split a screen like in scrotwm in
> example below?
As far as I know Awesome relies totally on xorg configuration of the
screen and it is not possible. This is why we're digging into RandR.
But please anyone correct me
2011/8/31 Piotr Adamus :
> -pure Xorg without xorg.conf and Display utilize LVDS and DVI (like
> before I used Display). No problems with Awesome. Here is xrandr
> output:
>
> Guusje% xrandr -q
> Screen 1: minimum 320 x 200, current 3200 x 1080, maximum 8192 x 8192
Is DL really disconnected? I sup
Hello all,
just one question. Is it possible to split a screen like in scrotwm in
example below?
# Split a non-Xrandr dual head setup into one region per monitor
# (non-standard driver-based multihead is not seen by scrotwm)
region = screen[2]:1280x800+0+0
region = screen[1]:19
Hello Pawel,
my findings.
-pure Xorg without xorg.conf and Display utilize LVDS and DVI (like
before I used Display). No problems with Awesome. Here is xrandr
output:
Guusje% xrandr -q
Screen 1: minimum 320 x 200, current 3200 x 1080, maximum 8192 x 8192
DVI1 connected 1920x1080+1280+0 (normal l
Hi Pawel,
sure- I will report back in the evening.
Kr.
Piotr.
On Wed, Aug 31, 2011 at 2:22 PM, Paweł wrote:
> 2011/8/31 Piotr Adamus :
>
>> But if only I attach Displaylink (so create another screen in
>> xorg.conf what is a must) then that situation occurs.
>
> Recent versions of xorg-server
2011/8/31 Piotr Adamus :
> But if only I attach Displaylink (so create another screen in
> xorg.conf what is a must) then that situation occurs.
Recent versions of xorg-server don't NEED xorg.conf. All configuration
can be done using xrandr, and xorg.conf contains only tweaks that fail
to auto-co
Hi Pawel,
well this is my current setup- LVDS and DVI are attached to Intel (and
if only those are attached with xorg.conf configure for a one scree
then awesome works awesome- rules works, maximization per monitor
too). But if only I attach Displaylink (so create another screen in
xorg.conf what
Hi Piotr,
I wonder whether it may be an issue with displaylink driver not
reporting correct screen configuration to RandR.
Have you tried (I don't know is it possible with your hardware)
attaching two displays to Intel gfx, and one to DL?
Still I'm very surpsised that you were able to get two car
Hi Pawel,
no. This is issue with any window manager (including KDE, all tiling
managers). The only exception here is Xfce4. Using this I can maximize
window on LVDS e.g. or on DVI- so the maximizing doesn't stretch
window on both LVDS and DVI.
Is there any possibility to "split" screen 1 (consist
Hello,
I have following issue and I would like to ask you for a help.
Physical configuration:
-GFX card: Intel and Displaylink (both works)
-Laptop LCD, and two external LCDs (one for DVI output of the laptop;
another for Displaylink).
The Displaylink forces me to set it screen 0 for Displaylin
2009/11/3 Simón Castillo
> Hello.
>
> I am using awesome 3.4 and bioe007's repo shifty version. For
> some reason either awesome or shifty, maybe both, is not honoring my
> default config to set everything not matched to the tilebottom layout.
> Instead
> it sets some
On Fri, Nov 06, 2009 at 12:41:17PM +0100, Julien Danjou wrote:
> At 1256674326 time_t, Pierre Habouzit wrote:
> > On top of v3.4
> >
> > Using that patch http://paste.debian.net/50072/plain/50072
> >
> > Plus this one:
> >
> > diff --git a/lib/awful/layout/init.lua.in b/lib/awful/layout/init
It works with "KP_Enter", thanks!
I must saw it by myself.
Thanks a lot guys.
On Sat, Nov 07, 2009 at 04:25:34PM -0200, Rodrigo Amorim Bahiense
wrote:
> Try change "Return" with "KP_Enter" or just "Enter" in rc.lua.
>
> On Sat, Nov 7, 2009 at 4:15 PM, Viacheslav Chumushuk wrote:
> > xev recog
Try change "Return" with "KP_Enter" or just "Enter" in rc.lua.
On Sat, Nov 7, 2009 at 4:15 PM, Viacheslav Chumushuk wrote:
> xev recognize Return key. Here is the output:
>
> KeyRelease event, serial 28, synthetic NO, window 0x2c1,
> root 0xfa, subw 0x0, time 19378088, (844,-451), root:(84
xev recognize Return key. Here is the output:
KeyRelease event, serial 28, synthetic NO, window 0x2c1,
root 0xfa, subw 0x0, time 19378088, (844,-451), root:(845,0),
state 0x10, keycode 104 (keysym 0xff8d, KP_Enter), same_screen YES,
" XLookupString gives 1 bytes: (0d) "
XFilterEv
Amorim Bahiense
wrote:
> Install package xbindkeys and run: xbindkeys -v -n
>
> Press "Return" to check if key is being recognized, otherwise that
> might be some hal problem, or even an unlikely package compile error
> for awesome 3.4-2 in Arch Linux i686 repository. If pr
On Sat, 7 Nov 2009 19:27:38 +0200
Viacheslav Chumushuk wrote:
> Yes, with another keys it works perfect.
>
> On Sat, Nov 07, 2009 at 03:24:12PM -0200, Rodrigo Amorim Bahiense
> wrote:
> > Have you tried to replace Return shortcuts with another key binding?
> > Say, instead of Return, use g, y,
Yes, with another keys it works perfect.
On Sat, Nov 07, 2009 at 03:24:12PM -0200, Rodrigo Amorim Bahiense
wrote:
> Have you tried to replace Return shortcuts with another key binding?
> Say, instead of Return, use g, y, or some other key?
--
Please, use plain text message format contacting me
Result is the same.
But keydindings from clientkeys are work, if they don't use Return key.
On Sat, Nov 07, 2009 at 01:32:37PM -0200, Rodrigo Amorim Bahiense
wrote:
> Try to remove:
>
> keys = clientkeys,
>
> in awful.rules.rules and merge clientkeys section with globalkeys section.
>
--
Pl
Try to remove:
keys = clientkeys,
in awful.rules.rules and merge clientkeys section with globalkeys section.
On Sat, Nov 7, 2009 at 1:24 PM, Viacheslav Chumushuk wrote:
> With root and client result is the same.
> I'v attached my rc.lua file.
>
> On Sat, Nov 07, 2009 at 01:15:54PM -0200, Rodrig
With root and client result is the same.
I'v attached my rc.lua file.
On Sat, Nov 07, 2009 at 01:15:54PM -0200, Rodrigo Amorim Bahiense
wrote:
> Is this behavior related only with awesome root window or inside
> clients too? Can you send a copy of your rc.lua?
>
--
Please, use plain text mess
> I'm running Arch Linux x86_64, awesome 3.4-2, and "Return" key is working
> fine.
>
> globalkeys = awful.util.table.join(
> ...
> awful.key({modkey, "Shift" }, "Return",
> function () awful.util.spawn(terminal)end),
> ...
I'm running Arch Linux x86_64, awesome 3.4-2, and "Return" key is working fine.
globalkeys = awful.util.table.join(
...
awful.key({modkey, "Shift" }, "Return",
function () awful.util.spawn(terminal)end),
...
)
On Sat, Nov 7, 2009 at 12:23 PM, V
"Control" }, "Return", awful.client.floating.toggle
),
[/lua]
And after last update (I'm using Archlinux distro) all keybindings with Return
key broken.
Does anybody have the same problem?
My software is:
OS: Archlinux
awesome: 3.4-2
Thanks.
Best regards, Vi
escribió:
> Hi,
>
> I've also run into trouble using Obvious on awesome 3.4. I required
> the module ("obvious/volume_alsa") but the configuration loading
> crashed.
>
> This is due to a new dependency of Obvious to the lua socket library
> (with debian tes
On Wed, 4 Nov 2009, Christian Cikryt wrote:
When I switch tags, move the mouse to a different part of the screen
and then switch back to the original tag, the window that was last
focused on this tag is now focused and not on the windows under the
mouse pointer. I'd like to have the windows un
focus = awful.mouse.client_under_pointer()
end
end)
I'm using awesome 3.4 and tried writing the following in the signal
section of rc.lua. However it has no effect. I don't know how the
arrange signal is emitted or if it is emitted at all.
client.add_signal("arrange", fun
Hello.
I am using awesome 3.4 and bioe007's repo shifty version. For
some reason either awesome or shifty, maybe both, is not honoring my
default config to set everything not matched to the tilebottom layout. Instead
it sets some apps to float. I detected it on OO.org and thought it was some
Hi there,
I upgraded to awesome 3.4 a soon as it was released, but so
far I've been unable to get the obvious widgets working, since readme
files are outdated/nonexistent and google show nothing...
Can someone give me a hint on the right direction to get this working?
An example on a the ne
At 1256606721 time_t, Pierre Habouzit wrote:
> This was perfect and forced the mouse inside the window of newly created
> clients, or when changing the focus to a new client *AFTER* all the
> resizes had been done.
>
> There is absolutely no sane way to do that right now unless I'm
> mistaken. I t
On Thu, Oct 22, 2009 at 09:37:19AM -0700, Marc Petit-Huguenin wrote:
> Hi,
>
> What is the equivalent of awful.hooks.arrange.register(function (screen) in
> Awesome 3.4? In 3.3 I added the following line to this hook, but now I do not
> know how where to put it:
&g
At 1256399132 time_t, Dmitry Korzhevin wrote:
> Please, submit this information to
> http://awesome.naquadah.org/download/ page:
Added.
--
Julien Danjou
// ᐰhttp://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
// Trust no one.
signature.asc
Description: Digital s
On Sat, Oct 24, 2009 at 11:11:25PM -0700, member zhurai wrote:
> asked about this on the irc
>
> mytextclock = awful.widget.textclock({ align = "right"}, " %a %b %d,
> %H:%M:%S", 10 })
>
> is what you want!
>
Thanks!
I,ve should have learned by now, to never touch a awesome config after
2:00 AM.
Perry Hargrave ; wrote:
On Fri, Oct 23, 2009 at 10:28:59PM +0200, "Jérôme M. Berger" wrote:
- How can I set the default layout for my tags? Right now it starts
in "floating" layout, which is about the worst possible choice (if I
wanted a floating wm I wouldn't be using awesome).
please see num
asked about this on the irc
mytextclock = awful.widget.textclock({ align = "right"}, " %a %b %d,
%H:%M:%S", 10 })
is what you want!
- Zhurai / Brandon Fu
On Sat, Oct 24, 2009 at 7:32 PM, Raphael Scholer
wrote:
> mytextclock = awful.widget.textclock({ align = "right", \
> format = " %a %b %d, %
Hi,
I'm having trouble configuring my textclock widget. I want to display
seconds and to set the timeout to 1 second. The command I'm using is the
following:
mytextclock = awful.widget.textclock({ align = "right", \
format = " %a %b %d, %H:%M:%S", timeout = 10 })
But awesome always uses the defau
2009/10/25 Adrian C.
> On Sun, 25 Oct 2009, Viacheslav Chumushuk wrote:
>
> Can you show me the right way to display widgets one after another?
>>
>
> mywibox_bottom[s].widgets = {
>mailmonitor,
>batterymonitor,
>cputempmonitor,
>clockmonitor,
>layout = awful.widget.layout.ho
On Sun, 25 Oct 2009, Viacheslav Chumushuk wrote:
Can you show me the right way to display widgets one after another?
mywibox_bottom[s].widgets = {
mailmonitor,
batterymonitor,
cputempmonitor,
clockmonitor,
layout = awful.widget.layout.horizontal.rightleft
}
--
Adrian C. (
Hello.
I updated to 3.4 version and have some problems with awesome configurations.
I made wibox and add textbox widgets into it, but all widgets have the same
position.
Awesome outputs all widgets in the same position, so they draws one over other.
Here is the code from my configuration file:
.
Hi,
Please, submit this information to http://awesome.naquadah.org/download/
page:
Distribution: MOPSLinux (http://mopslinux.org), packages are avaible
right out of the box :)
All future awesome updates will be avaible at packages repository:
http://mopspackages.ru/
--
Best regards,
Dmit
On Fri, Oct 23, 2009 at 10:28:59PM +0200, "Jérôme M. Berger" wrote:
> - How can I set the default layout for my tags? Right now it starts
> in "floating" layout, which is about the worst possible choice (if I
> wanted a floating wm I wouldn't be using awesome).
please see numerous other mail threa
Excerpts from Jérôme M. Berger's message of Sat Oct 24 07:28:59 +1100 2009:
> Hi,
>
> I've just upgraded to awesome 3.4 and I have a couple of
> issues/questions:
>
> - I have a vertical xfce panel on the left of my screen. With
> awesome 3.3 all was fin
Hi,
I've just upgraded to awesome 3.4 and I have a couple of
issues/questions:
- I have a vertical xfce panel on the left of my screen. With
awesome 3.3 all was fine, but now the left part of the wibox is
hidden behind the panel. (Note that I had the opposite issue with an
Hi,
What is the equivalent of awful.hooks.arrange.register(function (screen) in
Awesome 3.4? In 3.3 I added the following line to this hook, but now I do not
know how where to put it:
client.focus = awful.mouse.client_under_pointer()
Thanks for your help.
--
To unsubscribe, send mail to
I've started using Awesome 2 months ago, and I'm lovin' it damn much!
..going to use 3.4
way to go guys.. :)
On Tue, Oct 20, 2009 at 11:43 PM, Félix C. Morency
wrote:
> Keep up the good work. I'm looking forward to try awesome 3.4.
>
> Cheers,
> -Félix
>
Keep up the good work. I'm looking forward to try awesome 3.4.
Cheers,
-Félix
On Tue, Oct 20, 2009 at 12:43 PM, Felix Herrmann
wrote:
> On (Tue) 2009-10-20 20:53:12, Julien Danjou wrote:
>> Or we did total crap and nobody is using awesome anymore. :-)
> Im sure that's
On (Tue) 2009-10-20 20:53:12, Julien Danjou wrote:
> Or we did total crap and nobody is using awesome anymore. :-)
Im sure that's right. Nobody is using ugly awesome anymore.
Just kidding:). Great work, thanks a lot!
Felix.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
// ᐰhttp://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
awesome version 3.4 has been released. It is available from:
tar.gz: http://awesome.naquadah.org/download/awesome-3.4.tar.gz
md5: 4008e85c85694028eea593180ba2195f
sha1: 5e668b927229ab41a555415523c573004e204795
ar.gz: http://awesome.naquadah.org/download/awesome-3.4-rc3.tar.gz
md5: cbf41eba15ba61de8a854291d7adbcaa
sha1: a3a8407e50692a8476bcd6bac4792b574029eb9b
tar.bz2: http://awesome.naquadah.org/download/awesome-3.4-rc3.tar.bz2
md5: 5fd2e01c5bc7d5f4765731a05fea8691
sha1: 20aed6171a0a8c2481e69d1889d23038155
On Wed, Sep 30, 2009 at 3:39 PM, kAworu wrote:
> On Wed, Sep 30, 2009 at 03:22:55PM +0200, Julien Danjou wrote:
>> At 1254315845 time_t, Renato Botelho wrote:
>> > I never used cmake so i don't know how to collect more detailed
>> > data to make it easy to debug, could you gimme some help?
>>
>> I
On Wed, Sep 30, 2009 at 03:22:55PM +0200, Julien Danjou wrote:
> At 1254315845 time_t, Renato Botelho wrote:
> > I never used cmake so i don't know how to collect more detailed
> > data to make it easy to debug, could you gimme some help?
>
> It probably miss -lexecinfo in the link command. I'm no
At 1254315845 time_t, Renato Botelho wrote:
> I never used cmake so i don't know how to collect more detailed
> data to make it easy to debug, could you gimme some help?
It probably miss -lexecinfo in the link command. I'm not a CMake expert,
so there's a chance we have to fix that in awesome's cm
is the error:
Linking C executable awesome
CMakeFiles/awesome.dir/common/backtrace.c.o(.text+0x21): In function
`backtrace_get':
/home/garga/prs/awesome/work/awesome-3.4-rc2/common/backtrace.c:37:
undefined reference to `backtrace'
CMakeFiles/awesome.dir/common/backtrace.c.o(.text+0x33):/home/g
At 1254314018 time_t, Renato Botelho wrote:
> I'll research about it but I never heard about it be available for
> FreeBSD, if i'm right and we don't have it on FreeBSD, could you
> add a conditional to don't use it on FreeBSD?
Sure.
--
Julien Danjou
// ᐰhttp://julien.danjou.info
// 9A0D 5FD
On Wed, Sep 30, 2009 at 9:24 AM, Julien Danjou wrote:
> At 1254312303 time_t, Renato Botelho wrote:
>> Let me know if you need more information, i can provide it.
>>
>> Any ideas?
>
> I think you need something like 'libbacktrace'. I don't know the name
> for sure, that's part of glibc actually. B
On Wed, Sep 30, 2009 at 9:24 AM, Julien Danjou wrote:
> At 1254312303 time_t, Renato Botelho wrote:
>> Let me know if you need more information, i can provide it.
>>
>> Any ideas?
>
> I think you need something like 'libbacktrace'. I don't know the name
> for sure, that's part of glibc actually. B
At 1254312303 time_t, Renato Botelho wrote:
> Let me know if you need more information, i can provide it.
>
> Any ideas?
I think you need something like 'libbacktrace'. I don't know the name
for sure, that's part of glibc actually. But I've heard it can be found
on other OSes (at least the ones w
l so if no one
> take a look at them, they may only be fixed in stable update.
I tried to build it on FreeBSD 9.0-CURRENT and got follow error:
Linking C executable awesome
CMakeFiles/awesome.dir/common/backtrace.c.o(.text+0x21): In function
`backtrace_get':
/home/garga/prs/awesome/work/a
Cheers,
--
Julien Danjou
// ᐰhttp://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
awesome version 3.4-rc2 has been released. It is available from:
tar.gz: http://awesome.naquadah.org/download/awesome-3.4-rc2.tar.gz
md5: c5894d7e66497e87374a6be8ae2600d0
sha1: 4243a9a95f
On Fri, Sep 11, 2009 at 5:16 AM, Alessandro Massignan
wrote:
> Hi,
>
> > With a good month late, here comes 3.4-rc1.
> > [...]
> > You will be pleased to hear that we have started to renforce our
> > documentation system.
> > [...]
> You are the ONES!!! :-)
>
Hear, hear!
As always, looking forwa
Hi,
> With a good month late, here comes 3.4-rc1.
> [...]
> You will be pleased to hear that we have started to renforce our
> documentation system.
> [...]
You are the ONES!!! :-)
Thanks for this gem!
ff
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
pressure, my mood and my
bad jokes. :-)
As always, happy hacking everyone!
Cheers,
--
Julien Danjou
// ᐰhttp://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
awesome version 3.4-rc1 has been released. It is available from:
tar.gz: http://awesome.naquadah.org/
93 matches
Mail list logo
