Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-09 Thread Philippe Mechaï
Just for the record, the bug seems to be known to someone :) https://github.com/racket/gui/blob/master/gui-lib/framework/private/color.rkt#L989 On Mon, Oct 8, 2018 at 8:15 PM Robby Findler wrote: > I like the idea that you suggested where the parens keep their paren > color but the rest of

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-08 Thread Robby Findler
I like the idea that you suggested where the parens keep their paren color but the rest of the text becomes comment colored. It's not a trivial change, but it seems doable. Robby On Mon, Oct 8, 2018 at 12:37 PM Christopher Lemmer Webber wrote: > > It sounds nice, but I wonder if it would be

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-08 Thread Christopher Lemmer Webber
It sounds nice, but I wonder if it would be hard to shift consistently in the right direction for both light and dark themes... I guess if the code's opacity was reduced that could be a universal solution. Matthias Felleisen writes: > +1 > > >> On Oct 8, 2018, at 11:57 AM, Sam Tobin-Hochstadt

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-08 Thread Matthias Felleisen
+1 > On Oct 8, 2018, at 11:57 AM, Sam Tobin-Hochstadt wrote: > > A suggestion: what if #; comments used the code coloring, but shifted > somewhat, or grayscaled, or something along those lines? > > Sam > On Mon, Oct 8, 2018 at 11:56 AM Matthias Felleisen > wrote: >> >> >>> On Oct 8,

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-08 Thread Sam Tobin-Hochstadt
A suggestion: what if #; comments used the code coloring, but shifted somewhat, or grayscaled, or something along those lines? Sam On Mon, Oct 8, 2018 at 11:56 AM Matthias Felleisen wrote: > > > > On Oct 8, 2018, at 11:44 AM, Greg Hendershott > > wrote: > > > > p.s. > > > > On Mon, Oct 8, 2018

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-08 Thread Matthias Felleisen
> On Oct 8, 2018, at 11:44 AM, Greg Hendershott > wrote: > > p.s. > > On Mon, Oct 8, 2018 at 11:41 AM Greg Hendershott > wrote: >> Another use case (that Mattias might not love) is somewhere for "usage > > Apologies for the typo, Matthias! No worries. And for the record, I also use #;

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-08 Thread Greg Hendershott
p.s. On Mon, Oct 8, 2018 at 11:41 AM Greg Hendershott wrote: > Another use case (that Mattias might not love) is somewhere for "usage Apologies for the typo, Matthias! -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-08 Thread Greg Hendershott
Sexpr comments are interesting because people want them to act mostly like sexprs -- for indentation, and for structural editing/display like paredit or rainbow-parens. At most they should look like comments. Or not even that. As this thread shows. :) Another use case (that Mattias might not

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-07 Thread Neil Van Dyke
FWIW, an unreleased Racket mode for Emacs (which did fast incremental lexing, and some higher parsing[1]) intentionally colored the entire expression after `#;` as a comment.  I don't recall whether I decided to have it skip over the commented expression for sibling-level sexp-based editor

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-07 Thread Christopher Lemmer Webber
Daniel Prager writes: > If only there was a way to have the best of both worlds. > > E.g. change the background color for #; to something reminiscent of the > foreground color of regular comments: > > (display #|Comment|# > ; comment > #;(string-join "comm" "ent") >

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-07 Thread Daniel Prager
If only there was a way to have the best of both worlds. E.g. change the background color for #; to something reminiscent of the foreground color of regular comments: (display #|Comment|# ; comment #;(string-join "comm" "ent") "Hello world") Or perhaps something like

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-07 Thread Matthias Felleisen
>> I find the #; construct very convenient for commenting out sexps, but in Dr >> Racket the visual cue of switching to comment-color is missing. >> >> Example (in Racket 6.12): >> >> [image: Screen Shot 2018-10-07 at 10.19.09 pm.png] >> >> Expected: >> >> *#lang racket* >> >> (display

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-07 Thread Matthias Felleisen
For quite some time, I have > On Oct 7, 2018, at 8:05 AM, Christopher Lemmer Webber > wrote: > > I agree that they should be shown as comments. > > In many ways I like what happens (probably unintentionally) in my emacs > setup: I have rainbow-delimeters enabled, which colors the

Re: [racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-07 Thread Christopher Lemmer Webber
I agree that they should be shown as comments. In many ways I like what happens (probably unintentionally) in my emacs setup: I have rainbow-delimeters enabled, which colors the parentheses. When I comment out the s-exp with #; the sexp looks commented out, but the parentheses remain colored.

[racket-users] Should #; comments be colored as comments or code in Dr Racket?

2018-10-07 Thread Daniel Prager
I find the #; construct very convenient for commenting out sexps, but in Dr Racket the visual cue of switching to comment-color is missing. Example (in Racket 6.12): [image: Screen Shot 2018-10-07 at 10.19.09 pm.png] Expected: *#lang racket* (display #|Comment|# ; comment