9 ms·
Fulfilling a reader's request for my “dot files”
- stuaxo 3y agoThe nocolor thing I enjoyed, I'm the opposite I want an envvar to make my terminal as colourful as a Jodorowski film.
- janvdberg 3y agoOne tip for your .bashrc I only recently found out and can't do without anymore is one I picked up here (log all shell commands directly to a file): https://www.jefftk.com/p/you-should-be-logging-shell-history https://www.jefftk.com/p/you-should-be-logging-shell-history
- zamnos 3y ago'histgrep' is an interesting one. Bash has a built in backwards search via ^r, which is greatly enhanced by plugging fzf into it.
- cerved 3y agoIdk, the times I grep history I just history | grep Using fzf for backwards search sounds interesting, can you elaborate? My favorite is binding key-up and down to complete using search. That's a game changer
- zamnos 3y agoThe best description I found with a not so short Google was buried in https://www.redhat.com/sysadmin/fzf-linux-fuzzy-finder https://www.redhat.com/sysadmin/fzf-linux-fuzzy-finder but the workflow is I hit ctrl-R (in bash, but there's bindings for other shells), I type out part of the command I know is in my history, and fzf will grep history for commands that match via its fuzzy search algorithm. So if I remember running something that involved a file called something in a log dir, I type /log/, and it interactively lets me search. I remembered I was using awk with the log file, so I can add "awk" to the existing search), and then I use the up arrow to select it and hit enter. at which point it's in my command buffer waiting for me to either hit enter again or edit the command and then hit enter. Might sound complex written out like that, but I promise it's worth the investment to set it up and read the manual.
- bomewish 3y agothis is what mcfly does but it does it all automagically and stores everything in sqlite database. Also easy to sync that db between two computers connected by tailscale/ssh.
- jordemort 3y agoIf you like searching your Bash history with fzf, you're gonna love McFly: https://github.com/cantino/mcfly https://github.com/cantino/mcfly
- Evidlo 3y agoYou can get similar behavior with bash's built-in history by setting a few options: # -------- History -------- #increase bash history HISTFILESIZE=10000000 HISTTIMEFORMAT="%FT%R " HISTSIZE=10000000 # append to .bash_history and reread after each command export PROMPT_COMMAND="history -a;$PROMPT_COMMAND" # append to .bash_history instead of overwriting shopt -s histappend # dont allow repeated lines export HISTCONTROL=ignoredups:erasedups
- geraldhh 3y agowondering if scanning throu >10M history entries, looking for duplicates, will introduce a noticeable ex degradation on lesser systems (rpi etc).
- znpy 3y agoThe file might fit without much problems in the filesystem cache, so i guess it would only be a problem in the first time. I had a friend in university that used a refurbished hp workstation with a shitload of ram as a desktop computer, and he would find | xargs -L1 cat {} > /dev/null everything in his home directory on login to warm up the filesystem cache. The kernel would then drop stuff not actually needed/accessed nicely over time.
- iforgotpassword 3y agoDon't know about erasedups, but the other option just applies to consecutive repeats, so really only had to scan from the end until the first non-dup
- deleted 3y ago[deleted]
- jefftk 3y agoExcept if you ever accidentally open a shell without those settings set (ex: "bash --norc" to get a clean profile) it will trim your decades-long history. Your HISTFILESIZE is also probably not enough: my .full_history goes back to 2012 and is 2.5x your limit.
- deleted 3y ago
- jakebasile 3y agoI like to use atuin for this. Basically indispensable to me now. https://github.com/ellie/atuin https://github.com/ellie/atuin
- iAmAPencilYo 3y agoGreat Atuin, that's amazing. Thank you, this is indeed a game changer for having a permanent history. I use ctrl+r for everything including commands I vaguely remember but know at least some letters
- cerved 3y agoI like saving all my history, but I also find that it easily becomes a mess doing it in one file. So I split it up session, and then I merge it all into one file. # Eternal bash history. # --------------------- HISTCONTROL= HISTFILESIZE= HISTIGNORE= HISTSIZE= HISTTIMEFORMAT="%Y-%m-%dT%T%t" # read global history HISTFILE=~/.bash_eternal_history history -r # IIF there's no session history directory, create one if [ ! -d ~/.bash_history ]; then [ -f ~/.bash_history ] && mv ~/.bash_history ~/.bash_history.0 mkdir ~/.bash_history fi # change history file to one for the session HISTFILE=~/.bash_history/$$ # If it already exists, take a backup if [ -f "$HISTFILE" ]; then mv "$HISTFILE" "$HISTFILE"."$(stat "$HISTFILE" --format='%W')" fi # save the current session id + process id { export SESSION_ID="$(</proc/$$/sessionid)"; } 2> /dev/null printf "#$(date '+%s')"'\n# starting session:'$SESSION_ID' process:'$$' in:'"$PWD"'\n' > "$HISTFILE" && history -r # Use trap to save history, not just on logout but also EXIT trap_exit() { # Append session history to global history ## Append to local history session to file cp -f "$HISTFILE" /tmp/history.$$.0 history -a cp -f "$HISTFILE" /tmp/history.$$.1 ## Append local history file to global history printf "#$(date '+%s')"'\n# ending session:'$SESSION_ID' process:'$$' in:'"$PWD"'\n' | cat "$HISTFILE" - >> ~/.bash_eternal_history } trap trap_exit EXIT
- splitbrain 3y agoThis looks super interesting. I'll give this a go for a while to see how much I like it.
- programmer_dude 3y agoI have never felt the need to explicitly lookup history since I switched to fish shell. It has very good command completion (from history).
- p5a0u9l 3y agoIt’s indispensable in some workflows. Scoring history can help with otherwise difficult debugging, or looking up a variant to a complicated invocation that’s not the one suggested by auto complete.
- deleted 3y ago[deleted]
- userbinator 3y agoThe stock PS1 bugged me a bit, so I mangled it down to this That's not too far from this one which I use and have seen quite a few others use too --- really hate a lot of the newer defaults that hide the full path for some reason, and managed to convince a coworker who accidentally edited the file of the same name in the same directory with a different path to use it too: '\u@\h:\w$ ' Also I should mention that in this era of constant telemetry^Wspyware and tracking, everything you say can and will be used to identify or correlate you, and that does include using non-default configuration. Of course, how much this matters depends on the context in which you say it.
- deafpolygon 3y agoMine is even simpler... '> %d ' (yes, I use zsh) Root has '# %d ' Am I odd? I generally find I don't need /that/ much information on the shell.
- yjftsjthsd-h 3y agoI like to get exit codes, but otherwise yeah that's fine.
- ofalkaed 3y agoI use ... for user and []_ for root, I would rather not fill up terminal space with information I generally know. I really hate when the prompt causes things to wrap and I do not mind putting pwd or the like to use on those occasions I do not know.
- mock-possum 3y agoOh this person is living in a very different world than me.
- endorphine 3y agoCare to elaborate? What is so different between your setup? It seemed like a pretty standard setup to me
- mrweasel 3y agoIt's a really simply, bare bones, kinda setup. Many spend hours, weeks, months, if not years tweaking their setup. Everything from the shell to their editor get "riced up"[1] just the why they like it. It's usually beautiful to look at, but if like me you work on a large number of servers each day, it's kinda pointless, unless you insist on cloning your setup on each of the thousands of servers in your company. Personally I configure almost nothing, everything is standard. I do load a few Vim plugins for syntax checking, but that's about it. I don't even care if something is zsh, ksh or bash, I just care that it's not sh, csh or tcsh. The most customized thing I have is my ssh config. I'm sure I'm missing out on a ton of nice features, and I sometimes regret not learning tools to a larger extend, especially when others shows neat little shortcuts or speedy functions, on the other hand, I don't want the hassle. 1) https://www.urbandictionary.com/define.php?term=riced%20up https://www.urbandictionary.com/define.php?term=riced%20up
- CGamesPlay 3y agoI feel like there’s a sweet spot where I spend most of my time in a terminal but on a relatively small number of different servers, and that’s why I want things customized just so. It’s worth it because the number of machines is small.
- ranger207 3y agoI think that typically sysadmin-type people seem to have less customization, possibly because they ssh into so many boxes and dotfiles don't usually carry over.
- yjftsjthsd-h 3y ago> Quick, which of .bashrc, .bash_profile, .profile et al get run for any given type of login you do to a box? I appear to have just given up and symlinked them together. Anyone have a better idea? Edit: Actually, my profile apparently has a conditional to detect what shell it's loaded by (which I did remember), and for at least bash a conditional to detect interactive mode (which I did not). So I'm still dealing with this, just not at the file level.
- Flimm 3y agoI found this blog post really helpful in explaining the difference: https://shreevatsa.wordpress.com/2008/03/30/zshbash-startup-files-loading-order-bashrc-zshrc-etc/ https://shreevatsa.wordpress.com/2008/03/30/zshbash-startup-... It references this blog post: https://meta.ath0.com/2007/10/23/cleaning-up-bash-customizations/ https://meta.ath0.com/2007/10/23/cleaning-up-bash-customizat...
- axelf4 3y agoI have written a small reference for this that has served me well: [1]. [1]: https://github.com/axelf4/dotfiles#bash-startup-files https://github.com/axelf4/dotfiles#bash-startup-files
- blueflow 3y ago$ENV is for interactive shells, .profile is for login shells. Normal shells source these files according to to which of the two flags are set or not. To make make bash behave in a compatible manner, you need to: - Delete .bash_profile, so .profile gets sourced instead (works around bash ignoring .profile when .bash_profile exists) - At the bottom of .profile, call $ENV (works around login bash ignoring bashrc) - Make .bashrc call or be equal to $ENV - At the head of $ENV, do an early exit for non-interactive shells (works around bash sourcing the bashrc when invoked non-interactively via SSH or socket, also works around the previous workaround) In terms of startup logic, bash is the worst shell i've seen so far.
- mr_mitm 3y agoI still haven't figured out where the canonical place is to put modifications to $PATH. Now I just source ~/.profile from .zshrc and .xsessionrc and ignore that some directories sometimes appear multiple times in $PATH.
- akira2501 3y agoYou can customize LS_COLORS if you want, but I've never been mad at the defaults. Also, I prefer c-style escapes, which allows you to copy and paste the filename and use it in other commands: alias ls='ls --color=auto -F -b -T 0 -A' -F classify entries with (*/=>@|) -b use c-style escapes instead of quoting -T 0 do not use tabs for alignment -A show all dotfiles except . and .. Plus, I find colors to be insanely useful when my old eyes try to read 'ip' output, so I really do prefer: alias ip='ip --color=auto'
- Flimm 3y agoInteresting! I've been using "grc" to provide colours for commands like "ip", I didn't realise that "ip" had a "--color=auto" option.
- tommieb 3y agoAfter more than two decades - never knew ip had the --color switch, TIL and thanks! :)
- iforgotpassword 3y agoI really wish there were a unified environment variable to enable colors for everything instead of having a separate one for everything or having to clutter your bashrc with a trillion aliases.
- doubled112 3y agoI decided to clutter the filesystem instead and have my bashrc source a bunch more files. It helps me, at least.
- jwilk 3y agoColor support was added only in 2015: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=d7bd2db52c1fcfe5 https://git.kernel.org/pub/scm/network/iproute2/iproute2.git...
- Topgamer7 3y agoRemoving all syntax highlighting. You monster! How do you quickly determine logical chunks of things! Grep, coding, super useful to have colour!
- regularfry 3y agoI strongly suspect this is an example of a desirable disfluency. If you make things harder to visually distinguish, your brain takes in the information better because the parts that need to work harder influence attention.
- _moof 3y agoBy looking at it? Every time I see a screenshot of someone's super fancy color scheme it looks cacophonous.
- biftek 3y agoI also disable most highlighting. I find it terribly distracting when coding or doing other menial stuff, my exceptions are greping or diffing, but those only use 1-2 colors
- trallnag 3y agoAnyone else here managing his "dot files" with an Ansible playbook? In my environments files like .bashrc only contain a few statements that source other scripts where I inject / template my actual configuration.
- twp 3y agoI previously used Puppet, but you usually need root access on the machine to install Ansible or Puppet itself as they have a large number of dependencies and often add extra system services or user accounts. This is very heavy tool to install if you only need to update a few files in your home directory and install a couple of packages with sudo. For a longer answer, see https://www.chezmoi.io/user-guide/frequently-asked-questions/design/#why-not-use-ansiblechefpuppetsalt-or-similar-to-manage-my-dotfiles-instead https://www.chezmoi.io/user-guide/frequently-asked-questions....
- yjftsjthsd-h 3y agoEr, I install ansible in a virtualenv without using root. > and often add extra system services or user accounts. What? I'm less familiar with Puppet, but why would any of this need a service or extra account?
- regularfry 3y agoI do this. Bashrc, SSH key generation and distribution, a few development niceties and networking tweaks, all kept in sync with a Makefile and some ansible.
- renewiltord 3y agoHaha wow. I have a full color prompt with oh my zsh and starship. Overall, I like it though I don't really need a lot of it. The error code highlight and duration of last command are nice.
- twp 3y agohttps://chezmoi.io https://chezmoi.io is a dotfile manager that is runs on multiple OSes (including Windows) while handling differences from machine to machine, allows you to store your secrets in your password manager (so you don't have to store secrets in your dotfile repo), and it even supports the NO_COLOR environment variable. Check it out! Disclaimer: I'm the author. There's a comprehensive list of the most popular dotfile managers at https://dotfiles.github.io/utilities/ https://dotfiles.github.io/utilities/.
- Hasnep 3y agoCoincidentally, I migrated my dotfiles from a bare git repository to chezmoi yesterday, the experience has been great, thanks!
- doubled112 3y agoI have managed my dotfiles a few ways over the years. A deployment script in bash, GNU stow, YADM, dotbot, maybe a couple more. Chezmoi is where I landed too.
- atkailash 3y agoI’ve been using chezmoi for over a year now and having to set up two work computers and a new personal one in that time. It’s made that process significantly shorter and less painful.
- kps 3y agoThis seems to almost do what I need, but not quite; I wonder if I'm mistaken or if someone knows that one of the other dotfile tools would suit me. The major gap: Some files belong to external repositories (not all git), and some of these have contents that cross dot-directories. e.g. project repos A and B both contain material that should end up in ~/.local/share and material that should end up in ~/.config.
- bloopernova 3y agoThat sounds more like a job for plain old "install" which is part of GNU coreutils.
- wheybags 3y agoWhy does she hate colours so much?
- TheNewAndy 3y agoI am not the author, but I imagine that it could have started out as just a preference, but turned into great hatred as they kept on being introduced in more and more places. I don't mind colour, but really dislike incorrect colouring (not enough to any effort to do anything about it). Or maybe she really likes colour, but likes to use it very sparingly so it highlights things more effectively. I think there can be plenty of reasons, and I would be unsurprised if her reasons are ones that I guessed
- srhtftw 3y agoSome of us prefer tools which work best without them. Allow me to repeat my plea for CLI developers to take a little time to read https://no-color.org https://no-color.org and ensure their programs honor things like NO_COLOR, npm config set color false, TERM=dumb, INSIDE_EMACS etc. https://news.ycombinator.com/item?id=35017940 https://news.ycombinator.com/item?id=35017940
- munch117 3y agoColours interfere with scannability. It forces you to deal with text one colour region at a time, making it harder to take in the whole thing at once. Scanning is a skill you acquire with age. As you get older, and you more and more replace word-by-word reading with full-page scanning, colour becomes less attractive. Less attractive doesn't mean worthless. Colour just needs to carry its weight, by providing enough relevant information to compensate for breaking up scanning flow. So used sparingly, colours can be good. It's just that no one seems to use colours sparingly. You see things like giving ".gz" (and other compressed) files a different colour. I have no need for that, .gz is just one among a thousand file extensions that I know, I can read the file extension myself thank you very much. Even if I had a great need for recognising compressed files, I couldn't rely on colours for that: Colouring is too inconsistent between applications, whereas scanning text and spotting the .gz extension carries over to almost anything.
- fisian 3y agoI'm on so many different machines (mostly some embedded stuff/RasPis that need linux) that I ignore all these bad defaults. The only thing I find unbearable is vimdiff colors, that have the SAME or very similar foreground and background so it's impossible to read. (I don't remember, but believe it's just on some distros)
- g0xA52A2A 3y agoI share the same annoyance with quoting but avoid it differently by setting export QUOTING_STYLE=literal This means I don't have to be clever about thinking if I need to pass -N to ls depending which OS I'm on.
- Shorel 3y agoNo colours? Any non-coloured terminal feels dead to me. Half of the things I do in my dot files are related to adding colours. Including some long colour parameter string to be used with midnight commander.
- tomxor 3y agoI've been gradually dialling back colours in the terminal over the years. I find everything has just become too colourful for no apparent reason, when everything is highlighted it feels like nothing is highlighted and more distracting than anything... syntax highlighting is the only hold out I've kept so far.
- justsomehnguy 3y agoNo colours. Eg Docker defaults to DarkBlue on Black for some status states and it's barely visible on my setup at tge daytime. At night it's just incomprehensible, I need to turn off Night Light or ramp up brightness over 150%. No, I can't tune my environment, it's always some client's machine.
- tomxor 3y ago> Then I have a .xsessionrc which needs to exist because I now log in through xdm, and the window manager (fluxbox) ends up inheriting that environment. Yep, it doesn't get a .bashrc type thing applied to it. (Not gonna lie - this took a while to figure out. I've grown fond of just logging in via the tty and invoking startx... it's always there, even when your graphics drivers fail. I tried messing with xdms a long time ago when transitioning to i3wm, but it was just extra configuration, noise and inconsistency to sort out, without really gain anything useful for what is a single person machine. Simple is good.
- maccard 3y ago> it's always there, even when your graphics drivers fail. This sentence is jaw dropping to me. Maybe I'm not the target audience for this sort of ultra minimalist, ultra customised environment, but the concept of requiring a workaround because my graphics drivers aren't functional is something I cannot understand. Why would you willingly work in that environment? In the last decade of being a professional programmer, my graphics drivers have _never_ failed me to that level. They're not perfect, but they _never_ fail to initialise.
- tomxor 3y ago> the concept of requiring a workaround because my geaphics drivers aren't functional is something I cannot understand It's not a workaround, it's just a perk, when I moved to "ultra customized" as you put it, you don't want to have to configure masses of stuff, i3wm is good for this, it's pretty minimal to configure... an XDM was just more work to configure, but with little utility from my perspective, also I work on the cli a lot so it doesn't feel unnatural to be welcomed by a tty. And yeah the final perk, Linux wasn't always so compatible, and even in more recent history nVidia graphics drivers can still be problematic. About 10 years ago i think, I used Linux on a 2008 MBP, and freeBSD actually, those things had craptastic nVidia GPUs, you know the batch that came with the first gen unleaded soldier fiasco and when nVidia lied to apple about their thermal specs before they had a falling out and everyone got their GPUs underclocked in firmware to push failures out of warrantee - i digress - anyway the linux support for any nvidia stuff back then was terrible, and very flimsy on dual GPU laptops. For Apple it was more tricky still because you needed to write an Apple specific gmux switcher before even attempting to boot with the nvidia driver, and if that actually worked when you start X then you would lose visual access to your tty because it had no modsetting support... which ironically made using tty instead of an xdm a disadvantage for when the graphics driver failed once in X... I sometimes tried to bring it back to life essentially blindfolded on the tty if X died, mixed success. Point is, on any laptop with nvidia back then, you usually had to do some level of mucking around on the tty anyway before being able to depend on anything graphical like an xdm... and pray it doesn't break on the next driver update. Frankly right now, we are living in Linux utopia, a lot of hardware "just works".
- rmm 3y agoHow do people manage their custom bash profile across machines. Currently I just add a small if statement that checks if my custom file with all my little aliases I have put together over the years is there it sources it. Is there a better way?
- fcsp 3y agoI use https://github.com/thoughtbot/rcm https://github.com/thoughtbot/rcm, which works smoothly and includes support for host-specific files
- HDevo 3y agoI use https://www.chezmoi.io/ https://www.chezmoi.io/, which deals with that with templates and/or scripts. It's very flexible, so it can feel overkill, but I'm very fond of it.
- frumiousirc 3y agoSome application configuration does not allow host name resolution. In this case a symlink to a host-specific config file is used. Like, for `kitty` I make a `<hostname>.conf` for each host on which I have an account and then make a local, per account symlink to a literal `local.conf` included from `kitty.conf`. This same pattern is useful in configs that do allow dynamic host name resolution as it robust against cases where the host name unexpectedly changes. All dot files are distributed via `vcsh` with the remote `git` repo in a personal `gitea` instance.
- earthling8118 3y agoI've used many different methods but none of them stuck until I started using https://github.com/nix-community/home-manager https://github.com/nix-community/home-manager
- 2b3a51 3y agoMy slightly odd preference is... bash-5.2$ cat .nanorc set zero Together with UXTerm.vt100.translations: #override \n\ Ctrl Shift <Key>N: scroll-back(1, halfpage) \n\ Ctrl Shift <Key>T: scroll-forw(1, halfpage) \n\ Ctrl Shift <Key>C: copy-selection(CLIPBOARD) \n\ Ctrl Shift <Key>V: insert-selection(CLIPBOARD) \n\ Ctrl Shift <Key>H: set-altscreen(toggle) in .Xresources. See https://aduros.com/blog/xterm-its-better-than-you-thought/ https://aduros.com/blog/xterm-its-better-than-you-thought/
- tschumacher 3y agoPut your PATH into .profile when you want it to apply to your whole session. https://superuser.com/questions/183870/difference-between-bashrc-and-bash-profile/183980#183980 https://superuser.com/questions/183870/difference-between-ba... https://superuser.com/questions/789448/choosing-between-bashrc-profile-bash-profile-etc/789705#789705 https://superuser.com/questions/789448/choosing-between-bash...
- conaclos 3y agoMy main aliases are: a more human-friendly ls and an alias of rm which attempts to detect mistakes: alias l='command ls -Av1h --color=always --time-style=long-iso --group-directories-first' # -A: show all, including dotfiles, except . and .. # -v: natural sort of number # -1 (one): list (use -l for long version) # -h: human-readable sizes alias rm='command rm -Iv' # -I: prompt once before removing more than three files or recursively # -v: verbose I redefine also $HISTFILE to ensure that every shell get its own temporary history: HISTFILE="${XDG_RUNTIME_DIR:-/tmp}/shell-history-$$"
- liendolucas 3y agoI group different kind of settings under particular files. My .bashrc has `source ~/.rc.d/pyenvrc`, `source ~/.rc.d/gitrc` and so on which can help to organize yourself if you have too many custom settings. I also have a very tiny set of useful functions that I might occasionally use from some scripts. For example: # Changes the current working directory to the running script. cd_running_script_dir() { cd "$(dirname "$(readlink -f "$0")")" } # Display an error message and abort the running script. # # Arguments: # $1: A string with error to be displayed before aborting. abort() { ERROR=$1 >&2 echo "${ERROR}" kill $$ } # Return a program's full path if exists or display an error # message and abort script execution. # # Arguments: # $1: A string with the program's name to be looked up. get_program() { PROGRAM_NAME=$1 PROGRAM_PATH=$(which "${PROGRAM_NAME}") if [ -z "${PROGRAM_PATH}" ]; then abort "Error - ${PROGRAM_NAME} is not installed." fi echo "${PROGRAM_PATH}" unset PROGRAM_PATH unset PROGRAM_NAME } Given the sort of subtle nature of sh that for example misplacing a whitespace or a character can render a whole script wrong, from time to time I add these snippets so I can entirely forget how to do some regular things by sourcing `~/.scripts/lib.sh`. It's also a great way to extend your sh knowledge and learn about customizing your environment. Yes these are silly functions, but their main purpose is to make sh snippets more readable. Because I don't like to always display the same wallpaper over and over again my .xinitrc contains: "${HOME}/.scripts/set-random-background" & which is: #!/usr/bin/env sh # Randomly sets a wallpaper from a directory containing images. # # Usage: # ./set-random-background # Adjust global settings accordingly. WALLPAPERS_PATH="${HOME}/.scripts/assets/wallpapers" set_random_background() { FEH=$(get_program "feh") if [ -d "${WALLPAPERS_PATH}" ]; then WALLPAPER=$(ls "${WALLPAPERS_PATH}"/* | sort --random-sort | head -n1) if [ -n "${WALLPAPER}" ]; then ${FEH} --no-fehbg --bg-center --bg-scale "${WALLPAPER}" fi fi } main() { if [ -n "${BASH_LIB}" ]; then . "${BASH_LIB}" set_random_background fi } main
- deleted 3y ago[deleted]
- spudlyo 3y agoexport PS1='\h:\w\$ ' This is my prompt as well, it was the default Slackware prompt, which I’ve also used since the mid 90s.
- juujian 3y agoGot my hopes up, but no, not a graphviz post.
- deleted 3y ago[deleted]
- bloopernova 3y agoI wrote a gist about a year ago that discusses installing various tools into MacOS -- powerlevel10k prompt, fzf, ripgrep, difftastic, some git aliases, asdf and more: https://gist.github.com/aclarknexient/0ffcb98aa262c585c49d4b3f3ae24019 https://gist.github.com/aclarknexient/0ffcb98aa262c585c49d4b... Wow, it has 40 stars! I'm kind of shocked, I think it was way under 20 last time I looked. :) Feeling pretty good about that, if I've helped just that many people, then I feel like writing that was more than worth it!
- Cockbrand 3y agoI learned a lot from Kali Linux's zshrc [0]. But then I'm certainly no expert in customizing my shell environment, as I usually mostly stick with the distro's defaults. Still, now mine is a bit nicer. It also includes the `ip --color=auto` thing, which is mentioned in other comments and which I hadn't known about either. [0] https://gist.github.com/Anon-Exploiter/4e12193df0099183d18720c6471d571a https://gist.github.com/Anon-Exploiter/4e12193df0099183d1872...
- dhosek 3y agoThe mention of .plan and .project brings back memories. You used to be able to do things like finger dhosek@ymir.claremont.edu and see if I was logged on and what I had to share with the world (which was a long series of quotes that ran several screens). I remember learning that the AMS had shorter hours on Fridays thanks to Barbara Beeton’s .plan file.