Clojurians Log v2

wrt the helm situation, i've tried ivy and selectrum over the last couple of days and am leaning toward selectrum.

ivy has a few advantages imho > like ivy-occur and some various counsel plugins

I'd love to use selectrum instead personally (ivy code is... involved), but no ivy-occur equivalent is a blocker for me

ah i don't know what ivy-occur is, but i will look into it.

thanks for mentioning it.

ivy-occur is awesome, shotcut that opens all the candidates in an occur buffer

it's very useful

that does sound pretty nice.

there's also sub-selection that might be missing from selectrum

perhaps it's a matter of time before some similar features appear 🙂

I hope so. I opened an issue for ivy-occur equivalent on selectrum months ago tho

the sub-selection feature I mentioned earlier is ivy-restrict-to-matches I think

ah, thanks for the specifics, that should make searching easier

it allows narrowing in steps: "show all candidates for foo" > then for all these show candidates for "bar" > etc etc

ha ha ha -- i should stop listening now so i can "tolerate" what i've currently got 🙂

🙂

in terms of features, abo-abo's stuff will likely be difficult to match

yes, also counsel-ag, I am not sure there's a standalone equivalent that can be run with selectrum

ah, it looks like may be an issue where ivy-occur was discussed: https://github.com/raxod502/selectrum/issues/15

yes, i see you there 🙂

hmm, i wonder what the status is...the end of the issue seems to sound somewhat hopeful

not sure either

When I have emacs open to a clojure source file, I’m seeing a decent amount of input lag when typing. The problem seems to be worse when using multiple emacs window divisions, or when the application window is occupying the full screen (a 5K monitor). I’ve tried using M-x profiler-start, but the results weren’t very informative:

- command-execute                                                 612  90%
 - call-interactively                                             612  90%
  - byte-code                                                     523  77%
   - read-extended-command                                        523  77%
    - completing-read                                             523  77%
     - completing-read-default                                    523  77%
      - read-from-minibuffer                                      154  22%
       + command-execute                                           11   1%
       + timer-event-handler                                        6   0%
       + nrepl-client-filter                                        1   0%
       + redisplay_internal (C function)                            1   0%
  - funcall-interactively                                          89  13%
   - execute-extended-command                                      89  13%
    + sit-for                                                      86  12%
    + command-execute                                               3   0%
+ ...                                                              56   8%
+ redisplay_internal (C function)                                   5   0%

i notice in that trace something about nrepl so is it the case you are connected to some repl? if you aren't connected to the repl (so just using clojure-mode.el), do you notice similar input lag?

grasping for straws here, but there are some tidbits in here: https://emacs.stackexchange.com/questions/598/how-do-i-prevent-extremely-long-lines-making-emacs-slow

killing the nrepl didn’t fix it

switching to M-x text-mode didn’t fix it

multiple windows definitely makes it worse

if you turn off font-lock does it help at all?

that's one thing i try when things get slow

i guess using text-mode is like turning off font-lock-mode

i presume it's the same no matter which file of clojure code you are taking a look at?

may be you've already tried looking at a clojure file after starting emacs with emacs -q

there was mention of performance issues and a 5k display in this issue: https://github.com/sabof/org-bullets/issues/11

didn't know there was also emacs -Q...TIL

hrm, looks like the problem isn’t present with emacs -nw, running my normal configuration

there is a reddit thread mentioning some slowness of emacs on macos: https://www.reddit.com/r/emacs/comments/d2n2wh/emacs_is_slow_on_macos/ -- is this happening on macos?

yes, macos. I’ll see if brew has other emacs versions

fwiw, i tried recently: https://github.com/d12frosted/homebrew-emacs-plus -- and specified version 27

emacs-plus is dramatically faster. Thanks for the help

hi. this may sound stupid, but somehow I lost a file in emacs. I am positive it was there, I am positive I saved it numerous times, because I had it open for several days, and when I was creating a new file (with random clojure exercises) the previous one simply disappeared.. I though it’s just in another buffer, but it’s gone for good. No success searching for it in spotlight either, no success with recover-file nor recover-session… any ideas, please?

does anyone have experience with enhancing an existing flycheck plugin by making it tramp-compatible?

Maybe it was in your /tmp folder?

If you have Time Machine running you could look for it

no time machine, I am using icloud & dropbox

but is there a way to show history of open files in emacs actually?

yes, recentf-open-files

thank you!

did you not already find out that flycheck needs modification? https://github.com/flycheck/flycheck/issues/1816#issuecomment-673159577