What am I looking at?

I know, right? It is a bummer. It’s probably due to the lack of steam and close spaces 🥵

They are meant for movies, not for production

This is awesome!!!

You can emergency-fix a chain even with a piece of wire!

pole dancing girl: oh :/

I’ve been having this disrupting ideas for for years, and it seems that every year I (sadly) get one more:

• actually open source software all the way down to the kernel and drivers.
• user replaceable batteries.
• micro SD slot.
• 3.5mm audio jack.
• zero glue.
• free schematics.
• parts available for purchase.

Does the phone costs double? I don’t care. Shut up and take my money!

Shit! My gf has so much potential! sharing it right now! Hahaha

After the tragedy of wide screens, sidebars, side tabs, side menus, are the only way.

That’s stupid.

Buy a privacy screen protector and stop wasting battery juice.

What about serving your nation by being the captain of a (current) $800,000 electric bus?

Less gay (lol) and more useful to the country.

They totally knew

It’s actually quite neat. It is a three part archesta:

1. i3 key binding, say, Super-l that triggers a script of mine.
2. The script itself rofi-menu takes a single argument, a text “menu file” that describes the menu. Say, my-layouts.menu
3. The menu file is super simple. It looks like this:

Menu Title
[shortcut] # <exit | stay> # <label> # <command>
[shortcut] # <exit | stay> # <label> # <command>
[shortcut] # <exit | stay> # <label> # <command>
...

The script parses this file and generates the menu.

• shortcut is the key binding that will immediately trigger the menu item.
• exit | stay defines whether the menu closes after the option is actioned (sometimes you wanna keep the menu open)
• label is what you see in the menu
• command is… well, the command

One more thing, if your hostname is “my_machine”, and the menu file that you gave to my script is “my-layout.menu”, then the script will actually prefer to use “my-layout.my_machine.menu” if it exists. So you can share your config across multiple machines and have them pick the appropriate menus depending on where it is ran.

A menu example could be:

Layouts
l # stay # Rotate Layout # i3-msg toggle all
f # exit # Toggre Floating # i3-msg floating toggle

So to change i3 layouts, I type:

• Super-l (opens menu)
• l rotate layout (rows, cols, tabs, stack) and keep the menu open. If I keep hitting l it will keep rotating.
• Esc to close the menu.

To toggle the window floating:

• Super-l (opens menu)
• f to toggle floating. The menu closes immediately after.

If you are interested, I can share the script with you :)

It comes from a Cave at the northwest of Romania. So it may as well be a bacteria that turns you into a vampire or something…

There is a huge number of bacteria that do absolutely nothing to humans.

Is this one of them?

Darn… that’s a nice sword

Kind of serious question…

If you are in the tiling team, is this some sort of pattern in you? To be dissident of the “mainstream” way of doing things?

Do you see yourself also taking “the other”, custom, method for most areas of your life?

• i3 on X11.
• emacs for everything.
• Rust lover
• dvorak
• i3 config shared across different machines. Config dynamically generated based on hostname.
• Custom menus with rofi
• Web content is the only thing that makes me use the mouse.

relation status: long distance.

For this degree of tism, I would say that’s a win!

Amen. Whenever somebody ask me for help in their computer, the very first thing I do is to add dvorak so I can work

til. Thanks