On Mon, 23 Jan 2012, Benjamin R. Haskell wrote:
I had similar results until I compiled the st terminfo file by running:
tic st
Sorry:
tic st.info
On Sun, 22 Jan 2012, Christopher Lunsford wrote:
I'm having problems displaying fonts. Every font I use, besides the
default, leaves the display in a messy state. My locale is en_US.utf8
if it makes a difference and using the repo's tip. Here is a
screenshot: http://i43.tinypic.com/241r1jp.jpg
I'm having problems displaying fonts. Every font I use, besides the
default, leaves the display in a messy state. My locale is en_US.utf8
if it makes a difference and using the repo's tip. Here is a
screenshot: http://i43.tinypic.com/241r1jp.jpg
On Sun, Jan 22, 2012 at 10:10:23PM +0100, hiro wrote:
> Well, I already did break one of my usb ports.
That's the spirit!
> Should be easy to break the other two. But then also beware of the
> pcmcia ports. You can use a cheap FPGA to hack the whole PC using DMA
> over pci or so I heard.
Seems w
Well, I already did break one of my usb ports. Should be easy to break
the other two. But then also beware of the pcmcia ports. You can use a
cheap FPGA to hack the whole PC using DMA over pci or so I heard.
>> usb keyboard will bypass your security protections against this.
>
> That's a bug in yo
On Sun, Jan 22, 2012 at 09:15:53PM +0100, pancake wrote:
> On Jan 22, 2012, at 21:08, hiro <23h...@googlemail.com> wrote:
> > People used to take their steering wheels with them so that nobody
> > drives their car away. So I think your approach should work. Perhaps
> > you could take away the whole
usb keyboard will bypass your security protections against this.
On Jan 22, 2012, at 21:08, hiro <23h...@googlemail.com> wrote:
> People used to take their steering wheels with them so that nobody
> drives their car away. So I think your approach should work. Perhaps
> you could take away the who
On Sun, Jan 22, 2012 at 07:14:03PM +0100, Anselm R Garbe wrote:
> 2012/1/22 Hadrian Węgrzynowski :
> > I will repeat my self. Read this first:
> > http://who-t.blogspot.com/2012/01/xkb-breaking-grabs-cve-2012-0064.html
>
> I did, however there should be a way to prevent similar issues from
> happe
People used to take their steering wheels with them so that nobody
drives their car away. So I think your approach should work. Perhaps
you could take away the whole keyboard. It's very easy on my thinkpad.
Only 7 screws away from perfect security.
On 22.01.2012, pancake wrote:
> what about disab
> I just want to mention this breaks raising my floating windows also.
> Reverting the lines from the patch:
>
> - if(m->sel->isfloating || !m->lt[m->sellt]->arrange)
> - XRaiseWindow(dpy, m->sel->win);
>
> seems to fix it again.
That's why I attacked the SDL problem from another
On Sun, Jan 22, 2012 at 08:02:58PM +0100, Martti Kühne wrote:
> On Sun, Jan 22, 2012 at 01:22:20PM -0500, Peter John Hartman wrote:
> > Hi,
> >
> > Unfortunately, the tmux-split-pane problem still persists. The
> > tmux-split-pane problem is this: if one pane in tmux is spitting
> > out a bunch o
On Mon, Jan 16, 2012 at 12:25 AM, Anthony Cox wrote:
> This seems to have broken my floating windows - if I have a floating XTerm
> and open a new XTerm (tiled), the floating XTerm ends up behind the tiled
> one and I can no longer raise the floating one above.
>
I just want to mention this break
On Sun, Jan 22, 2012 at 01:22:20PM -0500, Peter John Hartman wrote:
> Hi,
>
> Unfortunately, the tmux-split-pane problem still persists. The
> tmux-split-pane problem is this: if one pane in tmux is spitting
> out a bunch of text (e.g. a sudo cat /var/log/messages or most
> compilations) you can
On Sat, Jan 21, 2012 at 11:54:17PM +0100, Aurélien Aptel wrote:
> Hi all,
>
> I've made st ~10x faster on my computer. If there are no major bugs I
> will tag tip as version 0.2.
> Here's the relevant commit message:
>
> * add a timeout value (SELECT_TIMEOUT) of 20ms in the select() call
> * wait
what about disabling ctrl key when slock is running by calling xmodmap or doing
it in C? will this work? ( i know its hacky)
On Jan 22, 2012, at 19:14, Anselm R Garbe wrote:
> 2012/1/22 Hadrian Węgrzynowski :
>> I will repeat my self. Read this first:
>> http://who-t.blogspot.com/2012/01/xkb-br
On 01-22 18:06, Anselm R Garbe wrote:
Having said all this, there is still another problem in slock. If you
launch a client *after* slock has taken over (like over a SSH
connection), the window will be managed and most likely appear on top
of slock (the window won't receive any input though).
2012/1/22 Hadrian Węgrzynowski :
> I will repeat my self. Read this first:
> http://who-t.blogspot.com/2012/01/xkb-breaking-grabs-cve-2012-0064.html
I did, however there should be a way to prevent similar issues from
happening anyways.
Next year someone sez press Ctrl-Alt-something this will crash
Dnia 2012-01-22, o godz. 18:30:03
Anselm R Garbe napisał(a):
> Ok, so the error handler trick doesn't work as it exceeds some x
> server threshold and then raises an XIO fatal error.
>
> I will investigate this issue further, but will need a more current X
> server first ;)
>
> Cheers,
> Anselm
r u using the multiply key from the numpad?
On Jan 22, 2012, at 18:30, Anselm R Garbe wrote:
> On 22 January 2012 18:25, Roman Z. wrote:
>>> On 21 January 2012 01:13, Bjartur Thorlacius wrote:
Ţann fös 20.jan 2012 23:42, skrifađi Rob:
>
> On Fri, Jan 20, 2012 at 07:01:22PM +,
On 22 January 2012 18:25, Roman Z. wrote:
>> On 21 January 2012 01:13, Bjartur Thorlacius wrote:
>> > Ţann fös 20.jan 2012 23:42, skrifađi Rob:
>> >>
>> >> On Fri, Jan 20, 2012 at 07:01:22PM +, Bjartur Thorlacius wrote:
>> >> Surely it just destroys the window, you can't get a PID for any X
> On 21 January 2012 01:13, Bjartur Thorlacius wrote:
> > Þann fös 20.jan 2012 23:42, skrifaði Rob:
> >>
> >> On Fri, Jan 20, 2012 at 07:01:22PM +, Bjartur Thorlacius wrote:
> >> Surely it just destroys the window, you can't get a PID for any X
> >> window,
> >> since it could be a networked
On 21 January 2012 01:13, Bjartur Thorlacius wrote:
> Þann fös 20.jan 2012 23:42, skrifaði Rob:
>>
>> On Fri, Jan 20, 2012 at 07:01:22PM +, Bjartur Thorlacius wrote:
>> Surely it just destroys the window, you can't get a PID for any X
>> window,
>> since it could be a networked one
>>
>
> As
I don't have an xorg.conf and don't know what an rc.d is.
I use ctrl-alt-backspace a lot, and as I live in a democratic country
I don't think I can be forced to start X with exec either.
On 22.01.2012, pancake wrote:
> ctrl+alt+backspace is not enabled by default. remove your xorg.conf an
> you'l
ctrl+alt+backspace is not enabled by default. remove your xorg.conf an you'll
enjoy it.
this is the reason why X must be started with exec or from rc.d. this way.
ctrl+alt+bs doesnt gives you a shell.
this ctrl+alt+multiple thingy looks evil. who the hell needs to do this? and
more to say.. wh
Give me a break. Our eyes need to rest, too. Stop coding everyone.
(I will from now on only troll on Sundays, thanks for your patience)
Slock sucks less, with a bit of luck next release will even survive
the destruction of our planet.
26 matches
Mail list logo
