2011/11/1 Nick :
> Quoth Peter John Hartman:
...
> Task maybe-one-maybe-two: make it play nice with webkit-gtk compiled
> against gtk3. Gtk3 probably sucks less than 2, but regardless, it's
> the future of webkit-gtk. Further into the future, hopefully an EFL
> based webkit port will happen, which
On 2011-10-31 19:58, Stephen Paul Weber wrote:
> 2) Is there any way to bring a window to the front programatically
> under 2wm? I tried xdotool windowactivate and it says the window
> manager does not support that, so I tried xdotool windowraise and
> that did nothing.
If you want to con
On Tue, Nov 1, 2011 at 8:41 AM, Connor Lane Smith wrote:
> Hey,
>
> On 31/10/2011, lolilolicon wrote:
>> The idea of having more than one master windows is brilliant. The `tile'
>> layout in current hg tip basically splits the master and slave areas
>> vertically, and tiles windows in each of th
On Tue, Nov 1, 2011 at 7:36 AM, Rob wrote:
>
> I don't have much time today, or possibly tomorrow, but I'm interested
> in this patch, it sounds almost like it recurses on each sub-section of
> the total area, applying a different layout function each time, except
> it's limited to two calls, one
Hey,
2wm is very old and completely unsupported, so I doubt there are
patches like this. It would be awesome if there were a dwm 'stereo
patch', though.
cls
1) Is there anything hanging around to give 2wm a "monacle mode" equivalent?
2) Is there any way to bring a window to the front programatically under
2wm? I tried xdotool windowactivate and it says the window manager does
not support that, so I tried xdotool windowraise and that did nothing.
Hey,
On 31/10/2011, lolilolicon wrote:
> The idea of having more than one master windows is brilliant. The `tile'
> layout in current hg tip basically splits the master and slave areas
> vertically, and tiles windows in each of the two areas using a vertical
> stacking algorithm.
I'll be intere
On 31 October 2011 23:07, lolilolicon wrote:
> Indeed mfact and nmaster being members of Layout does make more sense, and
> I made a patch which includes this change.
> Note that this may seem to add some SLOCs, but it actually reduces the
> amount of code required to implement the same layouts by
Quoth Connor Lane Smith:
> ... because it clashes with the developers' CSS. That's the problem. I
> think there ought to be pure style-free semantic HTML, and then users
> can style every site to fit their personal needs, without it resulting
> in ugly. Unfortunately people take the opportunity to
Quoth Peter John Hartman:
> Task One: Make it play nice with webkit-gtk 1.6.1 (which it doesn't; 1.4.2
> is as high as you can get.)
Task maybe-one-maybe-two: make it play nice with webkit-gtk compiled
against gtk3. Gtk3 probably sucks less than 2, but regardless, it's
the future of webkit-gtk.
On Tue, Nov 1, 2011 at 12:11 AM, lolilolicon wrote:
>
> Actually, `apply_lt` can be removed, since `apply_mslts` does the same
> thing when nmaster == 0. I'm thinking of making nmaster a member of
> the Layout structure, instead of the current Monitor. This way, we can
> make all windows slaves
Adapting the makefile to link against gtk3 shouldnt be dramatic. At some point
gtk2 will be like gtk1. And having two versions of the same lib sucks.
Im not using surf actually, but i find it nice to keep it in suckless. X11 is a
huge dep for dwm and this is not a reason to kill it :P
On 31/10/
On 31 October 2011 16:41, Jonathan Slark wrote:
> Thinking about it what I don't like about CSS is that the majority of the
> web has a white background. Yes, you can try and use custom CSS but then
> most of the web then looks ugly.
... because it clashes with the developers' CSS. That's the pr
On 31 October 2011 21:35, Nico Golde wrote:
> While this looks way more simple and sane I want to keep the behaviour for the
> -h command line switch as it's kinda expected to work with most programs.
If you don't check for '-h' it will still enter the switch and hit
default, resulting in usage()
On 31/10/2011 15:25, Connor Lane Smith wrote:
Roff is actually one of the ugliest markup languages I have ever seen.
HTML is actually pretty decent if you think about it. It's
(more-or-less) XML, which isn't nice, but I'd take that over roff any
day. Anyway, the main problem with the web is the o
Hi,
* Connor Lane Smith [2011-10-31 21:05]:
> On 31 October 2011 20:33, Nico Golde wrote:
> > Sorry for the late response, missed this thread. I'm still maintaining and
> > using it. So do some other people who occasionally contact me.
>
> Could you please apply the attached sanity patch? There
On Mon, Oct 31, 2011 at 4:21 PM, Anthony Martin wrote:
> This is just a side effect of having to
> deal with X11 on Unix and not something
> intrinsically difficult about 9P.
imo it's specifically about libixp: if the OS provides 9p interfaces
to use, that's one thing, but having to build them y
Anselm R Garbe once said:
> It is also noteworthy to remember that I actually
> started dwm development *mainly* because I came
> to the conclusion that libixp or 9P in general
> makes it extraordinary more complex to write a
> simple tool like a window manager for no really
> good reason.
This i
On 31 October 2011 20:33, Nico Golde wrote:
> Sorry for the late response, missed this thread. I'm still maintaining and
> using it. So do some other people who occasionally contact me.
Could you please apply the attached sanity patch? There are a few
strange bits in the source.
Thanks,
cls
diff
Am 31.10.2011 um 20:34 schrieb Peter John Hartman :
> On Mon, Oct 31, 2011 at 12:45:02PM -0600, Jeremy Jackins wrote:
>>> The current list of unclear removal candidates is:
>>>
>>> * surf (seems dead, please shout if you disagree or if anyone wants to
>>> take this on, it doesn't make sense if i
On Mon, Oct 31, 2011 at 08:39:00PM +0100, Joerg Zinke wrote:
>
> Am 31.10.2011 um 14:35 schrieb Peter John Hartman
> :
>
> >>> * surf (seems dead, please shout if you disagree or if anyone wants to
> >>> take this on, it doesn't make sense if it is not maintained, as
> >>> webkitgtk carries away
On Mon, Oct 31, 2011 at 08:33:05PM +0100, Nico Golde wrote:
> * Anselm R Garbe [2011-10-31 11:02]:
> > On 31 October 2011 10:43, Connor Lane Smith wrote:
> > > On 31 October 2011 08:38, Anselm R Garbe wrote:
> > >> The current list of unclear removal candidates is:
> > >>
> > >> * ii (Nion, are
Am 31.10.2011 um 14:35 schrieb Peter John Hartman :
>>> * surf (seems dead, please shout if you disagree or if anyone wants to
>>> take this on, it doesn't make sense if it is not maintained, as
>>> webkitgtk carries away)
Shout!
>> I wouldn't mind taking maintainership of Surf, if necessary.
Hi,
* Anselm R Garbe [2011-10-31 11:02]:
> On 31 October 2011 10:43, Connor Lane Smith wrote:
> > On 31 October 2011 08:38, Anselm R Garbe wrote:
> >> The current list of unclear removal candidates is:
> >>
> >> * ii (Nion, are you still maintaining it?)
> >
> > I disagree with this on the basis
On Mon, Oct 31, 2011 at 12:45:02PM -0600, Jeremy Jackins wrote:
> > The current list of unclear removal candidates is:
> >
> > * surf (seems dead, please shout if you disagree or if anyone wants to
> > take this on, it doesn't make sense if it is not maintained, as
> > webkitgtk carries away)
> > *
On 31 October 2011 20:28, Connor Lane Smith wrote:
> Also, having special
> 'set' bindings instead of the simple I-to-Increase, D-to-Decrease, is
> far harder to remember.
An afterthought: if it's the number of bound keys which is worrying
you, why not make, e.g., Mod-n increase nmaster, and Mod-
On 31 October 2011 10:01, Anselm R Garbe wrote:
> That's why I asked what the usual non-default ncol settings are, I
> guess nearly no one exceeds 3 colums.
>
> So in other words, if we can say tha majority use cases are:
>
> nmaster: 1-2
I honestly think removing incnmaster for some 'setnmaster'
> The current list of unclear removal candidates is:
>
> * surf (seems dead, please shout if you disagree or if anyone wants to
> take this on, it doesn't make sense if it is not maintained, as
> webkitgtk carries away)
> * ii (Nion, are you still maintaining it?)
I'm fine with the other ones, but
> So in other words, if we can say tha majority use cases are:
>
> nmaster: 1-2
> ncol (slave cols): 1-2
Hm, so are we no longer considering bstack? I agree that mod-shift-t
would be a nice way to do nmaster=2, but this means that with more
than two windows I'm stuck a stack on the side and I've l
On Mon, 31 Oct 2011 15:25:48 +
Connor Lane Smith wrote:
>
> Roff is actually one of the ugliest markup languages I have ever seen.
> HTML is actually pretty decent if you think about it. It's
> (more-or-less) XML, which isn't nice, but I'd take that over roff any
> day. Anyway, the main probl
On Mon, Oct 31, 2011 at 12:32 PM, Bjartur Thorlacius
wrote:
> If someone wants to write ugly code we can't stop him. But what's
> wrong with supporting handwritten HTML documentation?
> I'm not proposing using autogenerated HTML recursively populated with
> divs by JavaScript. The only argument in
With regards to ii,
> The problem imho is usability. Maybe some shellscripts or rcscripts can help
> here..
>
> Iirc there was a program that was reading one line at the bottom and writing
> to a pipe and getting the output of another pipe into the other part of the
> screen. Like irssi/bx does
On 10/31/11, Christoph Lohmann <2...@r-36.net> wrote:
> »And as long as the markup is terse« is a never fulfilled requirement.
> But surely, extending roff with runtime shellscripts will extend its
> usefulness. It's like Qt vs. plain C – redundancy vs. lean code.
>
If someone wants to write ugly c
On Mon, Oct 31, 2011 at 10:19 PM, Thomas Dahms wrote:
>
> That looks interesting. I have one suggestion for a simplification:
> I guess you can get rid of the functions combining the master and
> slave layouts by modifying setlayout() to take three arguments (the
> two layouts and the direction of
Greetings.
On 31.10.2011 15:57, Bjartur Thorlacius wrote:
> On Mon, 31 Oct 2011 09:34:10 -, Christoph Lohmann <2...@r-36.net> wrote:
>> Martin Kopta wrote:
>>> Proposal: 6. It has useful documentation.
>>
>> Now bureaucracy begins. What documentation? A manpage should suffice,
>> when it reach
On 31 October 2011 14:57, Bjartur Thorlacius wrote:
> There's nothing wrong with HTML documentation per se, and it sure is not
> worse than ASCII. Why do you believe roff is better than HTML? Just pipe the
> markup through htmlfmt(1) or html2text(1) if you like reading documentation
> on terminal
On Mon, Oct 31, 2011 at 10:57 AM, Bjartur Thorlacius
wrote:
> There's nothing wrong with HTML documentation per se, and it sure is not
> worse than ASCII. Why do you believe roff is better than HTML? Just pipe the
> markup through htmlfmt(1) or html2text(1) if you like reading documentation
> on t
Markdown is the only decent option for documentation. A part from a .docx
On 31/10/2011, at 15:57, "Bjartur Thorlacius" wrote:
> On Mon, 31 Oct 2011 09:34:10 -, Christoph Lohmann <2...@r-36.net> wrote:
>> Martin Kopta wrote:
>>> Proposal: 6. It has useful documentation.
>>
>> Now bureaucrac
On Mon, 31 Oct 2011 09:34:10 -, Christoph Lohmann <2...@r-36.net> wrote:
Martin Kopta wrote:
Proposal: 6. It has useful documentation.
Now bureaucracy begins. What documentation? A manpage should suffice,
when it reaches 1.0. I think it's already sucking, if a project really
needs a webbro
2011/10/31 lolilolicon :
> On Mon, Oct 31, 2011 at 9:49 PM, lolilolicon wrote:
>>
>> The code is in the attachment.
>>
>
> *huge facepalm*
>
> Forgot to attach the fixed code. Attached here.
>
That looks interesting. I have one suggestion for a simplification:
I guess you can get rid of the func
On Mon, Oct 31, 2011 at 9:49 PM, lolilolicon wrote:
>
> The code is in the attachment.
>
*huge facepalm*
Forgot to attach the fixed code. Attached here.
typedef struct {
int x, y, w, h;
} Booth;
static void apply_lt(Monitor *m, void (*ltf)(Client **, Booth *, unsigned int));
static void apply
The idea of having more than one master window is brilliant. The `tile'
layout in current hg tip basically splits the master and slave areas
vertically, and tiles windows in each of the two areas using a vertical
stacking algorithm. The `ncol' layout does it slightly differently by
tilling the ma
On Mon, Oct 31, 2011 at 08:44:01AM -0500, Stanley Lieber wrote:
> On Mon, Oct 31, 2011 at 8:41 AM, Jonathan Slark
> wrote:
> > On 31/10/2011 13:33, Kurt H Maier wrote:
> >>
> >> No, it then becomes a pain in the ass for experts, because you get
> >> hundreds of illiterate assholes storming mailing
On Mon, Oct 31, 2011 at 8:41 AM, Jonathan Slark
wrote:
> On 31/10/2011 13:33, Kurt H Maier wrote:
>>
>> No, it then becomes a pain in the ass for experts, because you get
>> hundreds of illiterate assholes storming mailing lists and irc
>> channels
>
>
>
> We have literate assholes on the lists i
On 31/10/2011 13:33, Kurt H Maier wrote:
No, it then becomes a pain in the ass for experts, because you get
hundreds of illiterate assholes storming mailing lists and irc
channels
We have literate assholes on the lists instead...
On Mon, Oct 31, 2011 at 12:42:19PM +0100, Troels Henriksen wrote:
> Anselm R Garbe writes:
>
> > * surf (seems dead, please shout if you disagree or if anyone wants to
> > take this on, it doesn't make sense if it is not maintained, as
> > webkitgtk carries away)
>
> I wouldn't mind taking maint
On Mon, Oct 31, 2011 at 7:45 AM, wrote:
> Putting elitism and relevance in the same line just doesn't make sense
> -- consider following: by chance, hundreds thousands of non-expert users
> discover the beauty of dwm through some end-user-friendly distro and
> overnight it's not only used by expe
What's really amazing about zimbra is that it overloads the server and
then sends so much javascript down the pipe that it overloads the
client too. I think they call that "vertical integration"
--
# Kurt H Maier
The problem imho is usability. Maybe some shellscripts or rcscripts can help
here..
Iirc there was a program that was reading one line at the bottom and writing to
a pipe and getting the output of another pipe into the other part of the
screen. Like irssi/bx does but non monolitic and logging i
The idea of having more than one master windows is brilliant. The `tile'
layout in current hg tip basically splits the master and slave areas
vertically, and tiles windows in each of the two areas using a vertical
stacking algorithm. The `ncol' layout does it slightly differently by
tilling the m
Connor Lane Smith writes:
> On 31 October 2011 12:27, Krnk Ktz wrote:
>> What should be done about ii? Are there features requests? I mean, it is a
>> great concept and works very well as it is, doesn't it?
>
> It works well, but the source could do with a little cleaning up.
> There are some we
On 31 October 2011 12:27, Krnk Ktz wrote:
> What should be done about ii? Are there features requests? I mean, it is a
> great concept and works very well as it is, doesn't it?
It works well, but the source could do with a little cleaning up.
There are some weird things, like fprintf(stderr, "%s"
>> For ii it is just a question of maintenance.
What should be done about ii? Are there features requests? I mean, it is a
great concept and works very well as it is, doesn't it?
* Anselm R Garbe [2011-10-31 12:51]:
> On 31 October 2011 12:45, wrote:
> > -- consider following: by chance, hundreds thousands of non-expert users
>
> This scenario is very unlikely,
I agree, not the best example. My remark was not of great practical
relevance, I know.
That aside, many th
On 31 October 2011 12:45, wrote:
> * Anselm R Garbe [2011-10-31 10:12]:
>> I'm working on such guidelines. The main aspects are:
>>
>>
>> 1. Relevance/Elitism: the project must be relevant in the context of
>> suckless.org's target audience, it must target expert
>> users/developers/administrato
* Anselm R Garbe [2011-10-31 10:12]:
> I'm working on such guidelines. The main aspects are:
>
>
> 1. Relevance/Elitism: the project must be relevant in the context of
> suckless.org's target audience, it must target expert
> users/developers/administrators and _not_ typical end users.
Putting
On Mon, 31 Oct 2011 10:11:28 +0100
Anselm R Garbe wrote:
> 3. Quality: the project must aim to be a quality finished product once
> exceeding the 1.0 version number and be maintained afterwards.
> Unmaintained projects will be removed after a grace period of one
> year.
those kind of version num
Anselm R Garbe writes:
> * surf (seems dead, please shout if you disagree or if anyone wants to
> take this on, it doesn't make sense if it is not maintained, as
> webkitgtk carries away)
I wouldn't mind taking maintainership of Surf, if necessary. I'm
already maintaining an off-tree fork with
On 31 October 2011 12:14, Connor Lane Smith wrote:
> On 31 October 2011 10:59, Aurélien Aptel wrote:
>> I also think libixp and ii should stay. I don't use them personally
>> but I think they follow the suckless philosophy.
>
> ii does, but since 2007 the originally suckless libixp has been
> blo
On 31 October 2011 10:59, Aurélien Aptel wrote:
> I also think libixp and ii should stay. I don't use them personally
> but I think they follow the suckless philosophy.
ii does, but since 2007 the originally suckless libixp has been
bloated up alongside wmii. The repository includes *broken*
auto
I agree with libixp and ii staying.
mkopta
On 10/31/2011 11:59 AM, Aurélien Aptel wrote:
On Mon, Oct 31, 2011 at 9:38 AM, Anselm R Garbe wrote:
* skvm (who uses this? development seems dead)
I use it. I installed it 1 or 2 years ago, never bothered to update it
since it works.
I also think
On Mon, Oct 31, 2011 at 9:38 AM, Anselm R Garbe wrote:
> * skvm (who uses this? development seems dead)
I use it. I installed it 1 or 2 years ago, never bothered to update it
since it works.
I also think libixp and ii should stay. I don't use them personally
but I think they follow the suckless p
On 10-31 10:26, Pierre Chapuis wrote:
The touch command under OS X Lion (44,016 bytes).
42200 /usr/local/bin/dwm
--
ilf
Über 80 Millionen Deutsche benutzen keine Konsole. Klick dich nicht weg!
-- Eine Initiative des Bundesamtes für Tastaturbenutzung
signature.asc
Description
On 2011-10-31 10:49, pancake wrote:
> I dont understand the point of documentation.
Neither do I, so let's triage:
Deviation from Convention
served by README
Commentary on the Code
served by IRC, mailing list
What is this? How do I?
bless some wiki/forum someplace as *th
On 31 October 2011 10:00, Anselm R Garbe wrote:
> The current approach of having a README and a manpage is enough. If
> someone needs additional info, there is the wiki.
Oh, I'm not suggesting we package extra documentation *with* dwm, only
that we improve the documentation on the wiki. It really
On 31 October 2011 10:43, Connor Lane Smith wrote:
> On 31 October 2011 08:38, Anselm R Garbe wrote:
>> The current list of unclear removal candidates is:
>>
>> * ii (Nion, are you still maintaining it?)
>
> I disagree with this on the basis that it's an interesting program. If
> need be I can ma
I dont understand the point of documentation.
If config/compile/install/uninstall must be documented we have a problem.
The target users we expect should be smart enought to read the source in case
of doubt. But comments in config.h should be clear enought to not allow users
to fall in c.
On 3
Jfyi. I added support for creating tiny binaries with r2 a while ago. So it
will be easy to create a 200 bytes elf/pe/mach0. For touch, true.. Written in
assembly or r_egg (a compiler im writing to create relocatable binaries)
For C... tcc is an option.
On 31/10/2011, at 10:28, Anselm R Garbe
On 31 October 2011 08:38, Anselm R Garbe wrote:
> The current list of unclear removal candidates is:
>
> * ii (Nion, are you still maintaining it?)
I disagree with this on the basis that it's an interesting program. If
need be I can maintain it.
On 31 October 2011 09:34, Christoph Lohmann <2...@
README and manpage should be enough. The README should answer "What it
is", "What it is good for", "How to
compile/install/uninstall/configure/..", "Who is responsible" and
manpage should answer "How to use it". But I am probably all wrong.
mkopta
On 10/31/2011 10:34 AM, Christoph Lohmann wro
Greetings.
Martin Kopta wrote:
> Proposal: 6. It has useful documentation.
Now bureaucracy begins. What documentation? A manpage should suffice,
when it reaches 1.0. I think it's already sucking, if a project really
needs a webbrowser to be opened for the documentation.
Sincerely,
Christoph Lo
>From their web site it's main task seems to be being sophisticated.
Such software can exist on it's own without purpose, although theists
may find joy in thinking about it.
On 31 October 2011 10:26, Pierre Chapuis wrote:
> There is probably no need to remind you how software
> bloat increases with time, but I found this particularly
> striking:
>
> The entire Turbo Pascal 3.02 executable--the compiler and
> IDE--was 39,731 bytes. Here are some things that Turbo Pasca
I like how a lot of javas are run by root.
rm `which bash` `which java`; reboot
On 31 October 2011 10:19, hiro <23h...@googlemail.com> wrote:
>> proper language. We only accept C and Go at the moment.
>
> So rc is not good enough?
It is, but an exception for a suckless.org project I think. I don't
expect many rc only based projects.
>> Unmaintained projects will be removed a
There is probably no need to remind you how software
bloat increases with time, but I found this particularly
striking:
The entire Turbo Pascal 3.02 executable--the compiler and
IDE--was 39,731 bytes. Here are some things that Turbo Pascal
is smaller than, as of October 30, 2011:
[...]
The touc
> proper language. We only accept C and Go at the moment.
So rc is not good enough?
> Unmaintained projects will be removed after a grace period of one year.
What if it doesn't need to be maintained?
> 5. Exclusivity: the project must be unique, i.e. it should not solve a
problem that is solv
Proposal: 6. It has useful documentation.
On 10/31/2011 10:11 AM, Anselm R Garbe wrote:
On 31 October 2011 10:01, Martin Kopta wrote:
Are there any explicit rules which project must follow in order to be part
of suckless? What is the line in here?
I'm working on such guidelines. The main asp
On 31 October 2011 10:14, hiro <23h...@googlemail.com> wrote:
> Come on Anselm, why so many words when one would suffice: ovulation
Haha, nice one ;)
-Anselm
Come on Anselm, why so many words when one would suffice: ovulation
On 31/10/11 10:00am, Christoph Lohmann wrote:
> Greetings.
>
> Džen wrote:
> > [...]
>
> This looks like a cloud-based multi-threaded Hello World in Java. Am
> I right?
:D
I wish I knew what the fuck it is doing. Maybe indexing mail...
--
Džen
2011/10/31 Anselm R Garbe :
> That's why I asked what the usual non-default ncol settings are, I
> guess nearly no one exceeds 3 colums.
>
> So in other words, if we can say tha majority use cases are:
>
> nmaster: 1-2
> ncol (slave cols): 1-2
To avoid confusion: the ncol layout that I use has col
On 31 October 2011 10:01, Martin Kopta wrote:
> Are there any explicit rules which project must follow in order to be part
> of suckless? What is the line in here?
I'm working on such guidelines. The main aspects are:
1. Relevance/Elitism: the project must be relevant in the context of
suckless
Greetings.
Džen wrote:
> Stumbled upon this output of top on a machine running zimbra, though it
> would be fun to share:
>
> top - 09:49:52 up 13 days, 20:48, 1 user, load average: 61.73, 61.67, 61.71
> Tasks: 538 total, 1 running, 537 sleeping, 0 stopped, 0 zombie
> Cpu(s): 16.6%us, 83.
Are there any explicit rules which project must follow in order to be
part of suckless? What is the line in here?
thanks, mkopta
On 10/31/2011 09:38 AM, Anselm R Garbe wrote:
On 30 October 2011 22:51, Jeremy Jackins wrote:
First I want many projects removed from suckless.org, only the real k
On 31 October 2011 09:50, Thomas Dahms wrote:
> 2011/10/31 Anselm R Garbe :
>> Ok, if the majority rarly increases nmaster to 3, I would suggest the
>> approach to have setnmaster() rather than incnmaster(). Then one could
>> define:
>>
>> Mod1-t: setnmaster(1); setlayout(tile);
>> Mod1-Shift-t: s
Stumbled upon this output of top on a machine running zimbra, though it
would be fun to share:
top - 09:49:52 up 13 days, 20:48, 1 user, load average: 61.73, 61.67, 61.71
Tasks: 538 total, 1 running, 537 sleeping, 0 stopped, 0 zombie
Cpu(s): 16.6%us, 83.4%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.
2011/10/31 Anselm R Garbe :
> Ok, if the majority rarly increases nmaster to 3, I would suggest the
> approach to have setnmaster() rather than incnmaster(). Then one could
> define:
>
> Mod1-t: setnmaster(1); setlayout(tile);
> Mod1-Shift-t: setnmaster(2); setlayout(tile);
What about some people
On 31 October 2011 09:39, Thomas Dahms wrote:
> 2011/10/31 Anselm R Garbe :
>> So after having clarified the question about if you'd change nmaster
>> dynamically, I'd like to clarify this
>>
>> question:
>>
>> --> What is your typical range of nmaster in reality? Is it just 1-2
>> or even 1-3 or
2011/10/31 Anselm R Garbe :
> So after having clarified the question about if you'd change nmaster
> dynamically, I'd like to clarify this
>
> question:
>
> --> What is your typical range of nmaster in reality? Is it just 1-2
> or even 1-3 or more?
I use ncol with nmaster=2 most of the time. On sm
On 30 October 2011 22:51, Jeremy Jackins wrote:
>> First I want many projects removed from suckless.org, only the real key
>> projects should survive. I plan to set up suckmore-graveyard.org or something
>> similar in a couple of weeks to allow for an archive of those non fitters, as
>
> Aside fro
On 30 October 2011 23:02, pancake wrote:
> When nmaster was released I was a heavy user of it.. And definitively when I
> stopped using it I didnt really miss it.
Same here. My current tendency is skipping nmaster in vanilla dwm in
favor for rather bstack and perhaps ncol. I find it really
conce
On 31 October 2011 05:42, Jeremy Jackins wrote:
>> keybinding), so increasing nmaster and moving that window into the
> s/increasing/decreasing/
Is it correct that you'd decrease to nmaster=0?
Anyhow, I more and more believe that incnmaster is the only sensible
approach, at least it has a clear
93 matches
Mail list logo
