| // This is @mmozeiko's libx + EGL example ported to xcb + EGL | |
| // Original code: https://gist.github.com/mmozeiko/911347b5e3d998621295794e0ba334c4 | |
| // It requires EGL_EXT_platform_xcb extension, so if your system is circa the end of 2021 or newer you should be fine. | |
| // Also, I don't know if it works on nvidia. LMK if you test it | |
| // example how to set up OpenGL core context on X11 with EGL | |
| // and use basic functionality of OpenGL 4.5 version | |
| // to compile on Ubuntu first install following packages: build-essential libxcb1-dev libgl-dev libegl-dev, then run: |
| #!/usr/bin/bash | |
| # Goal: move workspace $1 to the currently focused output, move the workspace on the current output | |
| # to the output where $1 was. | |
| # The workspace we want to end up on | |
| dest_ws=$1 | |
| # The output where the destination ws resides | |
| output_of_dest_ws=$(i3-msg -t get_workspaces | jq .[] | jq -r 'select(.name == "'$dest_ws'").output') | |
| # The currently focused output |
It's come to my attention that some people have been spamming issue trackers with a link to this gist. While it's a good idea to inform people of the situation in principle, please do not do this. By all means spread the word in the communities that you are a part of, after verifying that they are not aware yet, but unsolicited spam is not helpful. It will just frustrate people.
A number of things have happened since the last update.
tl;dr: Wayland is not "the future", it is merely an incompatible alternative to the established standard with a different set of priorities and goals.
Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating e
This steps should help working remotely with Sublime Text. They are meant to be incremental, just setting up SFTP will go a long way.
I have all my code on my laptop, edit locally and automatically push the files to my server.
I never edit "tracked" files on the server directly.
I sometimes modify untracked files on the server using rmate (see below).
\o will be a regular 'o' in this context.
| \033[38;2;23;147;209m ▄ | |
| ▟█▙ | |
| ▟███▙ | |
| ▟█████▙ | |
| ▟███████▙ | |
| ▂▔▀▜██████▙ | |
| ▟██▅▂▝▜█████▙ | |
| ▟█████████████▙ | |
| ▟███████████████▙ | |
| ▟█████████████████▙ |
| #!/bin/bash | |
| if [[ $1 == "dark" ]]; then | |
| UI_THEME_GTK="Mojave-dark" | |
| UI_THEME_QT="KvMojave" | |
| UI_ICONS="Faenza-Ambiance" | |
| VIM_BG="dark" | |
| elif [[ $1 == "light" ]]; then | |
| UI_THEME_GTK="Mojave-light" | |
| UI_THEME_QT="KvMojaveLight" |
| #!/usr/bin/env bash | |
| set -o errexit | |
| set -o nounset | |
| set -o pipefail | |
| (( ${#} >= 3 )) || { echo "usage: $(basename "${0}") github-username archive-file [files | directories]" >&2; exit 1; } | |
| username="${1}" | |
| outfile="${2}" | |
| shift 2 |