my i3 config for ubuntu 14.04 based on https://github.com/tunnelshade/awesome-dots

100%

my i3 config for ubuntu 14.04 based on https://github.com/tunnelshade/awesome-dots

✓ Published0🌍 Public

Last edited Jun 4, 2016

Created on Jun 4, 2016

This example visualizes an i3 window manager configuration for Ubuntu 14.04, adapted from the awesome-dots project. It consists of three files: the main i3 config file with keybindings and workspace definitions, an i3lock script that pixellates/blurs the screen for locking, and an i3status configuration that displays system metrics like CPU usage, temperature, load, battery, and time. A custom i3script.sh enhances i3status output by injecting the current keyboard layout with color coding (green for US, red otherwise) into the status bar. The config file defines a tiling window manager setup with mod-key shortcuts for window management, workspace switching, and layout toggling, demonstrating how text-based configuration files can be parsed and visualized as a structured reference for window manager customization.

AI-generated description

Similar vizzes

Loading thumbnail…

i3 dotfile

This example visualizes an i3 window manager configuration file as a network diagram, showing the relationships between keybindings, commands, and configuration settings. The visualization uses d3.forceSimulation to position nodes representing config directives and their associated actions, with links connecting related elements. It highlights the structure of the i3 config syntax, including bindsym commands, focus/movement operations, and window decoration settings. The data is parsed directly from the i3.config source file, revealing how keyboard shortcuts map to window management functions and system controls like audio and brightness.

Aaman-tiwari

77% match

Loading thumbnail…

Will's i3 config, minor edits for vim movement

This example visualizes a user’s i3 window manager configuration, showing how keyboard shortcuts are mapped to actions like focusing, moving, splitting, and switching workspaces. It reads the plain-text config file and parses each `bindsym` line to extract the modifier combination, key, and command. The rendering uses a custom layout that groups bindings by category—such as focus, movement, layout, and workspace control—while highlighting the vim-style keys (h, j, k, l) and their shifted variants. The visualization relies on string parsing and a simple DOM-based chart, with no external visualization library, to display the mapping structure clearly.

WWilliamQLiu

70% match

Loading thumbnail…

My Ubuntu setup note

This example visualizes a personal Ubuntu setup note as a tree of command-line steps, organized by topic such as SSH, Git, and i3 window manager configuration. The code parses the plain-text gist file into hierarchical nodes and renders them with d3.forceSimulation, using colored circles for categories and text labels for each action. It shows the dependency flow between installation commands and configuration tweaks, with links drawn as straight lines between connected steps. The underlying data source is the raw gist content, processed directly in the browser without external libraries beyond D3.

Aadkdev

64% match

Loading thumbnail…

Gist d6cbe45544b6e9628a66

This visualization is a text-based configuration file, not a graphical chart. It shows a tmux terminal multiplexer setup, written in the tmux.conf scripting language, detailing key bindings, pane navigation, and plugin management. The code configures tmux through commands like `bind-key`, `set-option`, and `set-window-option`, and integrates the tmux plugin manager (tpm) via `run-shell` to load plugins such as tmux-resurrect for session persistence. It also adjusts mouse support, history limits, and copy-mode behavior, reflecting a developer’s personalized environment rather than data-driven graphics. The rendering approach is purely textual, with no external visualization libraries involved.

66ewis

60% match

Loading thumbnail…

Starter tmux conf from....the web.

This example visualizes the configuration structure of a tmux status bar, showing how session, window, and pane information is formatted and color-coded. The code uses tmux’s `set -g` commands to define left and right status sections, including session name, window index, pane number, hostname, and a live clock with date. It explicitly sets colors for backgrounds, foregrounds, and active/inactive states, and includes workarounds for tmux’s color-flicker bug in activity indicators. The rendering approach is a direct textual representation of the terminal multiplexer’s built-in UI, with no external libraries beyond tmux’s native configuration syntax.

CCameron-Grams

59% match

Loading thumbnail…

Gist c40c213926a54197db25

This example shows a configuration file for Devilspie2, a window management tool, that programmatically arranges application windows on a Linux desktop. The Lua script defines rules for positioning, sizing, and setting workspace and layering properties for specific applications such as Terminator, Zim, MPlayer, and various file managers. The code uses Devilspie2's window inspection APIs like `get_window_class()`, `get_application_name()`, and `get_window_name()` to identify windows, then applies actions such as `set_window_geometry()`, `center()`, `set_on_top()`, and `change_workspace()`. The configuration demonstrates rule-based desktop automation rather than data visualization, relying on window metadata to conditionally configure the desktop environment.

MMrMattSim

58% match

Loading thumbnail…

The best and greatest tmux.conf ever

This example visualizes a configuration file for tmux, the terminal multiplexer, as a demonstration of practical customization. The code shows a text-based interface configuration using tmux’s built-in command syntax, including key bindings, pane and window navigation, and status bar theming. It employs tmux’s `bind-key`, `set-option`, and `set-window-option` commands to define behavior, such as Vim-style pane selection and automatic window titles. The status bar uses tmux’s formatting syntax with color attributes and system commands, like `whoami` and `cut` on `/proc/loadavg`, to display session information. The rendering is purely textual, reflecting a terminal environment rather than graphical output.

FFrozenfire92

58% match

Loading thumbnail…

Dotfiles

This visualization maps the structure of a developer’s dotfiles—configuration files for shell, aliases, and editors—as a node-link diagram. It shows the hierarchical relationships and dependencies between files like `.zshrc`, `.aliases`, and `.vimrc`, revealing how commands and settings connect. The rendering uses a force-directed layout, likely via D3’s `d3.forceSimulation`, with nodes representing files and edges indicating source references or shared commands. The source data comes from a gist containing plain-text configs, parsed to extract aliases, plugins, and path exports.

Aarchae0pteryx

57% match