Clojurians Log v2

just uppercase d, f and b

:simple_smile:

hi all - any idea how to get the mac to send Control and Shift to emacs? (so I can do Cntrl-) for example?

you mean Control-_?

I mean Control-) (sorry, missing bracket before)

to slurp

at the moment the terminal beeps whenever I send Control and Shift

for info, this is with emacs-mac installed from brew. If I install the Emacs for App bundle then it works when Emacs launches as an App, but not from the terminal

and of course the excellent Prelude 😉

hmm, I use the standard GNU Emacs from homebrew

and I don’t have to do anything special in iterm

I am using terminal, let me try iterm2

Now if I press Control -Shift-0 I get a 0 printed out.

I have Control mapped to capslock if that makes any difference? I think I will create a new user and see if that helps - I don’t recall doing anything weird in the . files but maybe.

nope - still the same, I literally downloaded iterm2; ‘brew install emacs’, install prelude and that’s it...

I guess I can live with using the Emacs for Mac app for now

@colin.yates: One way to investigate is to type C-h k followed by that key combo

It should tell you what Emacs sees when you press the key

A lot of terminals are very limited in what key combinations they understand

And if the terminal doesn't understand the key, it's never gonna reach Emacs

All that said, why not just use the standalone emacs? :simple_smile:

@malabarba: it just beeps. I think you’re right; it is never getting to emacs.

The standalone emacs feels a little bit laggy (2014 macbook pro 15”) compared to the terminal

I am using the terminal.app on Yosemite

It's probablyt a slugish minor mode

linum-mode is a common cause of that

The footer bar is claiming ‘Clojure , guru cljr Guide FlyC- company Heml ws Projectile SP/s Pre'

I don't know all of those. But not all minor-modes show up on the mode-line

Try M-x linum-mode

It should say whether it got enabled or disabled

ah yes, it just said it was disabled

ah, ok, line-numbers mode

that does make it quite a bit snappier now - thanks

Cool

You can try out the profiler too

1. M-x profiler-start 2. Type around some stuff, do your usual things. 3. M-x profiler-report

It might show you what's taking up the most time

thanks, I will try it. I am suprised nobody else seems to be hitting this - it must be something I have done, but I can’t think what… oh well :simple_smile:.

@bozhidar: It wouldn’t be the first time I’ve over-complicated things. Hah.

@colin.yates: I think your basic problem is quite obvious 😛

I knew you would be lurking :simple_smile:

Hehe