I recieved an "off-list" email yesterday from a guy with a patch for my
problem. I will try it out and see how it works.
Let me know if anyone else is interested in obtaining the patch and trying
it.
/David
Hi,
I am trying to compile 9base, but the compiler throws an error at me which
I've never seen before.
/usr/bin/ld: cannot find -lm
/usr/bin/ld: cannot find -lc
Any ideas? I've checked config.mk and can't see any problems with it.
Regards,
David Lind
Hello comrades,
Here’s some RFC for people using double‐width characters in terminals in
their daily life.
Which applications do you use that handle double-width as you expect them?
Do these applications use the double-width for the layout?
Any Chinese or Japanese user?
If doub
maybe:
/usr/bin/ld: cannot find -lm
/usr/bin/ld: cannot find -lc
See 'man ld' :
The linker is looking for library libc.a libm.a and doesn't find it.
i think you need devel package or something
On Tue, Apr 23, 2013 at 4:09 PM, David Lind wrote:
> Hi,
>
> I am trying to compile 9base, but the compi
Hey,
I sure am! Can you maybe upload it somewhere public so everyone can access it?
Thanks,
Jente
Van: David Lind
Verzonden: 23-4-2013 10:08
Aan: dev mail list
Onderwerp: Re: [dev] dwm 6.0 - separate taglists for muli-monitor setup
I recieved an "off-list" email
Hello,
I use st also for read japanese, so i think i can be in the japanese
user category.
application used:
tmux
mutt
moc music player
irssi
zathura as pdf viewer
On Tue, Apr 23, 2013 at 4:07 PM, Christoph Lohmann <2...@r-36.net> wrote:
> Hello comrades,
>
> Here’s some RFC for people using doub
Hi Alice,
I solved the problem by installing glibc-static.
Regards,
David Lind
On Tue, 23 Apr 2013, Alice Ferrazzi wrote:
maybe:
/usr/bin/ld: cannot find -lm
/usr/bin/ld: cannot find -lc
See 'man ld' :
The linker is looking for library libc.a libm.a and doesn't find it.
i think you need deve
Hi,
http://article.gmane.org/gmane.comp.misc.suckless/4230
This is the link that he gave me, seems legit. He was unsure if this
patch would work with the current git head.. we'll just have to try it
out.
Regards,
David Lind
On Tue, 23 Apr 2013, Jente Hidskes wrote:
Hey,
I sure am! Can y
On Tue, Apr 23, 2013 at 09:07:14AM +0200, Christoph Lohmann wrote:
> Hello comrades,
Hi Christoph,
> Here’s some RFC for people using double‐width characters in terminals in
> their daily life.
>
> Which applications do you use that handle double-width as you expect them?
>
> Do these app
Christoph Lohmann dixit:
>Which applications do you use that handle double-width as you expect them?
mksh and jupp (though I don’t use st).
> Do these applications use the double-width for the layout?
It’s possible to use Unicode characters, halfwidth or fullwidth,
to draw nice boxen in e
Greetings.
On Tue, 23 Apr 2013 10:50:32 +0200 Otto Modinos wrote:
> Howdy Comrades.
> I'm new to this mailing list.
> Just found st couple of days back and really loved it. It lacked however
> the ability to send Meta as the 8th bit, the way xterm does. I needed this
> because most of the apps I
On Tue, Apr 23, 2013 at 09:07:14AM +0200, Christoph Lohmann wrote:
> Which applications do you use that handle double-width as you expect them?
I use mutt and vim which handle double-width characters the way I expect
them to (using urxvt or lxterm).
> Do these applications use the double-w
On 04/23/2013 03:07 AM, Christoph Lohmann wrote:
Hello comrades,
Here’s some RFC for people using double‐width characters in terminals in
their daily life.
Which applications do you use that handle double-width as you expect them?
Do these applications use the double-width for the layo
On 04/23/2013 04:50 AM, Christoph Lohmann wrote:
I am considering making this the default behaviour of st. Are there any
arguments against it?
I'm actually confused by what he means by "most of the apps I tried
didn't recognize the escape sequence", because every app I've ever used
recognizes
It means first of all vim. I have also tried mocp, and that didn't work
either. What apps are you using that work?
On 23 April 2013 14:46, Random832 wrote:
> On 04/23/2013 04:50 AM, Christoph Lohmann wrote:
>
>> I am considering making this the default behaviour of st. Are there any
>> argumen
On Tue, Apr 23, 2013 at 10:50:32AM +0200, Christoph Lohmann wrote:
> Greetings.
>
> On Tue, 23 Apr 2013 10:50:32 +0200 Otto Modinos wrote:
> > Howdy Comrades.
> > I'm new to this mailing list.
> > Just found st couple of days back and really loved it. It lacked however
> > the ability to send Meta
On Tue, Apr 23, 2013 at 02:51:58PM +0300, Otto Modinos wrote:
>It means first of all vim. I have also tried mocp, and that didn't work
>either. What apps are you using that work?
All the applications which admit a meta-key should accept 8bit, that is the
real meaning of meta. Send ESC ins
On Tue, Apr 23, 2013, at 7:51, Otto Modinos wrote:
It means first of all vim. I have also tried mocp, and that didn't work
either. What apps are you using that work?
Huh? Vim doesn't have any keybindings that use meta.
Wait a minute... what exactly do you _expect_ meta to do? Using (for
exam
On Tue, Apr 23, 2013 at 08:23:22AM -0400, random...@fastmail.us wrote:
> Huh? Vim doesn't have any keybindings that use meta.
You can bind them.
No I mean when binding a key to meta, it doesn't work. I have and
for example to move lines up and down and well, it doesn't work when
sending an escape sequence as meta.
On 23 April 2013 15:23, wrote:
> **
> On Tue, Apr 23, 2013, at 7:51, Otto Modinos wrote:
>
> It means first of all vim. I
Greetings.
On Tue, 23 Apr 2013 15:23:59 +0200 "Roberto E. Vargas Caballero"
wrote:
> On Tue, Apr 23, 2013 at 10:50:32AM +0200, Christoph Lohmann wrote:
> The unique problem is utf8 encoding will put the 8 bit to 1 in some
> characters, so it is not very clear for me like applications can differe
Using the latest from git and tput smm everything works fine. Thank you
very much.
That got me wondering though. Since there exists such a terminfo
capability, why do apps that except 8bit-as-meta, don't use them?
On 23 April 2013 16:23, Christoph Lohmann <2...@r-36.net> wrote:
> Greetings.
>
>
random...@fastmail.us dixit:
>Wait a minute... what exactly do you _expect_ meta to do? Using (for
>example) meta-a to type 0xE1 "a with acute" is _not_, in fact, the
>expected or intended behavior; it is a bug. And I don't think it will
No, it is the intended behaviour.
http://fsinfo.noone.org/~
Hi,
This looks simple, though not something I could have come up with myself. I
don't need the nametag function, so personally I'm going to remove it. It
should not be too hard to tweak this for applying to git; it's a small patch.
Too bad that at the moment I don't have a second monitor to tes
On Tue, Apr 23, 2013, at 10:30, Thorsten Glaser wrote:
> random...@fastmail.us dixit:
>
> >Wait a minute... what exactly do you _expect_ meta to do? Using (for
> >example) meta-a to type 0xE1 "a with acute" is _not_, in fact, the
> >expected or intended behavior; it is a bug. And I don't think it
On Tue, Apr 23, 2013 at 1:42 PM, Random832 wrote:
> Did you see the st.c I posted a few days ago? The logic for double width is
> mostly complete in it - I just have to fix a few graphical glitches, and
> there are a couple of corner cases (mainly regarding erasing a double width
> character by ov
On Tue, Apr 23, 2013, at 11:01, Silvan Jegen wrote:
> I saw, compiled and tested it but when using mutt only half of the
> (Japanese Kanji) characters would be drawn (so presumably only one
> character cell of a two-cell double character). If I wasn't at a
> conference I would deliver some screensh
On Tue, Apr 23, 2013 at 02:30:29PM +, Thorsten Glaser wrote:
> [...]
> XTerm handles that transparently: when in UTF-8 mode, Meta-d
> is still CHR$(ASC("d")+128) = "ä", just U+00E4 instead of a
> raw '\xE4' octet.
>
> This is *extremely* useful – especially as it leads people
> away from natio
there is nothing keeping you from commiting this patch to the patches
site http://git.suckless.org/sites/tree/dwm.suckless.org/patches
On Tue, Apr 23, 2013 at 10:39 AM, Jente Hidskes wrote:
> Hi,
>
> This looks simple, though not something I could have come up with myself. I
> don't need the n
Actually, I have a question: does this work with the client rules?
> From: jthids...@outlook.com
> To: dev@suckless.org
> Subject: RE: [dev] dwm 6.0 - separate taglists for muli-monitor setup
> Date: Tue, 23 Apr 2013 16:39:23 +0200
>
> Hi,
>
> This looks si
> > No, it is the intended behaviour.
> > http://fsinfo.noone.org/~abe/typing-8bit.html
>
> The fact that someone discovered it, _thought_ it was intended, and
> showed other people how to do it does not mean that it actually was
> intended.
It is the expected behaviour. As far as I know the first
Gregor Best dixit:
>are added to your keyboard layout. Works fine with st, and the regular
>"Left alt sends escape"-behaviour stays the same (and works fine with
>irssi and the like).
On the BSD text console and in default XTerm, the left Alt key
acts as 8-bit enabling Meta key, so it’s *not* the
random...@fastmail.us dixit:
>If this were an intended feature why would it elevate latin-1 over other
>unicode characters? This only proves my point.
It doesn’t – it’s just that latin1 is the first 256 chars of Unicode
by accident (or design, don’t know, ask the Unicode people).
And this Meta/8
Greetings.
On Tue, 23 Apr 2013 17:49:38 +0200 Thorsten Glaser wrote:
> Gregor Best dixit:
>
> >are added to your keyboard layout. Works fine with st, and the regular
> >"Left alt sends escape"-behaviour stays the same (and works fine with
> >irssi and the like).
>
> On the BSD text console and
I'm planning on reworking xdraws and drawregion to draw the background
and text as separate functions. To do this I need to understand some
things:
As I understand it, the behavior is to have all attribute effects on
color (e.g. bold brightening, italic/underline colors) affect only the
foreground
Roberto E. Vargas Caballero dixit:
>It is the expected behaviour. As far as I know the first keyboard with meta
>key was space-cadet keyboard (look it in
Ah okay, thanks for the historic backup!
>meta codes you have it configured for it (or maybe your xterm has a
>different default configuration
> The nice thing about ASCII and the QWERTY layout is that it has
> all ASCII characters easily available, so you can enter *all*
> latin1-subset-of-Unicode characters with just it.
Because all the latin1 symbols begin from a0, that is the smaller value you
can generate using a meta key, because 2
Greetings.
On Tue, 23 Apr 2013 17:53:47 +0200 random...@fastmail.us wrote:
> I'm planning on reworking xdraws and drawregion to draw the background
> and text as separate functions. To do this I need to understand some
> things:
>
> As I understand it, the behavior is to have all attribute effect
On Tue, Apr 23, 2013, at 11:53, Christoph Lohmann wrote:
> It’s the simple way of doing all the brigthening and reversing. St is
> keeping to what other terminals do. But since none of them keeps to any
> standard colors or good behaviour is this what makes st being what it is
> – a simple term
2013/4/22 Carlos Torres
> It has been argued before that the use of named tags is somewhat a
> misunderstanding of dwm.
>
Yeah, it's was a misnomer. Personally, I was thinking about workspaces, but
I always called it tags.
Anyway, Jente, did you try it with statuscolors and / or pertag?
Kind Re
Thorsten Glaser writes:
> >I think it is easier a compose key, which allows you define non ascii
> >characteres using keystrokes (compose-key ' a -> á). This is the solution
> >use in my USA keyboard and could generate spanish accents.
>
> Sure, that works too, and I use it for things like ① but C
It has been argued before that the use of named tags is somewhat a
misunderstanding of dwm.
Yeah, it's was a misnomer. Personally, I was thinking about workspaces, but
I always called it tags.
My tag usage is inspired by this blogpost [0].
I have tags for:
* generic terminal usage
* web surfin
From: "Roberto E. Vargas Caballero"
The commit b78c5085f72 changed the st behaviour enabling BCE capability,
that means erase regions using background color. Problem comes when you
clear a region with a selection, because in this case the real mode of the
Glyph is not the value of term.line[y][x]
Greetings.
On Tue, 23 Apr 2013 20:36:52 +0200 "Roberto E. Vargas Caballero"
wrote:
> From: "Roberto E. Vargas Caballero"
>
> The commit b78c5085f72 changed the st behaviour enabling BCE capability,
> that means erase regions using background color. Problem comes when you
> clear a region with
On Tue, Apr 23, 2013 at 08:34:14PM +0200, Markus Teich wrote:
> >>It has been argued before that the use of named tags is somewhat a
> >>misunderstanding of dwm.
> >
> >Yeah, it's was a misnomer. Personally, I was thinking about workspaces, but
> >I always called it tags.
>
> My tag usage is inspi
On Tue, Apr 23, 2013, at 14:34, Roberto E. Vargas Caballero wrote:
> From: "Roberto E. Vargas Caballero"
>
> The commit b78c5085f72 changed the st behaviour enabling BCE capability,
> that means erase regions using background color. Problem comes when you
> clear a region with a selection, becaus
Is there an even more efficient way of using dwm? How do _you_ use it?
I don't know why anyone would care, really, but since you ask...
I know, why i care! I am interested in learning new ways to use tools.
So thanks for the insight.
--Markus
On Tue, Apr 23, 2013 at 03:38:32PM -0400, random...@fastmail.us wrote:
> On Tue, Apr 23, 2013, at 14:34, Roberto E. Vargas Caballero wrote:
> > From: "Roberto E. Vargas Caballero"
> >
> > The commit b78c5085f72 changed the st behaviour enabling BCE capability,
> > that means erase regions using ba
On Tue, Apr 23, 2013, at 16:21, Roberto E. Vargas Caballero wrote:
> In drawregion you have:
>
> 3172 bool ena_sel = sel.bx != -1;
> 3173
> 3174 if(sel.alt ^ IS_SET(MODE_ALTSCREEN))
> 3175 ena_sel = 0;
> ...
> 3190 if(ena_sel && *(new.c) && s
> That's not true. Only the attribute passed to xdraws() is altered - the
> real attribute stored in the character cell is left alone.
>
> Line 3189 new = term.line[y][x]; makes a _copy_ of
> the Glyph structure, and line 3191 only modifies the copy, not the
> original.
You
On Tue, Apr 23, 2013, at 17:05, Roberto E. Vargas Caballero wrote:
>
What _exactly_ is the behavior you are observing? Are you sure it's not
_actually_ staying selected, rather than simply drawing that way?
If you click the mouse somewhere else, does the original selection go
away, or does it st
On Tue, Apr 23, 2013 at 05:12:47PM -0400, random...@fastmail.us wrote:
> On Tue, Apr 23, 2013, at 17:05, Roberto E. Vargas Caballero wrote:
> >
>
> What _exactly_ is the behavior you are observing? Are you sure it's not
> _actually_ staying selected, rather than simply drawing that way?
Did you se
On 04/23/2013 05:27 PM, Roberto E. Vargas Caballero wrote:
It is very confusing see a hightlight blank line, that really is selecting
the previous content of the line. If the selecting mark keeps in the screen
it is only some garbage in it. If you can find other terminal emulator with
this behavi
2013/4/24 Random832 :
> On 04/23/2013 05:27 PM, Roberto E. Vargas Caballero wrote:
>>
>> It is very confusing see a hightlight blank line, that really is selecting
>> the previous content of the line. If the selecting mark keeps in the
>> screen
>> it is only some garbage in it. If you can find oth
We're now clearing empty areas with spaces, so there is no point to check
if character contains non-empty string.
---
st.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/st.c b/st.c
index 71e5b83..11b9b51 100644
--- a/st.c
+++ b/st.c
@@ -3077,7 +3077,7 @@ drawregion(int x1,
> Maybe the behavior is wrong - but if the problem is that it is
> _still selected_ (i.e. hilight goes away when you select something
> else), it's not something that can be solved with anything to do
> with visual attributes only.
> That was why I was asking for clarification whether it is _still
We're now clearing empty areas with spaces, so there is no point to check
if character contains non-empty string.
---
st.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/st.c b/st.c
index 71e5b83..11b9b51 100644
--- a/st.c
+++ b/st.c
@@ -3077,7 +3077,7 @@ drawregion(int x1,
2013/4/24 Roberto E. Vargas Caballero :
> You are talking here about our Selection data structure, and you are right,
> if we mark it as not enabled (sel.bx = -1), all the problem will be fixed,
> and maybe in a cleaner way.
> We can test it in tclearregion in this form:
>
>
>
> for(y = y1;
> We can test it in tclearregion in this form:
>
>
>
> for(y = y1; y <= y2; y++) {
> term.dirty[y] = 1;
> for(x = x1; x <= x2; x++) {
> if(selected(y, x))
> selclear(NULL);
> term.li
> Too late -- I already sent almost that exact patch :P.
> Yes, I think this is the right thing to do, because st currently
> clears selection on putting character inside it. So, changing a
> characted with tclearregion() should clear it as well.
I can not see your patch, I only can see you sen
---
st.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/st.c b/st.c
index 11b9b51..7e79358 100644
--- a/st.c
+++ b/st.c
@@ -1425,6 +1425,9 @@ tclearregion(int x1, int y1, int x2, int y2) {
for(x = x1; x <= x2; x++) {
term.line[y][x] = term.c.attr;
2013/4/24 Roberto E. Vargas Caballero :
>
> I can not see your patch, I only can see you send twice the same patch,
> maybe did you mistake the second mail?
>
Yeah, sorry, accidentally sent the same patch two times. Now it should
be correct, I think.
> @@ -1425,6 +1425,9 @@ tclearregion(int x1, int y1, int x2, int y2) {
> for(x = x1; x <= x2; x++) {
> term.line[y][x] = term.c.attr;
> memcpy(term.line[y][x].c, " ", 2);
> + if(selected(x, y)) {
> +
From: "Roberto E. Vargas Caballero"
The commit b78c5085f72 changed the st behaviour enabling BCE capability,
that means erase regions using background color. Problem comes when you
clear a region with a selection, because in this case the real mode of the
Glyph is not the value of term.line[y][x]
First off - nice work!
Awhile back I started hacking on st in my spare time. I haven't added
anything earth shaking - the majority of what I've been doing has been
refactoring and rewriting bits to make the code better.
Anyways, the way I've been doing things has diverged enough that I don't
know
On 23/04/2013 21:18, Paul Hoffman wrote:
On Tue, Apr 23, 2013 at 08:34:14PM +0200, Markus Teich wrote:
It has been argued before that the use of named tags is somewhat a
misunderstanding of dwm.
Yeah, it's was a misnomer. Personally, I was thinking about workspaces, but
I always called it tags.
66 matches
Mail list logo
