Straight.el: Suggestion : make byte-compile output optional

Created on 5 Dec 2020  Â·  4Comments  Â·  Source: raxod502/straight.el

I'm specifically thinking about the progress variables
https://github.com/raxod502/straight.el/blob/f6663b1de0fb5d9c64528e4f7f8bb914f49bb6d2/straight.el#L4339

Basically, having a switch to set a straight-debug mode to be able to inspect byte compilation if we want to would be really useful

build system byte compilation debug feature user option

Most helpful comment

@gagbo: Merged #657 which implements a defcustom, staright-byte-compilation-buffer.
It defaults to "*straight-byte-compilation*", so you should see all the output in that buffer on the latest develop branch.

All 4 comments

Yep, seems like a good idea to me.

657 may obviate the need for such an option, as the byte-compilation output could be redirected to a straight-byte-compile-buffer. This could be a defcustom which defaults to something like *straight-byte-compilation*. Users who wish to drop the byte-compilation output could set it to nil.

Yes, that seems like an elegant solution.

@gagbo: Merged #657 which implements a defcustom, staright-byte-compilation-buffer.
It defaults to "*straight-byte-compilation*", so you should see all the output in that buffer on the latest develop branch.

Was this page helpful?
0 / 5 - 0 ratings