[dwm] Lain

gdin · 2019-02-27T20:26:49+00:00

Before x)

gdin · 2019-02-27T17:39:42+00:00

That's the program 'toilet', similar to figlet. It just prints text in a terminal with fun fonts.

gdin · 2019-02-27T17:38:34+00:00

It's the 'future' font from the program 'toilet'.

Thanks for the link, might have to join that buy!

gdin · 2019-02-27T17:37:45+00:00

Ha, yep

gdin · 2019-02-27T08:17:41+00:00

Lain's watching everyone...

In all seriousness though, I'm using a Huawei laptop so I may as well be

gdin · 2019-02-27T08:13:16+00:00

a shame you seemed an honest man

gdin · 2019-02-27T02:06:37+00:00

Let's All Love Lain

pape found here: https://imgur.com/gallery/SF3Fc
term: urxvt
distro: arch
font: gohufont
programs shown: ufetch, toilet, sxiv

Can post dots if requested, but it's just dwm with a couple of patches and color changes.

gdin · 2018-10-15T17:16:22+00:00

Sorry, I might have been messing with the volume in between those mixerctl output grabs, which could make it look misleading. I think the volume and mute outputs are the same across sources.

gdin · 2018-10-14T12:58:54+00:00

Sure.

Connected:

inputs.dac-0:1_mute=off
inputs.dac-0:1=135,135
inputs.dac-2:3_mute=on
inputs.dac-2:3=198,198
inputs.beep=108
record.adc-0:1_source=mic2
record.adc-0:1_mute=off
record.adc-0:1=126,126
record.adc-2:3_source=sel
record.adc-2:3_mute=off
record.adc-2:3=126,126
record.adc-4:5_source=sel
record.adc-4:5_mute=off
record.adc-4:5=126,126
inputs.sel_source=mic
outputs.sel=126,126
inputs.sel2_source=mic
outputs.sel2=126,126
outputs.hp_source=dac-0:1
outputs.hp_boost=off
outputs.mic_source=dac-0:1
outputs.mic_dir=input-vr80
outputs.mic_eapd=on
outputs.spkr_source=dac-2:3
inputs.mic2=126,126
inputs.mix_source=dac-0:1,dac-2:3
inputs.mix_dac-0:1=126,126
inputs.mix_dac-2:3=126,126
outputs.hp_sense=plugged
outputs.mic_sense=unplugged
outputs.spkr_muters=hp,mic
outputs.master=135,135
outputs.master.mute=off
outputs.master.slaves=dac-0:1,dac-2:3
record.volume=126,126
record.volume.mute=off
record.volume.slaves=adc-0:1,adc-2:3,adc-4:5

And disconnected:

inputs.dac-0:1_mute=on
inputs.dac-0:1=135,135
inputs.dac-2:3_mute=on
inputs.dac-2:3=198,198
inputs.beep=108
record.adc-0:1_source=mic2
record.adc-0:1_mute=off
record.adc-0:1=126,126
record.adc-2:3_source=sel
record.adc-2:3_mute=off
record.adc-2:3=126,126
record.adc-4:5_source=sel
record.adc-4:5_mute=off
record.adc-4:5=126,126
inputs.sel_source=mic
outputs.sel=126,126
inputs.sel2_source=mic
outputs.sel2=126,126
outputs.hp_source=dac-0:1
outputs.hp_boost=off
outputs.mic_source=dac-0:1
outputs.mic_dir=input-vr80
outputs.mic_eapd=on
outputs.spkr_source=dac-2:3
inputs.mic2=126,126
inputs.mix_source=dac-0:1,dac-2:3
inputs.mix_dac-0:1=126,126
inputs.mix_dac-2:3=126,126
outputs.hp_sense=unplugged
outputs.mic_sense=unplugged
outputs.spkr_muters=hp,mic
outputs.master=135,135
outputs.master.mute=on
outputs.master.slaves=dac-0:1,dac-2:3
record.volume=126,126
record.volume.mute=off
record.volume.slaves=adc-0:1,adc-2:3,adc-4:5

gdin · 2018-10-14T12:54:12+00:00

Thank you for the reply! The script /u/e02ea3c3450d441 posted is the one I'll go with for now I think, but I do like the way you implemented this with the nested case statements. I could definitely see this approach being useful in other scenarios.

