This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (3)
- # babashka (5)
- # beginners (68)
- # calva (34)
- # cider (6)
- # cljsrn (3)
- # clojure (48)
- # clojure-australia (2)
- # clojure-europe (1)
- # clojure-nl (4)
- # clojure-spec (28)
- # clojurescript (10)
- # conjure (20)
- # datahike (1)
- # deps-new (1)
- # depstar (27)
- # events (2)
- # fulcro (61)
- # graalvm (32)
- # membrane (18)
- # off-topic (20)
- # practicalli (10)
- # reagent (2)
- # shadow-cljs (8)
- # slack-help (20)
- # spacemacs (9)
- # sql (5)
- # vim (10)
- # xtdb (8)
A question about "unletting" a conjure variable. It seems that I can only unlet, once the buffer has been loaded
if I try to do it whilst entering vim, vim complains that the
g:.... variable is not found
I am doing this atm, I suppose good enough
let g:conjure#mapping#def_word = v:false
you can unlet if conjure is loaded but you haven't entered a buffer for your target language yet
The last couple of Conjure releases, I've not been able to update Conjure via vim-plug. Is there perhaps some rebasing going on that makes it so that I can't
git pull on the master branch?
I get a message like:
When I cd into
x conjure: fatal: Not possible to fast-forward, aborting.
git status, I see:
Note the part about my branch and origin/master having diverged. When I do
On branch master Your branch and 'origin/master' have diverged, and have 1 and 10 different commits each, respectively. (use "git pull" to merge the remote branch into yours) nothing to commit, working directory clean
git pull, there are a ton of merge conflicts.
You might have to remove the repo and resync? I tried to rename master to main a few updates ago and it broke vim-plug users spectacularly 😞
That's what I've done, the last couple of releases. I made a point to do that after you restored master as the default branch.
What's weird is that the git log seems to be in a "grafted" state, which I'm not sure what that means.
After deleting and re-cloning the repo, when I do
git log, there is only a single entry:
It seems like something is quirky, as if the commit I'm currently on disappears from the log with each release, or something like that. Are you doing anything out of the ordinary with the git repo?
$ git log commit 0aa1e8f78e8e0746a6026260f4d9a64a0bdfbf7a Author: Oliver Caldwell <[email protected]> Date: Thu Jan 28 17:05:05 2021 +0000 Bump to v4.13.0
Expanding on the "grafted" thing: I have a fancy git log command that I run via a shell alias:
When I do that, I see the word "grafted" on each commit:
git log --graph --pretty=format:"%C(bold blue)%h%C(reset) %C(bold green)%ad%C(bold yellow)%d%Creset %s%C(bold white) — %an%C(reset)" --decorate --all --date=short
* 0aa1e8f 2021-01-28 (grafted, HEAD -> master, tag: v4.13.0, origin/master, origin/develop, origin/HEAD) Bump to v4.13.0 — Oliver Caldwell * 94a55a4 2021-01-16 (grafted, tag: v4.12.0) Add a note about the packer issue — Oliver Caldwell * ae46046 2020-12-30 (grafted, tag: v4.11.0) Sync sponsors — Oliver Caldwell * 078b058 2020-12-21 (grafted, tag: v4.10.0) Mention how to swap to the stdio client — Oliver Caldwell ... etc. ...
I wonder if vim-plug is setting some interesting git settings to do some sort of shallow clone? Although I don't know of anything that would cause this behaviour...
Hmm. No idea. I'll keep an eye on it whenever the next Conjure release comes down the pipe. Maybe the issue will correct itself?
Yeah, I'm not doing anything special whatsoever, so I guess it's local repo oddness caused by some weird coincidence :thinking_face: