Re: [dev] Simpler WiFi alternatives
Hi, * Laslo Hunhold 2023-05-13 09:51 Even though I absolutely am for free speech and against censorship, especially self-censorship due to "political correctness" (slippery slope), what good is free speech when nobody listens? This happens both when there's little signal over noise and the thread becomes hostile, because people just check out. Can't agree more. Suckless has always strived to be apolitical in terms of current societal debates, and it's the only hacker community of that kind that I know of in Germany. There are enough places to discuss the current heated politial topics on the web, this is not it. Everything is political, so is suckless, too, but I agree that it has been a place where the "hot" politics have been avoided. This is good, IMO, not because it's good to be apolitical, but because the polarisation in hot societal debates, doesn't really enable an useful discourse that contributes to developing better ideas or advance understanding. The knowledge gain is close to zero. Freedom isn't free, and in regard to free speech, I think the responsibility of each individual is to make use of it only as much as necessary. Not sure I understand this correctly, but I think it's similar to what I wanted to add to the thread; let me phrase it differently: abusing the free speech argument to justify tone and style is just as harmful as (self-)censorship. Freedom of speach is about ideas and messages. cheers --s
Re: [dev] Keyboard language/layout used with slock
Hi, * Benjamin Chausse 2022-09-04 23:39 Is there an existing elegant way to force slock to only use a certaint layout? My current best idea would be to used the failure-command patch to switch my layout after 1 incorrect password but this feels somewhat janky. slock man page says SYNOPSIS slock [-v] [cmd [arg ...]] DESCRIPTION slock is a simple X screen locker. If provided, cmd [arg ...] is executed after the screen has been locked. so, you probably can do something like slock setxkbmap -layout "us" -variant "intl-unicode" And I should probably do so, too, and remove some mental load. Thanks for making me think about it. cheers --s
Re: [dev] Let's talk about Go, baby
Hi, * Markus Wichmann 2019-01-30 20:13 > > Can you web development in C? > > You can, since you can do anything in C. But why would you want to? Web performance. (which translates to user experience and computational time these days, among others) I've heard that a large Chinese IT company runs only C[/C++] services in production. Well, hard to overlook the ++ there. Just speculating on the "why". On this scale, a fraction of a milisecond per request can earn you a fortune. cheers --s
Re: [dev] suckless html to markdown (text)
I'm afraid pandoc won't be considered suckless by most of the list, but I would double Nick's recommendation: pandoc is the only tool that eventually worked reliably for my tasks. Escpecially in corporative environment, I appreciate that I can convert accross formats,even to docx and import to / export from google docs. Actually, I prepare also my talks with a chain of [markdown and tex mix] --pandoc--> pdf unless they are reasonably simple to fit in `sent`. --s
Re: [dev] What would a well-designed voice assistant program look like?
Laslo, * Laslo Hunhold 2018-03-24 13:00 > most of the deep learning folks don't know what the hell they're doing > and it will cost us big time in the near or far future. > Just throwing data at a problem you do not understand will get you > better results but won't solve the fundamental issue of not > understanding it. While I share some of your concerns (even worse: without understanding what data one throws, there is no chance to meaningfully interpret the results), I know among deep learning folks there are knowledgeable people, including e.g. some which converted to DL after decades of developing other approaches to vision problems. Back to the point, end-to-end approaches are well worth attention, even though not modular. They seem to be able to find patterns in the coupled sub-problems to solve the combined problem better or more efficiently than if explicitly factorized and modeled separately. cheers --s
Re: [dev] What would a well-designed voice assistant program look like?
* Laslo Hunhold 2018-03-22 13:59 > When reflecting about a problem, it should be a priority to think about > how it can be split up. In this case, we can talk about two problems, > which combined, solve the "voice assistant" problem. > >1) voice recognition >2) assistant I'm sure that the deep learning folks will object: factorising in sub problemswas yesterday; now we ge end-to-end. And indeed there are a few examples where a field was swept by NN in short time (e.g. vision), at least in terms of accuracy. This was done not by factorising the problem better, but by solving it end-to-end with a lot of data. --s
Re: [dev] [st] Multiple monitors dpi autoswitch
Hi, I very rarely use both internal and external monitor simultaneously. I have a similar problem but with working on the internal (fine) XOR the external (coarse). It does not only affect st, but also browsers, dmenu, dwm status... I've tried setting the dpi with `zoom in` [1] when I plug in/out the external one and invoking st with a heuristic as in [2]: fontsize = dpi / 8 It's all dirty and inconvenient and involve manual steps and guessing... Not sure it gets much better anyway. The most suckless way is probably what arg suggested: buy a laptop with lower resolution display :o) good luck to make it work properly and cover all use cases. cheers --s 1: zoom: #!/bin/sh cur=`xrdb -query Xft.dpi | (read _ dpi; echo $dpi)` [ -z "$1" ] && echo "usage: zoom in|out|; now: $cur" && exit 0 case "$1" in out) new=$(($cur - 12)) ;; in) new=$(($cur + 12)) ;; *) new=$(($1 * 1)) ;; esac echo Xft.dpi: $new | xrdb -merge xrdb -query Xft.dpi 2: st invocation dpi=`xrdb -query Xft.dpi | (read _ dpi; echo $dpi)` [ x$dpi = x ] && dpi=96 fontsize=$(($dpi / 8)) font="Liberation Mono:pixelsize=$fontsize:antialias=true:autohint=true" /usr/local/bin/st -f "$font" "$@"
Re: [dev] [Announcement] slstatus
* Cág 2017-09-08 12:08 > i.e. a themeable panel that shows the output of a > script? dzen2? cheers --s
Re: [dev] pids for surf, webkit instances
or use lsw for a specific window: lsw | grep "some webpage title" | cut -f1 -d' ' | xargs xprop -id | grep PID
Re: [dev] Interesting Web Browser Decoupling Concept
> there are no interesting web browsers or web browser concepts. hiro just discovered a very interesting radical approach to fixing the web: if there were no web browsers, the web would be pointless and thus would not need to be fixed.
Re: [dev] [surf] freeze with gstreamer error
* Quentin Rameau 2017-05-30 18:27 > Yes, set MediaManualPlay to 1. > I think I'll push it as a default. useful, thanks to Quentin and Albert!
Re: [dev] surf+tabbed and session management
* hiro 2017-04-14 17:11 > personally i think tabs are stupid. there should be one url and title > per process. this! it's on my todo for long time now to come up with a clean and simple way to deal with stateful surf sessions (session being an arbitrary number, N, of current urls (and possibly histories)). the obvious approach is to have history and current url per surf window; but a worthwhile one could be to have a single surf window with N “buffers” -- one active and N-1 inactive at a time. what I'm trying to say is that i'd appreciate if the code is not tied to tabbed, but rather generally applicable to a collection of surf processes or something. cheers --s
skala (was Re: [dev][all] Hello)
on a related note: TIL scala lang is getting ready to be adopted by serious suckless projects: http://www.scala-lang.org/blog/2017/04/01/announcing-skala.html --s
Re: [dev] [slock] [PATCH] Add option to show the password on the screen
* David Phillips 2017-04-01 06:42 > With slock's current behaviour, the user can become frustrated when they > suspect that they have made a typo in their password and are unable to > remember how many times to hit the backspace key to correct it. This patch Now that I see the date of the mail: this patch is brilliant! --s
Re: [dev] [st] [PATCH 2/2] Keep end of lines in memory when resizing terminal
* Jochen Sprickerhof 2017-03-29 08:35 > I still ponder to write an experimental shell where input and output is > separated and where the last line is input and the rest is scrollable > output. Scrolling through the input history would give you the > corresponding output and all output would be preserved in variables to > ease processing later on (think of piping old output through grep again > and again without having to evaluate the command again). This sounds interesting to me. It's a reminiscent of the notebook environments (think jupyter) in the sense that at any time you can access previous results. (but wouldn't preserve the consistency, AFAIU, i.e. if you re-run a previous command, it wouldn't affect later command's output (which may be desirable or not)) I wouldn't use this as my regular shell, I guess, but I imagine it fits quite well specific sessions where I experiment with building a processing pipeline: It would automate the saving of intermediate results. > Anyone knows some code where this is implemented already? unfortunately no. cheers --s
Re: [dev] [announce] wjt-0.1 - slider widget
* Ian Remmler 2016-12-13 02:42 > The two examples in the repo are what I'm using for volume I tried the volume example. It's really a beautiful thing! However, I don't see use for it for me here. I've bound keys to directly interact with brightness/volume and firing up additional tool to grab my inputs looks like overkill to me. Maybe I'm missing something, though, or maybe you share some particular context in which you use it. cheers --s
Re: [dev] Shell style guide
* Marc Collin 2016-09-08 05:04 > What people here think of heredoc? > > cat << EOF > 1st line > 2nd line > 3rd line > 4th line > EOF is there a special reason people use `EOF` rather than anything else. FWIW, I use a dot. looks very clear and natural to me, saves some keystrokes, feels right, just as ending a sentence with full stop. cat <<. 1st line 2nd line 3rd line 4th line .
