Julian Scheid

@rmosolgo also, just checking that you saw this issue isn't primarily about error reporting, but about a specific bug to do with whitespace handling?

Not really, it would be a breaking change. But making the type declaration match the data shouldn't be causing much problems, and worst case at compile time.

I think this would also help with a Google Closure Compiler error I'm running into: ``` stdin:245570: ERROR - functions can only be declared at top level or immediately within...

I'm afraid there's nothing I can do here without a repro.

Just a quick note that I've upgraded to Xcode command line tools 15.0.0 and rebuilt from scratch, and it's still working (snappy and not flickering.)

I'm trying your build scripts. First, running just `./build-emacs-from-tar emacs-29.1.tar.bz2 release` doesn't seem to work: [logs](https://gist.github.com/jscheid/6a6e78cc7de08c4fa18b5f5a9d2abd6a) (yes the output is garbled like that in my terminal) Using the `--verbose` flag...

I've got `./combine-and-package Emacs-29.1-14-x86_64.tar.bz2` to work, but maybe the Readme should point out that one needs Ruby 2.x, run `cargo build --release` and copy the `launch` executable around. Anyway, the...

> It seems like the easiest alternative is to add package.json to .prettierignore, which will use Yarn's formatting rather than Prettier's, but still prevents conflicts between them. This is what...

@alphapapa hmm, now I can't get it to flag _any_ packages not listed as a dependency. For example, the below passes `lint-compile` and `lint-package` (as long as `async` and `package-lint`...

Right, got confused here -- this ticket wasn't even about `lint-package` originally but about `lint-compile`. Ignore the above, here is the correct repro: ```elisp ;;; main.el --- Summary ;;; Commentary:...