On Mon, Feb 04, 2019 at 05:37:59PM +0100, Hiltjo Posthuma wrote:
> When the initial version is ready and some (old and) new bugs are squashed it
> will be posted for review ofcourse.
Did you happen to fix the bug where UTF-8 sequences could be broken by
the ellipsis logic in drw_text?
Eric
I would say give it a try. After using the same window manager for a
long time, I switched to dwm. I tried just about every window manager
(ok, probably not true since there are so many obscure ones) but always
went back to my favourite. dwm was the only one that stuck and was a
big change for me.
> > **I've been using Openbox for several years. Is it worth switching to
> > dwm?**
It's completely free to try out. Give it a go.
If you like tiling, I'd recommend giving a manual tiler a go as well. I use i3.
> **I've been using Openbox for several years. Is it worth switching to
> dwm?**
Yes.
> I'm mostly keyboard guy so my crucial functionality is to use keyboard
> shortcuts to: run particular program, switch desktops, switch windows,
> move them, resize, resize half-screen (vertically and horizont
Hi.
I've been here for a while, mostly because of surf. And in general I like
"suckless" approach. But well, I've got a question about dwm. To make it
short:
**I've been using Openbox for several years. Is it worth switching to
dwm?**
I'm mostly keyboard guy so my crucial functionality
Does that mean that some kind of simple fallback mechanism will be implemented?
A bit like Lemonbar allowing to specify multiple X fonts.
On Mon, 4 Feb 2019 19:56:33 +
sylvain.bertr...@gmail.com wrote:
Dear Sylvain,
> On Mon, Feb 04, 2019 at 08:03:56PM +0100, Laslo Hunhold wrote:
> > echo -n -e "GET / HTTP/1.1\r\nHost: localhost\r\n\r\n" | \
>
> "My 2c": I would prefer shell "printf" than "echo -n -e"
yeah, good point. An
Hi Laslo,
04.02.2019, 22:04, "Laslo Hunhold" :
> It is very simple really. Let me give you an example with quark and
> nc(1) (You will need Netcat OpenBSD for the -U flag, which is available
> in all package sources I know).
>
> Let's first fire up quark:
>
> # quark -U uds_main -d . -l
On Mon, Feb 04, 2019 at 08:03:56PM +0100, Laslo Hunhold wrote:
> echo -n -e "GET / HTTP/1.1\r\nHost: localhost\r\n\r\n" | \
"My 2c": I would prefer shell "printf" than "echo -n -e"
--
Sylvain
On Mon, 04 Feb 2019 18:09:44 +0300
Platon Ryzhikov wrote:
Hey Platon,
> Studying quark commit history i found a note that listening on
> UNIX-domain socket was the idea behind its last rewrite.
this was one reason among others. Most importantly, the "old" quark was
heavily architectured around
On Mon, Feb 04, 2019 at 12:31:58PM +, Nick wrote:
> Quoth inasprecali:
> > Thanks for the effort. Actually, I just found out that a "historical" patch
> > exists, which seems
> > to include you as a contributor:
> > https://dwm.suckless.org/patches/historical/xft/
> > (Admittedly, I didn't kn
Hello!
Studying quark commit history i found a note that listening on UNIX-domain
socket was the idea behind its last rewrite. This led me to the following
questions:
1) how should client be organised to use server in this case?
2) which advantages does it grant and how could they be used?
My mistake, I meant "later than 6.2".
On February 4, 2019 12:31:58 PM UTC, Nick wrote:
>Quoth inasprecali:
>> Thanks for the effort. Actually, I just found out that a "historical"
>patch exists, which seems
>> to include you as a contributor:
>https://dwm.suckless.org/patches/historical/xft/
>> (
Quoth inasprecali:
> Thanks for the effort. Actually, I just found out that a "historical" patch
> exists, which seems
> to include you as a contributor:
> https://dwm.suckless.org/patches/historical/xft/
> (Admittedly, I didn't know, I started using dwm recently and I didn't bother
> looking up
Thanks for the effort. Actually, I just found out that a "historical" patch
exists, which seems
to include you as a contributor:
https://dwm.suckless.org/patches/historical/xft/
(Admittedly, I didn't know, I started using dwm recently and I didn't bother
looking up old
patches until now).
It sho
15 matches
Mail list logo