I cannot get urxvt (9.10) to work with tabbed. I've tried the 0.3
release and tip. (Works perfectly well with xterm, at least in tip).
In the release, I can't get it to do anything, ctrl+shift+enter does
nothing. If I invoke tabbed with -d then embed urxvt into it THEN
ctrl+shift+enter works but t
I actually have tried that option to xterm (+bdc). It doesn't seem
to affect my bold fonts, as they are still fat and unreadable. One thing
I have noticed however, is when I start one Aterm instance (MOD+aterm)
and then another, the second instance is slightly wider than the other.
If I focus t
Hello,
mikshaw wrote:
--- On Sat, 2/26/11, Matt Mrozinski wrote:
From: Matt Mrozinski
Subject: [dev] Aterm not running properly in dwm
To: dev@suckless.org
Date: Saturday, February 26, 2011, 12:25 PM
I can't seem to find documentation anywhere on this, so here's the problem:
In Arch Linux
--- On Sat, 2/26/11, Matt Mrozinski wrote:
From: Matt Mrozinski
Subject: [dev] Aterm not running properly in dwm
To: dev@suckless.org
Date: Saturday, February 26, 2011, 12:25 PM
I can't seem to find documentation anywhere on this, so here's the problem:
In Arch Linux 64 bit, when I run ater
BTW, any way of choosing
OS that do not fit this
generic path is braindead:
1. What I want to do?
2. Pick appropriate tool.
3. Pick (OS) that supports
that tool.
4. Pick (hardware) supported
by (OS).
...
Any deviation from this
path results in less than
optimal outcome.
regards,
- Jakub
On Sun, Feb 27, 2011 at 4:20 AM, Matt Mrozinski wrote:
> I suppose i dont really like the way the bold fonts are really bold in those
> terminals, to the point where they're unreadable. Tho i have to admit, i
> haven't spent a lot of time playing with them. I'll give them a chance
> again, to be s
Matt Mrozinski dixit (2011-02-26, 21:20):
> I suppose i dont really like the way the bold fonts are really bold
> in those terminals, to the point where they're unreadable. Tho i
> have to admit, i haven't spent a lot of time playing with them.
> I'll give them a chance again, to be sure.
>From
* Mark Williams [2011-02-24 17:22:03 -0800]:
> Definitely an edge case, but it's happened to me enough times that
> three possible fixes came to mind (listed in ascending preference):
>
> 1) Put a note in the BUGS section of the man page that mentions that
i think this can be fixed
> 2) The bar
