SQLite format 3 @ D \ .K # b I #0000 U z //!tableblog_posts_backupblog_posts_backup CREATE TABLE "blog_posts_backup" ( "post_id" INTEGER NOT NULL DEFAULT '0' , "url" VARCHAR(50) NOT NULL , "title" VARCHAR(300) NOT NULL , "subtitle" VARCHAR(300) NOT NULL , "excerpt" VARCHAR(1000) NOT NULL , "content" TEXT NOT NULL , "comments" INTEGER NOT NULL , "date" INTEGER NOT NULL , "live" INTEGER NOT NULL )u!!5tableblog_postsblog_posts CREATE TABLE "blog_posts" ( "post_id" INTEGER NOT NULL , "url" VARCHAR(50) NOT NULL , "title" VARCHAR(300) NOT NULL , "subtitle" VARCHAR(300) NOT NULL , "excerpt" VARCHAR(1000) NOT NULL , "content" TEXT NOT NULL , "comments" INTEGER NOT NULL , "date" INTEGER NOT NULL , "live" INTEGER NOT NULL , PRIMARY KEY ("post_id") )] tableblog_metablog_metaCREATE TABLE "blog_meta" ( "meta_id" INTEGER NOT NULL , "blog_id" INTEGER NOT NULL , "meta_key" VARCHAR(100) NOT NULL , "meta_val" VARCHAR(1000) NOT NULL , PRIMARY KEY ("meta_id") )* j d++tableblog_categoriesblog_categoriesCREATE TABLE "blog_categories" ( "cat_id" INTEGER NOT NULL , "blog_cat_id" DOUBLE NOT NULL , "name" VARCHAR(30) NOT NULL , "url" VARCHAR(30) NOT NULL , PRIMARY KEY ("cat_id") )^tableblog_tagsblog_tagsCREATE TABLE "blog_tags" ( "tag_id" INTEGER NOT NULL , "name" VARCHAR(100) NOT NULL , "url" VARCHAR(100) NOT NULL , "tag_count" INTEGER NOT NULL DEFAULT '0' , PRIMARY KEY ("tag_id") ) ero" src="https://blog.x-e.ro/ui/img/blog/r4-ds.04.jpg" alt="R4-DS circuit board skin by xero" />
here's the circuit board theme i made for my r4-ds. download it here. the three buttons on the bottom left screen are the three main options of the r4. the first is ds emulations, this allows you to play archival copies of games. the center icon is the media player moonshell. it can play mp3s and a custom ds video codec. the final option is to boot to slot-2 (gameboy advance slot). this however will not play regular gba games (you have to remove the r4 to do that) this option is for booting legacy gba hackloaders.
playback of emulated games is flawless! the speed, the sounds, the graphics, everything looks exactly the same. even games with multiplayer functionality work perfectly. what's great about the r4 is yew can grab an 0-day rom of a new game and check it out. if it sux, you just delete the rom and forget about it. and if you find out it's awesome, then you can buy the game and feel assured what its gonna be all about. i think if nintendo allowed you to download demo roms directly to an sd card on the hardware to "try before you buy" people would go crazy, and the ds scene would explode.
so now, you might be asking...
so xero, what can you play on this? and where can i get it?
public site is the devil's shadow. but if you google it, there are tons more. the other main application type is homebrew. and this is a very broad area. so, homebrew apps can be anything from data organizers, media players, emulators or homemade games. some of my favorites are:
Lameboy - gameboy/color emulator. (LSDJ anyone?)
jEnesisDS - sega genesis emulator)
DS Organize - calendar, address book, todo list, graphics app, file browser, calculator, irc client, webbrowser, rss feed reader.
MoonShell - do it all media player
SvSIP -VoIP/SIP client
glitchDS/cellsDS - a fun suite of graphical music composing tools
and there are tons of other retro game consoles emulated for the DS.
zophar's domain has a great list.
# export ZDOTDIR globally echo 'export ZDOTDIR="$HOME"/.config/zsh' >>/etc/zsh/zshenv # create directory skeleton mkdir -p ~/.local/{bin,docs,cache,lib,share,src,state} ~/.local/state/zsh
i like to run these before cloning my dotfiles and using stow, to prevent these dirs from being symlinks.
with it's tight integration to the unix shell, vim has been my editor of choice for years. once you start to grok movements and operators you quickly begin manipulating, not just editing text files. and in the shell, everything is just text ;D these days i'm a full time neovim user. it's just better than normal vim at this point imho. using a community built embedded language like lua5 makes way more sense than a custom/proprietary one.
with my asliases e is $EDITOR and se is sudo $EDITOR
e ~dotfiles/README.md is nvim ~/.local/src/dotfiles/README.md
se /etc/hosts is sudo nvim /etc/hosts
you can also start neovim using ec or editor clean, to run nvim --cmd ":lua vim.g.noplugins=1". which is kinda like nvim --clean with the added bonus of still loading some sane defaults. i use this as my MANPAGER with +MAN! as well.
my neovim setup is written in lua, uses lazy.vim, and a bunch of plugins. you can enable/disable them selectivly from plugins.lua. here's the structure of configs:
~/.config/nvim ├── lua/ │ ├── utils/ --> shared helper functions │ ├── plugins/ │ │ ├── alpha.lua --> each plugin has it's own config │ │ ├── cmp.lua │ │ ├── lsp/ │ │ │ ├── init.lua --> main lsp setup logic │ │ │ ├── remaps.lua --> lsp key-bindings │ │ │ └── servers/ │ │ │ ├── bashls.lua --> language server specific configs │ │ │ ├── luals.lua │ │ │ └── etc... │ │ ├── mason.lua │ │ └── etc... │ ├── ui.lua --> ui related options │ ├── commands.lua --> custom commands and key-bindings │ ├── general.lua --> general settings │ └── plugins.lua --> lazy.nvim entrypoint ├── nvim-logo* --> k-rad ansi art └── init.lua --> calls other files
as of writing this, i use ~50 plugins and an average startup time of 90-150ms. plugin highlights include:
it builds mosh-server from this pr for osc 52 clipboard support.
i use xvfb to create a headless xorg enviroment for the clipboard. you can then use tools like xsel and xclip to pipe {in/out} of it in the tty. i have a personal fork on clipmenu that uses fzf and a an osc52 yank script to syncromize the x and ipad clipboards. there are other osc52 plugins for neovim and tmux included in these dotfiles to bring the whole thing together.
i prefer a minimal setup, and choose to interact with my operating system via the so-called "terminal" or "command line", (read that quoting sarcastically). with the web browser and video player among the noted outliers. in my opinion, using your computer should be a very personal experience. your colors, aliases, key-bindings, etc meticulously crafted to your exacting specifications. so for me, the unix shell is the most important part of my environment.
i use zsh as my interactive shell. it's an extensible, bash like shell with awesome completion and correction engines. i manage multiple shell sessions with tmux. it's a feature packed terminal multiplexer with support for buffers, split windows, detached local and remote sessions, etc. i use neovim and a member of the cult of vi. sing phrases to the third reincarnation of the glorious ed! lel.
i'm all about living a comfy and clean digital life, so that means a tidy and organized home directory. my ~ and this repo, follow the XDG spec. here's a generalized breakdown:
~ ├── .config/ $XDG_CONFIG_HOME --> app specific configs │ ├── nvim │ ├── tmux │ ├── zsh --> each app has a folder │ │ └── zshrc --> config files │ └── etc... ├── .local/ │ ├── bin/ $PATH --> my scripts │ ├── cache/ $XDG_CACHE_HOME --> runtime files │ ├── docs/ ~docs --> my documents │ ├── lib/ $pkgManger_HOME --> app libraries │ ├── share/ $XDG_DATA_HOME --> shared app files │ ├── src/ │ │ ├── dotfiles/ --> this repo │ │ └── other_code/ │ └── state/ $XDG_STATE_HOME --> app state files │ └── zsh/ │ └── history --> app created files ├── .ssh/ │ ├── authorized_keys │ ├── config │ └── known_hosts └── ▄█▀ █▬█ █ ▀█▀
to make this all work, (esp ~/.local/lib) i have a ton of XDG directives in my