You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pop-to-buffer steals keyboard focus, which is very disruptive (especially as a nix novice who needs many iterations on my .nix files to get anything working). Can error messages be displayed with display-buffer instead? Or if they're short, just use message? (all the error messages I've been getting have been one-liners, although I'd prefer to have nix-buffer pass --show-trace to nix-build to get more details. I don't understand why this isn't the default).
I'm also getting uninterpreted ansi escape codes in the error buffer. I'm not sure whether this is the fault of nix-buffer or nix-build (I'm using nix 2.0, FWIW), but it would be good to either run this through the comint ansi filter or convince nix-build that it's running in a dumb terminal without color support. (This is especially annoying because the escape codes are confusing ffap)
The text was updated successfully, but these errors were encountered:
Re: pop-to-buffer, I'm not especially familiar with emacs's error reporting facilities, I'd be happy to consider a PR switching us to a more appropriate one
Re --show-trace: It's not the default because IIUC nix evaluation slows down and uses more memory. Maybe some nix-buffer option to turn it on, or to re-run with show-trace if evaluation fails, would be a good idea here
Re ansi codes: If there's a way to convince emacs to ignore them (or better yet, render them appropriately) that'd be great!
Yeah, I'm not familiar with the right way to do this kind of thing in emacs either. I just suggested display-buffer because it looks like the first reasonable option I stumbled across. This is worth some research to compare with other similar modes.
As for the ansi codes, there's a function ansi-color-apply that claims to do this. (This is what comint-mode uses)
pop-to-buffer
steals keyboard focus, which is very disruptive (especially as a nix novice who needs many iterations on my.nix
files to get anything working). Can error messages be displayed withdisplay-buffer
instead? Or if they're short, just usemessage
? (all the error messages I've been getting have been one-liners, although I'd prefer to havenix-buffer
pass--show-trace
tonix-build
to get more details. I don't understand why this isn't the default).I'm also getting uninterpreted ansi escape codes in the error buffer. I'm not sure whether this is the fault of
nix-buffer
ornix-build
(I'm using nix 2.0, FWIW), but it would be good to either run this through the comint ansi filter or convincenix-build
that it's running in a dumb terminal without color support. (This is especially annoying because the escape codes are confusingffap
)The text was updated successfully, but these errors were encountered: