Unless it produces output, like in the case of the issue I experienced during my live demo. 🙂
yeah the trace over fibs 🙂 i've never used trace before and it looked amazing
in emacs / prelude / cider, what is the thing called that gives a visual effect on the line I'm typing when I press enter?
I want to turn that off in vterm
@borkdude Can you show me the visual effect as I don't remember anything that's triggered on enter.
@bozhidar It might be an effect of zenburn, I'm not sure how I can replicate this...
when I disable global-hl-line-mode
then it goes away, but it isn't the same as hl-line-mode
Hmm, I trying this now on the latest Prelude but I don't see any effect when I press Return.
I'll let you know when I see this again.
@bozhidar There I have it, after calling cider-connect and hitting return in the REPL.
I have a similar effect called beacon, it might be that https://elpa.gnu.org/packages/beacon.html
Yeah, that's beacon.
I've removed it from Prelude recently, that's why I wouldn't see the effect. 🙂
Normally there should be an animation only for bigger movements in the buffer, though. Guess that's some bug in beacon.
ah, then I should update my prelude :)
Updated and I don't see it anymore
I want to disable hl-line-mode in vterm. How can I do that?
(add-hook
'vterm-mode-hook
(lambda()
(setq hl-line-mode nil) ;; hmm..?
(setq show-trailing-whitespace nil)))
@bozhidar What is the new line number stuff and how do I disable it?
global-nlinum-mode
From the changelog/docs:
* Enable `nlinum-mode` by default. Can be disabled by setting `prelude-minimalistic-ui` to `nil`.
Ops, that should be t
, not nil
. 😄
like this? (setq prelude-minimalistic-ui t)
?
fwiw it doesn't work for me (in init.el)
It should go the preload
config - e.g. preload/personal.el
.
The var needs to be set before the UI is initialized otherwise some UI elements would briefly appear and then disappear.
Makes sense!
That worked.
@bozhidar what is used for highlighting the current line in a buffer and how do I turn this off for vterm only? I have a half-assed attempt a couple of lines up
global-hl-line-mode
. I you think you can just add a hook for vterm that looks like (lambda () (hl-line-mode -1))
.
Haven't used vterm
, but it guess it defines a major mode named vterm-mode
or something like this can you can hook into.
FYI if you want to keep the beacon package for some things, beacon-mode
should toggle it, its just a minor mode.
Yeah, don't really care about that one, but thanks :)
that's true. I found vterm using a couple of searches as one of the best alternatives to ansi-term, etc
Ironically I just started using it with Spacemacs, I quite like it... maybe I just havent used it long enough to get bored with it 🙂
vterm is what people using Spacemacs have been recommending for a while, looks very good.
I tried this, but even in the buffer where I'm executing (hl-line-mode -1)
the current line stays highlighted
I found this code on stackoverflow. It works:
(global-hl-line-mode)
(make-variable-buffer-local 'global-hl-line-mode)
(add-hook 'some-mode-hook (lambda () (setq global-hl-line-mode nil)))
(add-hook
'vterm-mode-hook
(lambda()
(setq global-hl-line-mode nil)
(setq show-trailing-whitespace nil)))
The only unsatisfying thing about this is that I don't know why one has to do it like this.You wrote a blog about it and you didn't even tell me? https://emacsredux.com/blog/2020/11/21/disable-global-hl-line-mode-for-specific-modes/ Thanks!
So, I've heard, but I was always too lazy to set it up. I did it just now and it looks pretty nice indeed.
That's weird. I can reproduce it for every buffer, so it's not something to do with vterm. Seems something is off in hl-line-mode
as normally the non-global version of the mode should work just fine within one buffer to disable/enable it.
hi! I'm tackling this: https://github.com/clojure-emacs/cider/issues/2901
the remaining problem is that cider-font-lock-as-clojure
doesn't work well with mixed Clojure code and ANSI color codes. cider-ansi-color-string-p
(which is used in cider-font-lock-as
) only applies the color codes if the string starts with a color code (e.g. "\033[33mHello\033[0m"
). in matcher-combinators we have "(mismatch \033[33mHello\033[0m)"
etc. what's the best solution here? is always running ansi-color-apply
on the font-locked Clojure code acceptable for test reports?
Can't we just adjust the predicate method?
> is always running ansi-color-apply on the font-locked Clojure code acceptable for test reports?
Probably that'd be fine.
yep, adjusting the predicate method is what I meant :)
I’ll open a PR soon-ish then
here's the one for cider-nrepl
: https://github.com/clojure-emacs/cider-nrepl/pull/683, unrelated to the coloring issue.
I'm not sure how to test it, though. my first idea was to add a cider.nrepl.middleware.test-custom-print
ns with a failing test containing custom print logic, filtering it out with :test-selectors
, and then calling it with session/message
to run the assertions. does that sound good?