Daniel Bainton writes:
> Yeah, apparently something is wrong with Marc's email host.
I'm going to guess it's because his outbound (and apparently inbound)
mail is all routed through genotec.ch, which is (obviously) not the same
string as brain-dump.org. Genotec appears to add a domain-keys head
Typically I have three windows open: Emacs and rxvt on tag 1, and
Firefox on tag 2. Emacs runs in less RAM than Firefox or what many of
you use for playing music, and it does all of the following:
Emacs: editor, chat (rcirc + bitlbee, comint), email (gnus),
rss (gnus), address book (bbdb)
Ian Daniher writes:
> Why do you want to use sic over irssi?
Maybe the guy likes a challenge :)
> irssi is pretty light...
The irssi processes on my multi-user server are currently the second
biggest memory users. Behind them are the web server, the SMTP, IMAP,
and POP3 servers, bitlbee, and
Premysl Hruby writes:
> I had saved one bounce message mlmmj received from your MX, and it
> looks like your MX is acting very strangely (bounce message attached
> to this email).
Wow, his MTA (or maybe MUA) is sending out a delivery status
notification, saying that the message was delivered. I
On 3/6/2009, "markus schnalke" wrote:
>I modified `slock' some time ago to display a fullscreen red window
>that closes on any button press. I use it to notify about low battery.
That reminds me, I used to use xrefresh for something similar.
xrefresh -solid red
If you have a fancypants gr
On 3/5/2009, "Engin Tola" wrote:
>the problem with xmessage is that it steals the focus. do you know a way
>to prevent it from doing that ?
I haven't looked into it. When my battery is at 5%, I want to be sure
I'm aware of it.
On 3/5/2009, "Neale Pickett" wrote:
> xbacklight =[some-value]
> xvattr -a XV_BRIGHTNESS -v [some-value]
While I'm thinking of it, I use xmessage to wake me up when my battery
is about to die. It has the nice advantage that if I'm not looking at
the screen that ins
xgamma just changes the gamma, which may not be noticeable on things that
are predominantly black and white. Here are a few suggestions that will
set actual brightness:
xbacklight =[some-value]
xvattr -a XV_BRIGHTNESS -v [some-value]
These may not work on all systems, but will probably work
I've fixed a bug in xss that would cause the included "magic" hack to
die after running for a few days straight. My 4-year-old daughter asked
me to explain it to her, and it's such a good explanation that you're
going to get it too.
Every time I wanted to draw a new line, I would ask for a new c
>I noticed with certain applications like Gimp, k3b, etc. it is very
>difficult to maximize a work screen--I have yet to figure it out.
As Anselm pointed out, you probably want to hold down your modifier key
(default Alt) and use mouse buttons. A "maximize" could probably be
written by raising w
On 2/17/2009, "I. Khider" wrote:
>I will say this, I love DWM though I do not completely understand it
>yet. It makes me feel like a man.
Bwahahaha. Sometimes I wonder if that's the real reason any of us use
it.
Neale "Chest Beatin'" Pickett
Evgeny Grablyk writes:
> I just downloaded dwm-5.4.1 and noticed that stdin-to-statusbar output
> mechanism was removed. Sadly, I don't seem to remember any discussion
> about that. Was there any?
Someone suggested the idea, I think in jest, and I was foolish enough to
implement it. I've been r
Folks,
May I suggest that you get into the habit of trimming your replies?
This is more important for bottom-posting, where your reply goes after
the quoted text. Scrolling up and down to follow the conversation in
the "Bottom Stack Patch" thread was mildly annoying :)
That's all, thanks for you
I'd be more inclined to consider this if dwm had ever had a problem in
the year or so I've been using it.
But if you're enamoured of the idea, here's something you can do from
your .xinitrc to get this behavior. This will work better with dwm 5.4
than with a prior version.
while ! dwm; do t
On 1/13/2009, "Frederic Chardon" wrote:
>void
>quit(const Arg *arg) {
>if (arg->i)
>execlp("dwm", "dwm", NULL);
>running = False;
>}
Here's the one I use, which can go into config.h instead, and can also
be used to launch other WMs (but why would you want to do that? ;)
void
re
Jeremy Jay writes:
> Anyways, here's my "finished" dwm status code.
Nice. I've written something very similar, but mine relies more on the
shell and having to use lots of programs. I wanted to create an
extensible tool that you could use as the foundation of a shell script
that chains lots of
Anselm,
My apologies for bringing up something which has already been discussed,
I didn't think this specific issue would have come up before!
My primary machine (a shared machine on which I don't have root access)
triggers a cache miss nearly every time with dwm_path, due to
directories being co
I theorize that find outperforms for/test. Below are two shell scripts:
if you run the first one it will let you know the results of two runs.
The second one is a modified dmenu_run that uses find. I'd appreciate
it if people would run the first one and mail the results to me. I'll
let the list
Guillaume Quintin writes:
> Neale Pickett, where are you in your investigations ? Could be X the
> problem ?
I stopped my investigation when Anselm accepted the xprop patch. Now
status scripts will be just another background process with an X
connection (like xterm), and there should
"Michael Brown" writes:
> Seems the problem has something to do with xsetroot's whitespace
> handling...
Then it's probably working like bourne shell. Observe:
$ argcount () { echo $#; }
$ argcount 1 2 3
3
$ argcount "1 2 3"
1
$ argcount $(echo 1 2 3)
3
$ argcou
Since the list is talking about slock, now might be an appropriate time
for me to mention again my xss project:
http://woozle.org/~neale/src/xss/
This provides several single-purpose programs which allow you to build a
screen locker (or just saver) with a shell script. I set mine up to
check
James Turner writes:
> After taking some time and looking at the different signal headers on
> OpenBSD only #include is required, no need to #include
> which contains additional functions.
My man page (Linux) says to #include . I don't have any of my
books nearby, nor do I have access to any
Benoit, I'm still confused about what you want. I have a "restart"
function in my config.h that also lets me start a different WM
(currently unused):
void
restart(const Arg *arg)
{
if (arg->v) {
execvp(((char **)arg->v)[0], (char **)arg->v);
} else {
execlp
I very much like this patch. I realized right away that I would never
again need to restart dwm when I work on my status script. When it
dies, I can just start it up again without restarting DWM. Someone
could even have multiple programs running to update the status text. It
removes the need fo
"Anselm R Garbe" <[EMAIL PROTECTED]> writes:
> I don't like the alternatives very much, I dislike popen() some status
> feed process, or creating a fifo, or reading from some status text
> file, or using X properties (like larsremote).
I sort of like the idea of using X properties. You could use
Guillaume Quintin <[EMAIL PROTECTED]> writes:
> But now, when I reinstall dwm-5.2 I get the same problem than in
> dwm-5.3 and dwm-5.3.1, "double-fork", "simple-fork" and
> re-"double-fork". I don't understand why.
This makes me happy, not only because my spawn function wasn't the
problem, but al
Jeremy Jay <[EMAIL PROTECTED]> writes:
> This was my hunch too, glad someone got it before me though. This
> patch fixes the problem with 5.3. Probably the same with the double-
> fork version too.
The open FD was my first guess too, but the double-fork version didn't
close any fds either, so I
Neale Pickett <[EMAIL PROTECTED]> writes:
> Would you mind sharing how you launch dwm?
It might also be helpful to share your status script. If you launch
your status script like this:
status | dwm
and status forks, the parent may not be exiting.
If the status program never exits
Guillaume Quintin <[EMAIL PROTECTED]> writes:
> As usual this is the dwmii patch for dwm-5.3.
> I think I have an issue when quitting dwm : If windows are openned
> (xterm, claws-mail, firefox, pidgin for example) then X won't shut down
> until I close (when possible) the windows. Does this have t
Jeremy Jay <[EMAIL PROTECTED]> writes:
> Hope someone else finds this handy, I let my battery die one too many
> times because I never noticed how low it was...
I had this problem too. My solution was this in my status script:
battery_pct=$(get_charge)
if [ $battery_pct
"Anselm R Garbe" <[EMAIL PROTECTED]> writes:
> I'm fine to add it in 5.3, since it seems to work quite well.
Sweet!
For the record, I've never had to work so hard to justify such a small
patch to a FOSS project. It was a pleasant experience that makes me
feel better about the larger codebase!
Neale Pickett <[EMAIL PROTECTED]> writes:
> "Anselm R Garbe" <[EMAIL PROTECTED]> writes:
>
>> Well, I remember there was a problem with the SIGCHLD signal handler,
>> I need to recheck with Stevens tomorrow. It might be that this was on
>> so
"Anselm R Garbe" <[EMAIL PROTECTED]> writes:
> Well, I remember there was a problem with the SIGCHLD signal handler,
> I need to recheck with Stevens tomorrow. It might be that this was on
> some ancient UNIX though. But the double-fork is definately the most
> portable solution.
Page 267 in Stev
"Donald Chai" <[EMAIL PROTECTED]> writes:
> 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 th
"Donald Chai" <[EMAIL PROTECTED]> writes:
> The proposed change would add inconsistency, unless if people want the
> second MOD+1 to jump to the previously selected set of tags or do some
> other weird thing.
I think that would make more sense if all available layouts were shown
at the top like t
"Thayer Williams" <[EMAIL PROTECTED]> writes:
> By having a togglelayout() feature that worked for any mode, it would
> allow folks to quickly go to a desired mode and jump back to the
> previous when they're done.
Yeah, that's my use case. I only ever go back and forth between tile
and monocle.
yy <[EMAIL PROTECTED]> writes:
> After a quick look, I think the last check in the first if should be
> arg->v != lt[sellt^1]
Yes, that's what it should have said. I wonder how it was working for
me before, when I sent the code to the list. [cue twilight zone music]
Here's what it should have
This simple modification to setlayout causes a binding to toggle if it's
already in the requested layout.
void
setlayout(const Arg *arg)
{
sellt ^= 1;
if(arg && arg->v && (arg->v != lt[sellt]))
lt[sellt] = (Layout *)arg->v;
if(sel)
arrange();
else
drawbar();
}
Now Alt-M toggle
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 SLOC, but surely there's some reason the double-fork is there that
I'm just m
I was inspired by dwm to write a screen saver / locker, and an
auto-launcher (like xautolock, but mine blocks). I split it up into
several little programs that each do one thing. You can use the
programs to build a lot of different kinds of screen savers.
http://woozle.org/~neale/src/xss
I
40 matches
Mail list logo
