This patch makes X draw window borders offscreen, so that you see
|
|
|
|
|
instead of
++
| ||
| ||
| ||
| ||
| ||
++
I find the outside borders to be a bit jarring when in black-
I evaluated this border style some time ago. And I must say I still
prefer the original behavior of dwm. The problem about you're
borderstyle is, that my brain needs more time to identify the selected
window. Also I don't use resizehints, as some clients really start to
fuck up if it's set to
- shows all windownames in the statusbar (this is nice for the
maximized layout, as you wouldnt see there are multiple windows on
that tag otherweise). that stuff is a little bit messy, id like to
see suggestions how to make that better. it uses a defined maximum
length for the title, and
Any help would be appreciated, and also how could i do the same
without using threads?
This seems to work fine for me...
--- a/dwm.c Thu Jul 03 17:05:56 2008 +0100
+++ b/dwm.c Fri Jul 11 00:26:08 2008 -0700
@@ -1313,11 +1313,28 @@ setmfact(const Arg *arg) {
arrange();
}
Attached is a slightly different implementation of the fibonacci()
function that respects `mfact' for the master window [and lets you
resize your master window with M-j M-k] This worked under hg tip
(1314). Comments, insights welcome. --Madhu
--snip--
Here's one that uses 'mfact' throughout.
@pancake :
I dont see any point for having a function called
dwmiinoinfiniteloop
Well this function is necessary, I didn't know how to call it,
though its name is relevant... If you don't like its name feel free
to change it but I won't. The important thing is that it does its job.
I
On Aug 7, 2008, at 12:35 AM, Sander van Dijk wrote:
On 8/6/08, Donald Chai [EMAIL PROTECTED] wrote:
I have the inside border
set up to follow resize hints (this packs more text onscreen if my
display's number of rows is not a multiple of 3). The outside border
does not follow resize hints
What about the ability to run different dvtm instances on different
virtual terminals that share a common session?
This could be seen as the tag/workspace concept. You could detach a
window on /dev/tty1 and reattach it in your other dvtm on /dev/tty3.
The only thing that comes to my mind is
Hi, the following two patches add support for a scrollback buffer and
enhanced color in dvtm.
scrollback:
- Simply set up some keybinding to scrollback(), passing in -1 or
1 to scroll up or down.
256color:
- Allows the use of nice VIM color schemes
- Ncurses doesn't allow more
On Aug 28, 2008, at 1:12 PM, Maxim Vuets wrote:
The reason for the built-in status bar is simplicity. In theory it
would be
possible to externalize it, but then you would end up with adding
some
kind of command interface to dwm to aim the mouse interaction from
the bar. In the end
Thanks for the patches, scrollback is probably the most requested
dvtm feature. You introduced a separate buffer for the scrollback
data, did you consider allocating more space for the main buffer and
just adjusting the scroll_{top,bot} pointers and using them in
madtty_draw to draw only the
- tags/workspaces are a straightforward addition to dvtm, since it
was
derived from dwm. (I have it mostly working for myself, but I had
to rip
out a lot of dvtm-specific things like 'minimize')
Why had you to rip out these things? There is a git branch which
should mostly work but i so far
- The implementation of tagging is contrary to the suckless
philosophy:
http://www.suckless.org/common/
I agree, however this is because the various functions take char*
arrays
instead of an Arg union. This makes it impossible to specify bit
masks.
We could of course change this but it
Hi!
The current arrange() procedure hides and shows windows in the order
specified by clients. This causes a lot of flicker and unnecessary
screen redraws when there are many overlapping windows whose stacking
order is different from clients, i.e. when using monocle or
floating layouts.
I have found something quite useful when working with lot of terminals
that is having different background colors depending on the task they
are designed to be. But currently i just change the background
color of
vim and use this to differentiate them. another stuff would be like
changing the
On Sep 6, 2008, at 1:25 AM, Anselm R Garbe wrote:
2008/9/3 Donald Chai [EMAIL PROTECTED]:
I'm sure there might be other problems I created...I don't
understand the
X11 event model at all.
Yes you did. It is important to showhide() before focus and restack
handling. I also slightly changed
On Sep 8, 2008, at 2:09 AM, Anselm R Garbe wrote:
2008/9/8 Donald Chai [EMAIL PROTECTED]:
Actually, this is a totally unrelated problem. The problem is that
XGrabKeyboard generates focus events (XGrabKeyboard is called by
the X
server after establishing the passive grab with XGrabKey).
So
On Sep 11, 2008, at 8:14 PM, bill lam wrote:
On Thu, 11 Sep 2008, Donald Chai wrote:
I tried adding pango+xft support because bitmap CJK fonts suck,
and also
Sorry for my ignorance. The chinese font on my FF3 now looks ugly
while it previously looks quite good using ukai under gnome. Does
On Sep 11, 2008, at 9:54 PM, bill lam wrote:
On Thu, 11 Sep 2008, Donald Chai wrote:
bug. By looks ugly do you mean it's rendered with a different
font, or
that the font is improperly rendered?
look like 15x16 character printed on an old dot-matrix printer.
I've checked with rxvt-unicode
On Sep 12, 2008, at 1:38 AM, Antoni Grzymala wrote:
Donald Chai dixit (2008-09-11, 22:34):
Just specify multiple font patterns in config.h, separated by commas:
static const char font[] =
-*-fixed-medium-r-normal-*-12-*-*-*-*-*-*-*,-*-ukai-*-r-normal--*-
*-*-*-*-*
;
What does
On Sep 16, 2008, at 9:16 AM, [EMAIL PROTECTED] wrote:
--snip--
The best way to cope with this seems to me to be a key binding for
switching on/off grabbing MOD in dwm. Say, MOD-g, like in
- MOD-3 // goto tag 3, where the dvtm terminal is running
- MOD-G // stop grabbing MOD
-
On Sep 23, 2008, at 2:55 AM, bill lam wrote:
Hello,
I want to set java programs to float in config.h, Does anyone know
what the classname of sun java/openjdk java as that reported by
XGetClassHint?
You can get classnames (and other useful information) using the
'xprop' program.
On Sep 26, 2008, at 12:00 AM, Claudio wrote:
Your version of the function works properly, it's better to use
array of integers, indeed, and the focus is now under control.
Though i don't want to toggle the window floating automatically and
i prefer to check for arg and arg-v before to use
On Sep 28, 2008, at 6:50 AM, bill lam wrote:
On Sat, 27 Sep 2008, Donald Chai wrote:
On Sep 27, 2008, at 5:26 AM, Tinou wrote:
awesomewm (and my dwm) move windows within the clients list instead
of
turning on 'floating', and I very much prefer it that way.
Interesting feature, could you
On Sep 28, 2008, at 12:37 PM, Valentin wrote:
Hi,
can somebody tell me how to change the latest grid layout patch to put
the clients in two columns and one row instead of two rows and one
column when there are only two clients in a tag? [1] The current
way of
doing it isn't very nice on
On Sun, Sep 28, 2008 at 4:26 PM, Claudio [EMAIL PROTECTED] wrote:
It's a more logical and useful approach, indeed. Though i rarely use layouts
other than monocle. Since i use dvtm i don't have more than a terminal in a
tiled tag anymore but all the terminals has been moved to one dvtm session
On 9/28/08, Carlos Pita [EMAIL PROTECTED] wrote:
I use a vanilla dwm, without any layout per tag facility. I like it
this way but still some clients are cumbersome to manage.
Which version of dwm?
For example fluid, the gui designer for fltk, which follows the gimp
and gaim ugly paradigm of
On Wed, Oct 8, 2008 at 4:44 PM, Charlie Kester [EMAIL PROTECTED] wrote:
I assume the question concerns the new scripting support in dvtm.
Originally I was excited by the addition of this feature and downloaded
the tip right away.
But since then, I've scarcely used it.
So I won't object if
On Oct 10, 2008, at 1:36 AM, Marc Andre Tanner wrote:
On Wed, Oct 08, 2008 at 05:44:31PM -0700, Donald Chai wrote:
On Wed, Oct 8, 2008 at 4:44 PM, Charlie Kester
[EMAIL PROTECTED] wrote:
I assume the question concerns the new scripting support in dvtm.
Originally I was excited
On Wed, Nov 5, 2008 at 1:39 AM, Anselm R Garbe [EMAIL PROTECTED] wrote:
Ok, are there any concerns making this upstream again? (Yes I know, we
had this already in earlier versions, by that time it was called
togglelayout())... There were reasons for not toggling, basically it
was confusing to
On Tue, Nov 4, 2008 at 9:09 AM, Neale Pickett [EMAIL PROTECTED] wrote:
Reparenting everything to init with the double-fork is a nightmare on a
many-user machine, especially when I'm logged in more than once. pstree
becomes useless. This sets up a SIGCHLD handler and only forks once.
Adds 2
On Dec 6, 2008, at 10:20 AM, Guillaume Quintin wrote:
Why don't we change the way dwm gets its status text ? For example
we could use the SIGALRM signal to call a spawn2 :
--snip--
This will take only a few LOC, because all the reading p[0] part
will be in fact the reading-stdin code from
On Dec 6, 2008, at 1:02 PM, Guillaume Quintin wrote:
This is a little very basic patch that does what I asked above. I
tried
this using the SIGALRM signal but I randomly got fatal errors about
memory (un)locks.
Your code looks like an idle loop; I recommend you read the man page
for
On Dec 6, 2008, at 10:32 PM, Amit Uttamchandani wrote:
On Sun, 7 Dec 2008 01:14:45 -0500
Jeremy Jay [EMAIL PROTECTED] wrote:
If you are using a recent version of xorg, and don't have your screen
resolution hardcoded in xorg.conf, it should be autodetected. For
example, the last time I had
On Dec 10, 2008, at 9:05 AM, Johannes Wegener wrote:
is there anybody who has experience with dwm and dualhead setups? I
tried to use dwm with a xrandr dualhead but it seemed quite useless
becouse I
could just drag floating windows into the second screen. Xinerama
seems
no more supported
On Dec 11, 2008, at 2:32 AM, Kai Großjohann wrote:
Anselm R Garbe wrote:
I tried different multihead approaches in between 4.9 and 5.1 with
dwm. I remember the following: [...]
You haven't mentioned my favorite approach:
Currently, each tag is visible or hidden. Change this so that a
On Jan 29, 2009, at 12:49 AM, bill lam wrote:
In commit sha1 a107d3 it added a call to an undeclared set_escdelay,
and it fails to compile. Is that a known issue?
You can replace that line with:
ESCDELAY = esc_delay;
By default, ncurses waits a long time to interpret escape
On Jan 29, 2009, at 8:54 PM, bill lam wrote:
On Thu, 29 Jan 2009, Donald Chai wrote:
You can replace that line with:
ESCDELAY = esc_delay;
Thanks!
I found 2 further issues
1. on my ubuntu, $TERM is xterm (actually it is 256 color), but dvtm
cannot detect it and makes it a 8
On Jan 30, 2009, at 6:43 AM, bill lam wrote:
On Fri, 30 Jan 2009, Donald Chai wrote:
On Jan 29, 2009, at 8:54 PM, bill lam wrote:
1. on my ubuntu, $TERM is xterm (actually it is 256 color), but
dvtm
cannot detect it and makes it a 8 (or 16?) color rxvt.
You probably need to set TERM
On May 3, 2009, at 3:12 PM, Preben Randhol wrote:
I have setup my Asus Eee to run commands when I press the function
keys
(like power up/down etc...) In these scripts I'm running notify-send
to
get a small window to give a message (like touchpad off etc...). The
scripts are run from acpid.
40 matches
Mail list logo
