Closed liuyinz closed 2 months ago
One option would be to add to mhtml-mode-hook
a function that sets apheleia-formatter
to whatever you desire it to be. The buffer-local variable overrides automatic formatter detection.
But, since mhtml-mode
is built in, I guess we should make this work by default. I'd like to do it in a way that does not special-case one particular mode in the internal code. Let me add something generic for that, one moment.
How do you feel about the approach in https://github.com/radian-software/apheleia/pull/303? I'm not sure if it's the best, but it seems not unreasonable to me.
LGTM. mhtml-mode
is the only mode which can fontify css/js code correctly in html file so far, thanks for your great package !
I use web-mode
, personally, but that has its own problems.
In
mhtml-mode
, the varmajor-mode
is changed when your point moved into different position:css-mode
;js-mode
;mhtml-mode
.so when I point at section, apheleia select
prettier-css
which is wrong, to fix the problem we need to always getmhtml-mode
as major-mode .@raxod502 I guess need to fix function
apheleia--get-formatters
, does issue https://github.com/radian-software/apheleia/issues/29 is related to this either ?