This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-01
Channels
- # adventofcode (93)
- # announcements (44)
- # asami (23)
- # aws (1)
- # babashka (48)
- # beginners (112)
- # calva (26)
- # cider (57)
- # clj-kondo (17)
- # cljfx (5)
- # cljs-dev (21)
- # clojure (124)
- # clojure-europe (19)
- # clojure-hungary (40)
- # clojure-nl (3)
- # clojure-spec (7)
- # clojure-uk (3)
- # clojurescript (3)
- # cursive (81)
- # datalog (11)
- # events (21)
- # exercism (1)
- # fulcro (37)
- # graalvm (1)
- # introduce-yourself (8)
- # jobs (1)
- # lsp (1)
- # malli (5)
- # membrane-term (17)
- # minecraft (3)
- # nextjournal (5)
- # off-topic (14)
- # other-lisps (14)
- # polylith (58)
- # reagent (16)
- # reclojure (3)
- # reitit (6)
- # remote-jobs (1)
- # shadow-cljs (55)
- # spacemacs (15)
- # testing (2)
- # tools-build (7)
- # tools-deps (191)
Has anyone had success with MacBook Thunderbolt dock and external displays being detected upon waking from sleep? I've been trying the TS3 Plus with my MacBook, and I often must replug the cables or restart the laptop for my displays to be detected. From my research, it sounds like this is a widespread problem, but perhaps someone has found some dock that always works as advertised?
Crazy. I can't believe that's the norm. As a sanity check, I've ordered 3 different Thunderbolt 4 docks (Sonnet Echo 11, Blaze, Razer) to see if the problem continues. It feels like it's a Mac issue and not a dock issue.
Do you have some technique to get all your windows back to the position they were in before?
I’m going to buy one of these model. hoepfully this is some software issue
FWIW, I use Plugable's TBT3-UDC1 to connect to 2 external 4K DisplayPort monitors (plus keyboard/mouse/Ethernet) with a couple of Intel MacBooks, and it remembers layout/window positions on plugging in and wakeup. It's reliable with an Air (2020 / Intel integrated graphics), but a Pro (16" 2019) with discrete Radeon graphics sometimes kernel panics on wake/plugin (macOS Catalina & Big Sur).
I have a plugable as well with a 2020 16” mbp and was getting kernel panics until I switched from HDMI to DisplayPort and haven't seen the issues since. Don't have any issues with display waking either
not sure where to ask this: at what point do you guys think we need to add attribution for borrowed source code? i’ve got two functions that i’m lifting from cider-nrpl-middleware and throwing into debux. does it make sense to mark that somehow?
I also mention code/concepts used from other places under license(s) section in README. Example https://github.com/clj-commons/rewrite-clj#licences and from https://github.com/lread/test-doc-blocks#license.
I've used function https://clojure.org/reference/metadata for this purpose in the past - I added a :license
key like this:
{:name "MIT License"
:source ""}
Noting it in the README is a good idea tooyeah i like the metadata or comment version for small sections, the readme makes sense if its larger parts. thanks!