On 2012-01-27 Dimitris Papageorgiou wrote:
> This works for me:
>
> awful.key({ modkey, }, ",", function ()
> awful.client.incwfact(-0.05) end), awful.key({ modkey, }, ".",
> function () awful.client.incwfact( 0.05) end),
That works for me, too. When I change to another
This works for me:
awful.key({ modkey, }, ",", function ()
awful.client.incwfact(-0.05) end),
awful.key({ modkey, }, ".", function () awful.client.incwfact(
0.05) end),
It is indeed mentioned in the FAQ though the keys suggested weren't available
in the rc.lua debian
I'm sorry for spamming the list, but as a new user I face
some problems getting my configuration right.
Yes, that's exactly the question from the FAQ. I added the
code to my rc.lua, but I still cannot change the size of
the clients.
My scenario: I use the layout “tile” and open three
te
Thank you for the reply, Uli!
You were absolutely right. I tried to recompile awesome with the changes
in client.c you mentioned and it changed nothing. Then I removed
proprietary FGLRX drivers and installed xf86-video-ati and it worked
like a charm.
Guess now I should be choosing between 3D
On 2012-01-27 Bill Sun wrote:
> On Thu, Jan 26, 2012 at 05:06:00PM +0100, Marco wrote:
> > I face a problem with vim since I use awesome. Sometimes
> > the displayed text is wrong (for instance when scrolling,
> > the wrong part of the file is displayed), marking the text
> > then changes to t
On 2012-01-26 Perry Hargrave wrote:
> On Jan 26, 2012 7:50 PM, "Marco" wrote:
> >
> > On 2012-01-27 Anurag Priyam wrote:
> >
> > > On Fri, Jan 27, 2012 at 9:05 AM, Perry Hargrave
> wrote:
> > > >
> > > > Do you get the problem with
> > > >
> > > > vim -u NONE
> > >
> > > Or with gvim?
> >
> >
On 2012-01-27 Bill Sun wrote:
> On Thu, Jan 26, 2012 at 05:06:00PM +0100, Marco wrote:
> > I face a problem with vim since I use awesome. Sometimes
> > the displayed text is wrong (for instance when scrolling,
> > the wrong part of the file is displayed), marking the text
> > then changes to t
On 2012-01-27 Marco wrote:
> On 2012-01-26 Perry Hargrave wrote:
>
> > Also, does ctrl+L do anything?
> >
> > Does anything trigger the behavior? Like resizing
> > window, merging tags or toggle float.
>
> No, I didn't find an easy way to reproduce. I have the
> feeling that it only happ
On 2012-01-26 Perry Hargrave wrote:
> Also, does ctrl+L do anything?
>
> Does anything trigger the behavior? Like resizing
> window, merging tags or toggle float.
No, I didn't find an easy way to reproduce. I have the
feeling that it only happens when there are more lines in
the file
On 27.01.2012 09:04, Alexander Yakushev wrote:
Hello everyone,
Today I for the first time tried to use a composite manager (to be able
to use transparent wiboxes in git/master version, as Uli suggested). I
started with xcompmgr and the wiboxes went transparent just fine... with
all of my windows
On 2012-01-27 Javier Barroso wrote:
> On Fri, Jan 27, 2012 at 12:37 AM, Marco wrote:
> > On 2012-01-27 Javier Barroso wrote:
> >
> >> On Thu, Jan 26, 2012 at 7:37 PM, Marco wrote:
> >> > On 2012-01-26 Julien Danjou wrote:
> >> >
> >> >> On Thu, Jan 26 2012, Marco wrote:
> >> >>
> >> >> > I fa
On 2012-01-26 Perry Hargrave wrote:
> On Jan 26, 2012 8:06 AM, "Marco" wrote:
> >
> > I face a problem with vim since I use awesome. Sometimes
> > the displayed text is wrong (for instance when scrolling,
> > the wrong part of the file is displayed), marking the text
> > then changes to the c
On 2012-01-27 Dimitris Papageorgiou wrote:
> > Marco writes:
>
> > Some of my applications (e.g. urxvt, xterm) don't take the space
> > they should. There's a small border at the bottom, a few pixels,
> > maybe 8-14.
>
> > I already tried to set the border to zero, then I
Hello everyone,
Today I for the first time tried to use a composite manager (to be able
to use transparent wiboxes in git/master version, as Uli suggested). I
started with xcompmgr and the wiboxes went transparent just fine... with
all of my windows. Changing any settings in the xcompmgr comma
14 matches
Mail list logo
