This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (1)
- # announcements (2)
- # beginners (20)
- # calva (44)
- # cider (60)
- # clj-kondo (6)
- # clojure (27)
- # clojure-dev (2)
- # clojure-europe (8)
- # clojure-italy (18)
- # clojure-mexico (5)
- # clojure-nl (61)
- # clojure-spec (12)
- # clojure-uk (101)
- # clojurescript (82)
- # cursive (2)
- # data-science (21)
- # datomic (24)
- # fulcro (19)
- # graalvm (5)
- # hoplon (11)
- # jobs-discuss (35)
- # juxt (7)
- # keechma (6)
- # off-topic (21)
- # pedestal (5)
- # planck (2)
- # qa (43)
- # re-frame (3)
- # reagent (7)
- # reitit (4)
- # rewrite-clj (12)
- # sql (10)
- # testing (4)
- # tools-deps (6)
- # vim (23)
- # xtdb (3)
@lady3janepl when I finally meet you, it will be weird if you aren't cartoon Velma. That's my only image of you in my head.
@lady3janepl I read the
:language [:pl, :en, :jp] entry of your introspection and initially thought it said Perl until I didn't see
more like, inspired by linguistics: http://world.std.com/~swmcd/steven/perl/linguistics.html
we even say "idioms" and "idiomatic" at things which are seen to be "in the spirit" of a certain language
Perl and Lisp were the two languages that I encountered which felt like I was downloading my brain directly into a program, fluently
Ah, yes. The "context" aspect of Perl was the most frustrating (initially) and powerful (permanently). But also really prone to misinterpretation.
with the side effect that if you read that a year later, it sometimes read like binary -.-
otoh, the ability to grasp
%foo representing 3 distinct variables came in handy when I encountered Lisp-2 languages.
@lady3janepl I can’t begin to tell you how many times
perl -i -p -e "s/thing/thang/g;" myhugefile.txt has saved my life.
tis amazing, in fact, I was looking at the man page right now to figure something out
I use ripgrep from Spacemacs,
SPC /, it's great for searching through specific project files
@minimal: thanks for reminding me… I forgot I had that installed and hadn’t bound it to a key.
I’ve got regexp buffer search as C-s and helm-do-ag (interactive search) as M-C-s which makes finding something super simple
I use counsel-projectile-git-grep, counsel-recent-f and counsel-projectile-find-file and I am a happy bug
Any requests for the type of workshops wanted the day before ClojureX this year, Sunday 1st December (or we could try Saturday 30th if preferable). Its a still a long way away, but creating new workshops takes time... Workshops are usually 2-4 hours in length and highly practical / minimal theory. Also any volunteers to give a workshop this year ? If not, I can always do a whole day of Spacemacs indoctrination 😂😂😂😂😂😂
@jr0cket - I am going to have to say that if I can__ I will come along and help, and nearer to the time I will be able to be more concrete, but for now it's too far out to plan.
You have reminded me that I need to start putting my talk proposal together though...
I could do something with serverless cljs, but I’ll probably have to rewrite it twice by then haha
@alex.lynham only twice 😁 I usually refactor many times... In fact I changed the ClojureBridge curriculum for almost every event we have done (I like to see if the coaches are paying attention).
haha no I don’t mean revise, I mean start from scratch - I find anything cljs is out of date p quick!
I have an embarrasingly n00b linux question.
I have updated my
~/.profile to enable ssh daemon for Yubikey.
I use gnome terminal which runs
When I create a new gnome terminal, it doesn't auto-pickup the change I made; I have to manually
source ~/.profile to make it work.
What am I doing wrong?
they do - I have NEVER manged to get anything to run in .profile using a terminal emulator
I am aware that I am almost certainly showing my own ignorance, but if you put it in .bashrc it will at least work. I believe it to be the case that one should__ use .profile, but I've never made it work.
export SSH_AUTH_SOCK="$(gpgconf --list-dirs agent-ssh-socket)" if that helps anyone)
the .profile stuff is to do with whether bash is being invoked as a login shell or interactive shell, suffice to say that a .profile is only read during login
There may already be a ".profile" in your home, if you cat it, you'll see it sources in your .bashrc
for more hairy details, if you man bash and go to the
invocation section, you'll see it there in it's glory
man bash and read the 3 paragraphs in the middle of the INVOCATION section. But @dharrigan is bang on.
FTR I find
.profile etc pretty useless on macos. They make more sense on Linux in some situations… IIRC some login managers would source
.profile etc for you when starting an X session after logging in.
which would provide a way to set environment variables etc that are visible to all processes including graphical ones.
e.g. if you want your gui Emacs to see the same env you set at the terminal in
.bashrc you can wire things up by moving that to
.profile and sourcing it in the right way.
/.profile or /.bash_profile should be sourced every time you log in. ~/.bashrc should be sourced everytime you start bash (IIRC)
.profile in the root of your home directory should contain lines to source the
This allows you to put all your settings into
# if running bash if [ -n "$BASH_VERSION" ]; then # include .bashrc if it exists if [ -f "$HOME/.bashrc" ]; then . "$HOME/.bashrc" fi fi
.bashrcand have them for both login (and gui apps) and terminal shell.
Confused by bash initialisation? You need not be after this straightforward and easy to follow diagram: http://www.solipsys.co.uk/new/BashInitialisationFiles.html
I am doing a broadcast on regex with Clojure on Saturday morning, 10am UK time... so its time to learn regex properly (at least for a day) https://www.youtube.com/watch?v=iTimmZcNToY