Fork me on GitHub
#emacs
<
2019-04-18
>
PB15:04:43

I've noticed that when running emacs with the option -nw certain keybinds dont work. Is there something I can do to fix this that doesn't involve explicitly re-binding all combinations I find that don't work?

dpsutton15:04:49

which kind of keys?

PB15:04:43

So as an example. In gui emacs, I use C-s-) to slurp with paredit.

PB15:04:53

But with -nw, that command doesn't work

dpsutton15:04:57

that's control-super )?

PB15:04:03

ctrl - shift

dpsutton15:04:19

can you check if your terminal is swallowing the control shift?

PB15:04:44

How would I do that? Excuse my ignorance

dpsutton16:04:02

i think i normally check by running C-h c which finds out which binding is at which key. and it says the key input you've entered. So in your case it might say that nothing is bound to C-)

dpsutton16:04:10

which means its not getting the shift

PB16:04:33

I actually just set this up this bind:

(global-set-key (kbd "C-)") 'paredit-forward-slurp-sexp)

PB16:04:23

It ignored that bind as well

PB16:04:39

So it seems, using C-h c that any command C-) or C-S-) is not being picked up

PB16:04:02

However M-S-) shows up as M-) whcih might be right, I"m unsure at this point

dpsutton16:04:40

wait, is there a thing as shift parens? on my keyboard it requires shift to get the paren

PB16:04:20

I think you can do something like s-S-y

PB16:04:38

But i'm probably wrong. I think you're right about the shift beign silent

PB16:04:51

Eitehr way C-h c and trying to do C-) doesn't get detected

PB16:04:05

It just sees it as )

PB16:04:32

C-g is correctly picked up properly thoguh

PB16:04:05

I guess I could bind it to M-)

PB16:04:32

Also, interestingly enoguh, using C-h c. If I simply do M-n it shows up as M-n. But if I do C-n M-n it's read as C-n ESC n

dpsutton16:04:19

oh yeah. terminals are funky. are you on mac? if so there are ways to customize iterm to not be wonky

PB16:04:29

I'm not, arch

PB16:04:56

So I'm sure there is a way to fix this. I'm just not sure what I'm looking for

robertfw16:04:32

Hello - recent convert from vim to (spac)emacs here. I’ve been enjoying the features for running tests and getting a summary straight into a buffer - I’m wondering if there are any suggestions for how to include debugging information in that summary? Usually when I am digging into a failing test it’s useful to get the log output for the test to get some more visibility. I suppose I could put in a failing assertion with the data I’m interested in, are there any better options?

PB17:04:02

Erm. Are you not seeing a stacktrace?

robertfw17:04:26

If I crash out yes, but when I’m not fixing a crash, I’ll use things like timbre.spy to look at values (either in the test, or in code I’m debugging). When I used to run tests directly in the repl I’d see those flow past while the test was running, but in this case the test summary doesn’t capture that

robertfw17:04:38

right now i’m using (is (= false symbol-im-interested-in)) so I get the info dumped out in my test summary as a failed assertion

PB17:04:17

So you can still do that, it would still show up in your repl

PB17:04:35

But if you're looking for it inside of the test-results buffer. I'm not really sure of a solution

robertfw18:04:53

Thanks. I’m still figuring out suitable workflows so I may just be trying to hammer a square peg into a round hole