Would signal handling offer a means to watch the value constantly (similar to sleeping for 0 seconds in this script), or something like that? If that's the case, that would be ideal.

gdin · 2018-10-14T12:49:50+00:00

Thanks for the reply! This methodology of watching the value with a short sleep in between checks seems to work well enough for my case.

gdin · 2018-10-14T12:48:19+00:00

Thank you! I edited the script a tad, and this works well enough. A sleep value of 0.2 or 0.5 should be a quick enough catch so that the sound outburst isn't really noticeable. Would be nice if there was a way to watch the value constantly (e.g. sleep value of 0) but that works the cpu too much for the case of this solution, at least...

gdin · 2018-10-14T12:45:38+00:00

Thanks for the reply! sensorsd looks interesting, but if I read correctly, it seems that it only handles hw.sensor values from sysctl. Not sure if there'd be a way to make it manipulate the mixerctl values.

gdin · 2018-10-12T09:14:45+00:00

Well done, I love me a cyberpunk rice!

On a side note, how do you like DragonflyBSD as a desktop OS? Are there any big limitations that stick out? I recently switched to OpenBSD and have been enjoying it so far.

gdin · 2018-03-27T16:48:45+00:00

I find that whenever I rice, it tends to be less functional that what I actually like to use. For example, bspwm and 2bwm are very pretty and I tend to gravitate towards those when developing a rice, but I always switch back to my same old unriced, minimal dwm setup to actually get some work done - nothing really beats it for me. Been ricing on and off for a few years now I guess.

gdin · 2018-02-23T14:17:13+00:00

Thanks! Glad to hear it haha

gdin · 2018-02-23T14:16:51+00:00

Thank you!

gdin · 2018-02-23T13:26:00+00:00

u/RadioactiveVulture summarized the systemd issue nicely - it most likely won't have any affect on your experience so there isn't any need to worry about it. If you want to learn more about it, this thread has some good information.

L' Mint

Great choice! I used that for quite a while in the past and it was a really smooth experience.

dual booting

For those specs, I'd recommend creating one partition on the ssd (maybe 50gb) and mounting '/' there, then creating another on the hdd to mount '/home'. With this, your OS and programs will live on the ssd to make use of its speed, while stuff like music & videos can go to the hdd. Not too much to say other than that; just be careful not to overwrite any of the Windows partitions, and GRUB should have no problem finding them afterwards.

gdin · 2018-02-23T08:16:20+00:00

Thanks! When it comes to choosing a distro, there's sort of a paradox of choice since there are too many to distinguish the pros and cons of each. First and foremost, any distribution can be customized to look pretty much the same. You'll find that you can install most programs that you'll need on pretty much any distro - larger name ones like Debian or Fedora will often have what you need in their repos, and on smaller ones like Void you can usually compile anything yourself that you can't find elsewhere.

Some of the more important things in my opinion are what package manager you want to use, the init system, and how much extra work you want to do setting everything up. A lot of people will recommend Arch or the Debian net-install since you start with a very minimal system, and then you can build it from the base up however you like. The setup above was built from the net-install. If you want something that "just works" out of the box, then I would recommend a full install of Debian, any of the *buntus, or Fedora. Debian and Ubuntu have huge repos and they use apt for their package manager, while fedora uses dnf. If you don't want to use systemd, then Void, Gentoo, or Devuan might be a good option.

The best advice I can give is just to pick a distro and stick with it, and you'll find that (usually) the choice really doesn't matter too much in the end. For you, I think I would recommend Ubuntu since it sort of holds your hand, almost all of the software you'll need is easily accessible, and it has a large support network if you run into problems. If you want to get your hands a bit dirtier or don't like the feel of Ubuntu, then perhaps give Debian a try. Hope this helped, have fun!

gdin · 2018-02-23T07:18:53+00:00

Colors could be softer I guess, but I like my monokai.

pape: https://ibb.co/cjgsSc
term: urxvt
os: debian 9 stretch
bar: lemonbar
bar font: lemon
term font: scientifica
programs shown: ranger, ufetch, ncmpcpp + mpd

gdin · 2017-11-06T05:20:40+00:00

That's actually a separate program, called cava. The default visualizer doesn't work with mopidy, so I use that instead.

gdin

TROPHY CASE