This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-31
Channels
- # architecture (5)
- # beginners (35)
- # boot (150)
- # cider (1)
- # clara (7)
- # cljs-dev (131)
- # cljsrn (10)
- # clojure (76)
- # clojure-austin (3)
- # clojure-berlin (1)
- # clojure-brasil (1)
- # clojure-chicago (2)
- # clojure-dusseldorf (1)
- # clojure-italy (30)
- # clojure-nl (2)
- # clojure-russia (40)
- # clojure-serbia (2)
- # clojure-spec (25)
- # clojure-uk (13)
- # clojured (2)
- # clojurescript (106)
- # core-async (29)
- # datascript (65)
- # datomic (38)
- # emacs (8)
- # funcool (8)
- # hoplon (6)
- # jobs (3)
- # klipse (93)
- # luminus (16)
- # lumo (4)
- # off-topic (2)
- # om (11)
- # onyx (13)
- # pedestal (4)
- # protorepl (3)
- # re-frame (40)
- # reagent (31)
- # ring (6)
- # ring-swagger (4)
- # slack-help (5)
- # spacemacs (13)
- # untangled (17)
- # vim (2)
Found a problem with the desktop
approach above (see 1/28) -- it reopens all buffers, even those which aren't currently displayed, so over time you build up a vast list of open buffers (all that you've ever opened since starting to use this approach, except any you've explicitly killed). I expect there's a reasonable workaround, but wanted to point it out in case anyone else has been trying this approach.
@eggsyntax one workaround i've employed around the general problem of lots of open buffers, is marking old buffers in ibuffer manually
(ibuffer :variables
ibuffer-group-buffers-by 'projects
ibuffer-old-time 8)
8 there is hrs, i think default is 72
Does marking them like that cause them to be automatically killed? If so, do you happen to know what the behavior is if a buffer has unsaved changes?
na marking just 'selects' them, similar to selecting by regex
then there's a separate command to close them, that confirms with you when there are unsaved changes
ibuffer-mark-old-buffers
is the selection function