On 2022-04-15 08:51:50 +, Hadrien Lacour wrote:
>
> Some implementation details: do you really need autohell when the only thing
> you use it for is to detect the presence of sys/xattr.h? That's only a few
> lines
> of sh calling cc to do the same.
> Personally, I use POSIX sh to "augment" ma
Hello,
On 2021-04-20 19:53:04 -0400, Sebastian LaVine wrote:
> I am curious, what experiences have people had with Go?
The language is kinda fine I guess? It gets the job done, but I cannot
say I enjoy writing code in it that much. And some design choices
(context.Context) are in my opinion weird
On 2019-12-23 16:47:59 +0100, Laslo Hunhold wrote:
> [..] Especially with the H, L and P options we found many bugs in GNU
> coreutils, and keeping them in is essential if we want to claim that
> we are more or less POSIX compliant. [..]
Sorry I do not understand how this is meant. Looking at the
Hello,
On , Mattias Andrée wrote:
> Wouldn't it just complicate matters if you needed to specify whether a
> number is an integer or a real value;
Could you not just consider sequence of [0-9]+ to be an integer and
anything with other characters either invalid or float? Not sure, I'm in
no means
On , sylvain.bertr...@gmail.com wrote:
> json almost deserves a promotion to suckless format.
Except for not putting any limits on sizes of integers. I think it would
be better to have size the implementation must support to be json
complient. And also having separate int and float types. Because
On , Teodoro Santoni wrote:
> I like jsmn [1] because I like SAX or PULL style parsers.
> There's a list of C JSON parsers at json.org.
>
> [1]: https://github.com/zserge/jsmn
Thing to keep in mind is that jsmn does not transform (unescape)
strings. So for example json
"\u732b\u304c\u592
Hi,
On , Hiltjo Posthuma wrote:
> On Sun, Feb 10, 2019 at 11:31:23PM +0100, Wolf wrote:
> [..]
>
> Also have a look at this patch:
> https://st.suckless.org/patches/fix_ime/
>
> I want to integrate this patch upstream, but in my testing this patch doesn't
> im
Greetings,
I've decided to give a st a try but I've hit a problem quite quickly. It
seems that IBus input is not handled completely correctly. While trying
to input japanese inside rxvt-unicode (using IBus with Anthy), it shows
the prompt around the cursor (urxvt.png). While for st, the prompt is
d
vasuck these days,
otherwise dillo would be king.
/wolf
to be able to tag a window (or a tag) as
needing lots of space, and letting dwm accomodate (go into
monocle or whatever) automatically, but maybe the problem
is that 1024x768 just isn't enough.
/wolf
s/tail recursion/tail call/
> Original Message
> Subject: RE: [dev] dwm taskbar config
> From: "Wolf Tivy"
> Date: Wed, March 23, 2011 9:17 pm
> To: "dev mail list"
>
>
> > "like this in your .xinitrc:
> >
>
set up your X session (usually one of:
.xinitrc, .xsession,
dwm.desktop, etc).
Good luck!
/wolf
t;900 lines.
IMO, uzbl interpreted the unix philosophy wrong.
mumble mumble something about unix haters handbook mumble mumble
suckless instead.
/wolf
the
others were. This should be applied to mainline (how do I push changes
myself?).
Thanks
/wolf
diff -r 7a931a352cf9 surf.c
--- a/surf.c Thu Sep 09 11:15:02 2010 +0200
+++ b/surf.c Sun Feb 20 10:20:18 2011 -0800
@@ -62,7 +62,7 @@
static gboolean showxid = FALSE;
static char winid[64];
s
love to figure out this 'developer console'. I've never heard of it,
but I added the JS to get some level of debugging/reflection support. I
was planning to figure out some schemes that allowed me to do more of
that kind of stuff (page editing, etc), but if something already exists,
that's great. I'll look into it, thanks!
/wolf
-wise. It should be in mainline on it's own.
So much text for such a small issue.
Glad you like the changes!
/wolf
nfig.h.
I'll put it on the wiki as-is unless there is anything you guys can
think up
to improve.
Happy hacking!
/wolf
diff -r 7a931a352cf9 surf.c
--- a/surf.c Thu Sep 09 11:15:02 2010 +0200
+++ b/surf.c Sat Feb 19 13:47:23 2011 -0800
@@ -62,7 +62,7 @@
static gboolean showxid = FAL
.
You'll have to hack it yourself.
Surf is so awesome and fast because it doesn't have all those features.
That also makes it really really easy to hack.
good luck.
/wolf
dard out. Pipe it to dzen2.
You can only justify text left are right, not both.
This makes status bar stuff kindof hard.
It's even harder to make it interactive (like clicking on tags and
stuff).
/Wolf
ally
identify one as being obviously suckless.
/wolf
Hi everyone, I added an option for automatically joining a channel. I find it to be pretty useful. Makes sic easier to use in scripts.Updated the man page with the new option too. Don't forget to quote or the rest of the command gets eaten by the #. Also included in the patch is the fix for that s
oops. That patch just moved the bug. This one squashes it.
- Original Message -
From: Wolf Tivy
Date: Wednesday, November 24, 2010 9:18 pm
Subject: [dev] [dwm] combo patch bugfix
To: dev@suckless.org
> Hi everyone!
>
> I found a little bug in my combo patch. The mouse clic
it, you
really ought to try it!
-Wolf
combo.patch
Description: Binary data
so I would have to redo the mod on a clean branch, commit,
somehow get it back on the wiki... Too complex.
I don't know what others feel about abstraction, but I personally prefer simple
transparency for this and I think it fits better in the suckless philosophy.
-Wolf
> 2) dmenu v4.2.1 appears to be leaking memory. It is missing the
> routines to teardown/cleanup memory structures present in previous
> versions. This patch also adds them.
dmenu doesn't run long and the OS frees all the memory used
by the process. Once it's decided that the process is going to q
Hi!
Here is a dmenu patch that adds a -t option to specify some text that initially
goes
in the input part. I just parachuted in and wrote this when the idea popped in
my head.
It might be useful for surf url stuff or something.
argtext.diff
Description: Binary data
> Instead of going the NetSurf route, I would suggest to re-use the
> chromium source code, even if it's much more monstrous than webkitgtk.
> surf could become a headless chromium where each surf window behaves
> exactly like a chromium tab (+ some dashboard surf window on demand
> like for downl
>I've managed to make it compile a good chunk of the object files,
>but not malloc/free so its somewhat wasted.
It'll talk eventually, keep up the pressure.
> When I get a chance to go at it again I believe the android distribution
>has some "clean" kernel headers included. I may try to move thos
> It can be built alone with jam I _think_, I've been toying with
> it but
> it takes some work and I haven't gotten it all figured out (it seems
> to be making incorrect assumptions about where some header files are,
> and missing some files that i think get moved around by the whole
> build), an
> 2. Demonstrate stand-alone static binaries that have been linked
> against bionic/x86.
This assumes we have bionic itself working. Has anyone actually built it
without building all of android? I got the source, but I can't make it build.
I've tried a few things, but I hate makefiles. Especiall
> > So moving towards that ideal, my first step would be some good
> > documentation or tools for gettign ABS to build static with bionic or
> > uClibc or whatever, and then a statically linked pacman repository.
> > But that's only for the hacked archlinux form of sta.li.
>
> That goes further th
Ok, it works if I make the port 6667, which is also not in my /etc/services.
Should port just be 6667 instead of mucking around with symbolic port
resolution?
- Original Message -
From: Wolf Tivy
Date: Saturday, October 9, 2010 9:27 pm
Subject: [dev] [sic][patch] fixes and questions.
To
Hello!
some fixes for sic attached. story below.
sic was saying "error: cannot resolve hostname : Success" so I
went to the source.
The Success was because the code was written assuming the failure would set
errno, but it didn't.
I fixed it to print out the right error message, but make wouldn't
I've been interested in sta.li for a while but luck has been against me.
surf leaks memory or something at maximum speed when I visit the
elevenislouder link on the sta.li website, and hg hangs trying to clone
hg.suckless.org/stali-toolchain. Furthermore, the hg repository hasn't
been touched in 7
> Hi everyone.
>
> I have been using DWM now for a number of months, and so I am confused
> as to why I'm having so much trouble recompiling surf. I have
> downloaded it from the arch linux AUR. Can anyone let me
> know the steps
> that I should take to recompile with my changes to config.h?
> Yeah, I just wasn't so keen on having to hold down each number when
> selecting tags, so I tried to alter it so you could do something like
> so:
>
> KeyDown: Modkey
> KeyPress: 1
> KeyPress: 2
> KeyUp: Modkey
>
> to select 1 | 2, obviously, rather than
>
> KeyDown: Modkey
> KeyDown: 1
> KeyDo
> What should we do for programs which need controls which don't
> repeat? Make a new kind of input device which looks just like a
> keyboard but
> which isn't because keyboard keys repeat, by definition?
Obviously some programs do need non-repeats, in which case, by all means, jump
thru the
o patch? I am finding it pretty useful.
- Original Message -
From: Ethan Grammatikidis
Date: Wednesday, October 6, 2010 1:54 pm
Subject: Re: [dev] [dwm] tagging interface
To: dev mail list
>
> On 23 Sep 2010, at 3:28 am, Wolf Tivy wrote:
>
> >> Can you explain what co
> Can you explain what could go wrong? The predicate would
> be passed in
> the KeyRelease event (as an XPointer), and return True if it finds
> a KeyPress with matching time and keycode.
Sorry, there is no problem. I didn't quite grasp the arbitrary predicate
part before.
I am skeptical about w
> > There are various functions I think you could use. apropos XCheck?
>
> In particular, XCheckIfEvent seems well suited to this situation-
> -feed
> in a predicate which specifically finds the repeated KeyPress (matches
> time, key, etc.). But this can perform unnecessary computation
> since it
> I suppose your goal was code economy, so maybe you don't care,
> but: by
> not adding the code to deal with repeats, you're forcing the resulting
> release/press pairs to be handled by the toplevel event loop, one
> undoing the effect of the other.
>
> Visually though it shouldn't be an issue:
> By the previous tags I mean the other tagset. It can be toggled with
> view(0), MODKEY+Tab by default. If you want to add that functionality
> to your patch add
>
> selmon->seltags ^= 1; /* toggle sel tagset */
>
> before
>
> selmon->tagset[selmon->seltags] = newtags;
>
> It will pro
> hey,
>
> sounds quite interesting, but what's wrong with a simple
> diff-file instead of instructions where to insert c-code? -.-
>
>
> v4hn
A diff would be better, but my dwm has some other crap, and I
don't have the unmodified, and those are just excuses for the
fact that i don't know how t
er than the
seperate toggle functions. Thanks for all the help!
- Original Message -
From: Wolf Tivy
Date: Monday, September 20, 2010 9:44 pm
Subject: [dev] [dwm] tagging interface
To: dev@suckless.org
> I would like to change the way tag selection works in my dwm.
> The way I thin
> As you can see, I misspoke earlier: the events have *exactly*
> the same time
> field. Combining this with what I said about the queuing
> (the "atomic"
> insertion), I think you'll agree that doing XPeekEvent inside the
> KeyRelease handler, and discarding the pair of events if the time,
> ke
> I'm not sure I'm understanding what you mean but I think you can
> achieve that only changing your config:
>
> #define TAGKEYS(KEY,TAG) \
> {
> MODKEY, KEY, toggleview, {.ui
> = 1 << TAG} }, \
>
> (n.b. toggleview instead of view)
>
> You don't need to rel
> You want the KeyRelease event. Note that, by default, X11
> will generate
> spurious repeat KeyPress events. Years ago I read the
> relevant SDL code
> (which maintains a vector of which keys are currently down) to
> see if it
> had a nice way of handling these events. It turns out it
> ju
does anyone know how to change the mode or something so
that we can get the paired events instead of just 'keypress'?
I know this is possible somewhere because that's how SDL does it.
Thanks.
-Wolf
> Let me rephrase that, given the nature of this list. There's not
> much science to simple string hash functions. Cryptographic hash
> functions are another matter entirely. I'll also add that 31
> happens to be a prime number.
The first thing that struck me was that 31 in binary is all ones,
> Sounds like vi.
except with a clean command set and less legacy baggage.
> Curses does support mouse use at this point, and seeing as the
> use of
> the mouse to select text is one of the big features of sam, I think
> it'd be important to keep that. Instead of using the menu, the options
> from it could all be mapped to single or chorded keystrokes of the
> left han
> Yes, indeed. Both acme and samterm ship with their very own window
> manager, so you can fullscreen acme in rio and pretend you're using
> wmii. And samterm is even worse: a stacking window manager
> within a
> stacking window manager (so you can stack while you stack).
>
> There is a good reas
> > Luxuries like syntax coloring would be nice but really not critical.
> Would you like reading a book with all adjectives bolded and
> nouns italicized?
> You may want to take a look at ALGOL 68.
I hadn't thought of it like that before. Good point.
Excuse me while I also remove indentation fro
I find it useful to be able to edit files using my regular editor
after I break X, or if I don't feel like starting it up.
I like curses stuff even in X because it is nice to open up an editor
and have it tempoarily reuse the terminal window without spawning
another and thrashing my layout. Further
I noticed there is a project for a samterm on the project ideas page.
Has anyone started on this? It seems like a really good idea.
I guess ideally it would be usable without X (in text mode) but would
still keep the nice view and selection interface.
Luxuries like syntax coloring would be nice bu
55 matches
Mail list logo
