(Replying to PARENT post)
I understand bash is the basis of so many things, that its importance is just enormous.
But at the same time, I'm appalled by its syntax, idioms, etc. It's barely readable for the casual reader that I am. I wonder why nobody tries to provide a meaningful alternative. I've seen some (in python for example) but I'm kind of surprised nobody puts more money in such an effort.
For example, the "trim string" function described at the beginning of the book is horrible (although probably very clever). Why not simply provide a built in function ? That would make code so much cleaner...
I ask the question honestly, it's not a rant :-)
(Replying to PARENT post)
Highlights include:
- Bind C-c/C-v to Copy/Paste, bind C-g to sigterm (Note: Breaks docker interactive unless you mount bashrc into /etc/bashrc or similar!)
- Autorun tmux on SSH session
- Syntax/colour highlighting in zsh interactive, I think there's some diff/less/man magic in there too!
- Log all shell activity to .shell_logs (Be _super_ careful with this one, breaking it could prevent you opening an interactive shell
- Useful grep defaults, particularly relevant when using .shell_logs
Bashrc: https://gist.github.com/YoloClin/f4c82a6e693000a2da20e8029a4...
Zshrc: https://gist.github.com/YoloClin/ffd82f441d292ccc5f25c62a80c...
One thing I've lost love for is Powerline9k - Right-aligned data breaks copy/paste functionality, and patching fonts to get UI-arrows is fiddly for little functional value. If I ever need to fiddle with that stuff again, I'll configure a regular theme to do similar and go without the UI-arrow breaks.
I was considering hiding history-relevant log data (such as current system time) to behind a carriage return, something like PS1="$(date)\r$PS1".
I'm interested in hearing others' cool, non-standard hacks!
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
* RipGrep: Replace Grep and it is blazing fast
* exa: Replace ls with many more options
(Replying to PARENT post)
(Replying to PARENT post)
i know the correct path forward here is, of course, diving into the guts of spacevim and tinkering until it works for me, but i will post one quirk as it will probably be some time before i will be able to write my own comprehensive plugin:
the hugofy/markdown plugins seem to all do this awful thing in which they render the markdown on the fly. it's kinda neat for basic text formatting, but my god it is an utter nightmare if you have any sort of URL's or images, because the second you key in that second bracket, it suddenly dissapears and you're left having to basically guess your way through the process of typing the url and closing out the shortcode.
if someone knows of a markdown editor that plays nice, i'd love to see it. hope im not overlooking something painfully obvious here
anyways, i picked a hell of a time to dive into the commandline, a year ago i came across scoop/chocolatey and quickly discovered WSL, and thanks to a phenomenal amount of work by some great folks (even you, Person Reading This), my desktop is not much more than the lobby i pass through before going to where the magic happens: https://imgur.com/a/iCpWZAC
(Replying to PARENT post)
(Replying to PARENT post)
This being said, I'm in love with `fzf`, my workflow improved markedly after scripting (on mac)
`ggvi() { git grep "$@" | fzf | sed \"s/:/ +/\" | cut -d \":\" -f 1 | gxargs -r -o vim }`
(Replying to PARENT post)
(Replying to PARENT post)
export FZF_DEFAULT_OPTS="--ansi --preview-window 'right:60%' --preview 'bat --color=always --style=header,grid --line-range :300 {}'"
(Replying to PARENT post)
You can also open a list of files in separate tabs with the -p argument. So βvim -p CppFile.*β will open the .h and .cpp in separate tabs for example. You can then Y/p between the two buffers.
Itβs so useful that I always βalias vi=vim -pβ in my .profile.