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?

which kind of keys?

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

But with -nw, that command doesn't work

that's control-super )?

ctrl - shift

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

How would I do that? Excuse my ignorance

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-)

which means its not getting the shift

I actually just set this up this bind:

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

It ignored that bind as well

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

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

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

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

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

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

It just sees it as )

C-g is correctly picked up properly thoguh

I guess I could bind it to M-)

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

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

I'm not, arch

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

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?

Erm. Are you not seeing a stacktrace?

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

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

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

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

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