summaryrefslogtreecommitdiff
path: root/dot
AgeCommit message (Collapse)Author
2023-05-13fix "scan" to specify mode colorGordon GECOS
2023-05-04pingwatch: handle "Address unreachable" properlyAndrew Cady
2023-05-04tmux-log-everything: exec out of shell wrapperAndrew Cady
2023-05-01avoid sourcing .bashrc twiceu
2023-04-29source .xsession.local instead of executingDebian Live user
2023-04-29i3: bind mod+TabDebian Live user
2023-04-29git-ll-remote: add missing message outputDebian Live user
2023-04-29google: pass through options to w3m; and allow launching firefoxDebian Live user
2023-04-29xsession: improved firestartx supportDebian Live user
2023-04-28xsession will load .xsession.local and .Xresources.localDebian Live user
2023-04-28package installer that auto-backports i3-wmDebian Live user
2023-04-28fix tap-to-clickDebian Live user
2023-04-27xsession will try i3 if xmonad missingDebian Live user
2023-04-27fixes get_firefox()Debian Live user
2023-04-14bashrc aliasesGordon GECOS
2023-04-04new command montage0Gordon GECOS
2023-04-04update musopen to new server apiGordon GECOS
2023-04-04new command: webm2opusGordon GECOS
2022-11-29remove redundantAndrew Cady
2022-11-29add .xsessionAndrew Cady
2022-11-29bash_profile fixesAndrew Cady
2022-11-28add .bash_profileElla Grapp
2022-11-28new command: scanElla Grapp
2022-11-28new command pingwatchAndrew Cady
2022-11-27remove mispasted garbage string creating syntax error at runtimeAndrew Cady
2022-10-09increase bash HISTSIZEAndrew Cady
2022-10-09redo .ssh/configAndrew Cady
It's questionable whether this should be in this archive at all, since this file is so likely to contain machine-local settings. Highlights the need for some mechanism to back up what we overwrite.
2022-10-09automatically log all tmux sessions if $HOME/.tmux-log-everything/ existsAndrew Cady
2022-10-09rename marginate -> letterboxAndrew Cady
2022-10-09new alias "nodes"Andrew Cady
2022-10-09enable prboom flag -windowAndrew Cady
2022-10-09remove xinitrcAndrew Cady
2022-10-09remove "penme" commands from this repoAndrew Cady
2022-10-09fix usage bugAndrew Cady
2022-10-09remove all traces of xtigervncviewerAndrew Cady
2022-10-09switch back to xtightvncviewer for shared connectionAndrew Cady
This is needed because xtigervncviewer now fails to forward the input from the other side when launched in this way. There is the same buggy behavior in xtightvncviewer when connecting in the 'reverse' style -- which has been removed from this code base because of that regression. The system as it is now uses both tiger and tight viewers. It uses tiger locally and tight when it projects the display remotely. But only tight has proven reliable in operation. Tight should be available locally. Tiger is preferred because it supports use of a socket file and because it supports many other features and has a superior UI. But these features are not worth bugs and unreliability.
2022-10-09fix race condition with pollAndrew Cady
2022-10-09add doom gamesAndrew Cady
2022-10-09thinkfix.shAndrew Cady
2022-10-09bashrc: new aliases: emacs, frbAndrew Cady
2022-10-09git-ll-remote: trim outputAndrew Cady
2022-02-24xvnc: use unix socket instead of tcp, always (now requires xtigervncviewer)Andrew Cady
2022-02-24switch to tiger vnc viewerAndrew Cady
2022-02-24Successfully eliminated TCP port on both sides!Andrew Cady
This requires relying on xtigervncviewer on the remote side, since only tiger supports connecting to a unix socket file. This is for -r only. The regular connection still uses TCP :(
2022-02-24factor 'trap ... EXIT' code into function atexit()Andrew Cady
2022-02-24avoid use of local TCP port -- use socket file insteadAndrew Cady
2022-02-24remove (now unused) reverse connection codeAndrew Cady
2022-02-24xvnc "-r" option: working solution!Andrew Cady
Works around regression in xvncviewer where reverse connections no longer work. We now use direct connections for -r. Also, we now default to direct connections without '-r', since reverse connections fail to forward mouse+keyboard. The occupation of the port on both connection sides is not ideal. Also note that this also shares the local desktop with all other local users. Limiting the port to the calling user would be a good security feature! This may be relevant: https://serverfault.com/questions/127794/forward-local-port-or-socket-file-to-remote-socket-file/753733#753733 Not sure if either x11vnc or xvncviewer can use socket files.
2022-02-23workaround option -d for regression in xvncviewer from bullseyeAndrew Cady
2021-10-06even more beautiful output from git ll-remoteAndrew Cady
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-10 22:53:40 +0000