@borkdude if you're fine with antora (which is a distribution of asciidoc with nice things like versioning), then there's a theme that may fit your description. A demo here https://asciidoctor-docs.netlify.app/asciidoctor/current/
source code of the theme here https://github.com/asciidoctor/asciidoctor-docs-ui
or you may just steal some code from that theme ;)
No asciidoc plugin needed for overriding a single template. Just the -t option to the cli iirc.
Hey everyone! I tried to view the code of conduct but didn't have access. Wanted to see if it's ok to post Clojure jobs in this channel/slack group?
We (moderators) assume members are able to find appropriate channels via the Slack UI but that often doesn't appear to be the case 😐
Thanks for linking @seancorfield. Just a heads up the code of conduct linked in this channel is https://goo.gl/VsJ8q8 and is not public and cannot be viewed 🙂
Oh, I wonder when that stopped being a public document? Sorry. I'll mention it to the admin team.
there are some job specific channels just for that. #jobs #remote-jobs should help in getting the highest concentration of people looking for jobs
and clojure jobs are always welcome, I'm sure
I know a lot of Clojurians use Vim/SpaceMacs… has anyone hit the problem where they cannot override their OSX /usr/bin/vim with the newest Vim 8.2 version… using homebrew? It looks like homebrew removed the override command, instead of deprecating it ?
basically, someone on the brew team royally screwed this up, by removing a much needed flag command
But homebrew is installing binaries into /usr/local/bin
@delaguardo yes, I worked around it… by adding the /usr/local/bin path into my bashrc… homebrew was supposed to take care of updating the system default exe but they removed the command flag to do that.
I am irritated. Who knows. Maybe it was a huge security hack… over riding the system default… but it cost me an Sunday, hunting this down. I am ready to dump homebrew and just compile everything like I do on Linux.
when I first started out coding, as a child… I did not have to spend half my week reading stackoverflows and githubs, tracking down broken bugs and broken tools… things just worked. I could spend 90% of my time coding.
I think it’s uncharitable to call this a royal screwup. Even compiling everything manually on Linux the default would be to make install into /usr/local. This or /opt has been the expected behaviour of non OS managed packages on unix platforms for many, many years. /usr/local/bin is also higher precedence by default than /usr/bin on almost any sane unix, including, I thought, all current macOS installs out of the box.
@nathantech2005 Heh, I use linuxbrew to manage everything on Ubuntu 🙂
yea, I am researching… why OSX will not allow me to change /usr/bin/vim
ahh ok. thank you so much for that update…
even with root
I think it is pretty standard practice for Linux/OSX users to carefully manage their command path env variables, to be in the order they wish.
And I thought that when I used homebrew on both Linux and OSX that it updated my bashrc for me, but it has been long enough that I don't truly recall now.
yes… and Linux allows me to setup my bins how I want… OSX is not allowing me… some kind of over ride wheel permissions things
nope. I had to add a path inside bashrc… just 1 little line
@nathantech2005 I'm not sure but I think macOS kinda assumes that those directories are managed by the OS and aren't written to so it can safely updates these during upgrades. Also, there is:
$ cat /etc/paths
/usr/bin
/bin
/usr/sbin
/sbin
which contains the paths that are included in your shell by default probablybecause there’s 2 versions of vim on my system, now
You can use sudo on OSX if you really want to, but recent OSX versions are doing more security measures to lock down the standard binary directories than older versions did.
yea, I understand… OSX has put some kind of idiot-proof feature into it… I get it
nope, sudo is not working
it might be a Catalina thing
I just upgraded to Catalina
@nathantech2005 let me google this for you: https://stackoverflow.com/a/36734569/6264
I just checked PATH
on my old Mac and /usr/local/bin
is part of the core path, ahead of /usr/bin
-- I didn't have to do anything to set that up that way. But that's 10.12.
anyways, really apppreciate the feedback
I have a ~/Dropbox/bin folder where I put binaries I like, and they come with me every system I work on
@seancorfield interesting…. yes. that’s the fix
@borkdude seriously?
yes
you can just swap out your bins when needed?
Interesting bit from that SO answer:
Note that while /usr/local/bin doesn't exist by default, it is in the default PATH, so as soon as you create it, it'll be searched for commands.
hmm, ok
yes, that’s what I had to do… on Catalina… was add /usr/local/bin to the path
export PATH=“/usr/local/bin:$PATH”
added that line to my .bashrc
because homebrew put the exe into the path
for 8.2
the default shell is zsh now on macos
vim 8.2
ahh really, I did not know, they moved to zsh
zsh is actually really good
I'm still on bash because I stayed on 10.12 I guess?
yea, I was afraid to upgrade to Catalina… but it went smooth
in the past, upgrades, with Apple, have bricked my devices
I won't upgrade because almost every macOS upgrade breaks my dev env setup 😐 When I replace this 8 year old iMac, I'm going to Windows 🙂
and I mean, only 2 versions later, bricked
upgrades bricked my mobile devices..
but the desktop upgrade went really well
8 years? yea, not going to work
I would not even try that
(after many iPhones over the years, I finally switched to Android this year -- happy with that)
this is going off on a tangent…
It started on a tangent 🙂
but after many years, I finally found how to fix my usb-c on apple
@seancorfield best laugh all weekend, thanks
I don't know if I would prefer Android over Apple, if your Google account gets disabled you might be locked out of certain app accounts. Nasty.
disabled google account?
woah… better have a few accounts, I guess
I have gotten locked out of MFA…
where MFA backup codes did not work
well, anyways, time for a break… thank you much… great thoughts… at least it’s fixed
it was introduced in El Capitan as System Integrity Protection https://support.apple.com/en-us/HT204899