On Mon, Mar 20, 2017, at 10:00, robin wrote:
> If only the same honesty could be applied throughout life without bad outcome.
No matter how outrageous the contribution of another party, just don't
be a dick about it. We're all human. We all think something completely
idiotic is a good idea at
> STDIN to add files to queue: `find ~/music | sad`
> Usage:
> sad [-sr] [-f socket]
I should also probably just let you add files to the queue by passing
them as arguments, duh. So:
Usage:
sad [-sr] [-f socket] [FILE]...
I mostly wanted the former so you can use tools like grep, sort, vipe,
Thanks for the suggestion of sad!
I've been using mpd with bindings I added to dwm along with a
libnotify/dunst background shell script on `mpc idle player`. mpd has
been total overkill for what I need. I just add my media library
(Vorbis) and shuffle them.
I've been playing a bit with sad and I
On Mon, Jan 23, 2017, at 02:48, Martin Kühne wrote:
> I had a dream last night...
Now now. No need to hold contempt on the mailing lists. Suckless isn't
some Linux list where we go off on people who want to help but didn't
read the entire codebase, wiki, and archive before posting.
However,
The simplest way I can imagine is to link them into a directory
temporarily and/or permanently with:
mkdir playlist
ln *some_glob_pattern* playlist
Then use the vidir(1) program to edit the files to number them
sequentially the way you want. Then you can either create a playlist and
This has become a C discussion, so I'll toss in here.
If you have a background in Python (most people who have coded before
seem to), I recently stumbled upon http://www.toves.org/books/cpy/. It's
light but covers enough to give you directions to study the language
further.
I personally would
Thanks Quentin! Sounds like its all under control.
Just wanted to bring it up in case nobody knew.
> surf is not _silently_ ignoring them. If the validation fails, `sslfailed`
> will be true and in the window title you can see a `…:U` for untrusted
> instead of `…:T` for trusted.
You're right. It does provide that feedback. My apologies. :)
I've just been doing a bunch of digging in the TLS
> That's in the config, the user should be responsible for it.
True, it is in the config. It's also the default. If the alternative is
too much, perhaps changing
strictssl = FALSE \* Refuse untrusted SSL connections *\
to
strictssl = FALSE \* Validate SSL certificates from server
I just took surf to badssl.com to test how the TLS implementation in
surf reacts. To test I took the default Arch Linux package for a ride.
It failed the test. This is because by default:
static Bool strictssl = FALSE;
Without this set to TRUE, the browser effectively does not look at the
> what do you guys do for wget like functionality? opt for curl?
I just use curl. If you really need something small, you could use
netcat:
nc example.com 80
GET / HTTP/1.1
Host: example.com
User-Agent: netcat
11 matches
Mail list logo
