Laurent Orseau

In the editor would be ideal, but I think it's also valuable (and probably simpler) on the command line. I see it at first as 1. Analyse the file 2....

`apply / skip / apply-all … / apply none / abort` ?

Racket's `read-syntax` does parse 'special-comments' that appear during parsing, with their associated value, but unfortunately they are discarded when constructing the syntax objects :( Ideally, read-syntax should (optionally) parse comments...

Is it possible to extend the read table to override the parsing of `#;` maybe?

> Maybe, but I'm not sure, and it seems like it might be tricky. I'd rather just avoid the problem entirely, especially since any solution would be specific to `#lang...

Just a suggestion: Instead of closing the proposal, maybe you could tag it as `controversial` or `matter-of-taste` or something, which enables others to refine the idea, and also this rule...

I think that's fine, do you find it annoying?

include all the methods that can be overridden/augmented by a tool/plugin, such as `on-tab-change`, as for example in @sorawee's [plugin](https://github.com/sorawee/drracket-cmdline-args/blob/master/tool.rkt#L131). Look for example for methods that can be augmented in...

That should be relatively easy to do indeed, since it's just a matter of adding a word at the end of a file, [as per the given link](http://aspell.net/man-html/Format-of-the-Personal-and-Replacement-Dictionaries.html). I guess...

Works with me too. It's just that I prefer to avoid `system` calls whenever possible (in particular for portability reasons), but otherwise I don't mind that much.