On Thu, Apr 30, 2020 at 11:16 AM Hendrik Boom
wrote:
> On Thu, Apr 30, 2020 at 09:36:15AM +0200, Dexter Lagan wrote:
> > There’s one thing I noticed: if debugging is disabled, then
> parenthesis highlighting is also disabled (as well as other visual aids, if
> I remember well?). The editor
I have debugging disabled, but my parenthesis highlighting is NOT disabled.
Are we talking about the same parenthesis highlighting? Can you attach the
screenshot of this "parenthesis highlighting is also disabled" to the
mailing list?
On Thu, Apr 30, 2020 at 12:36 AM Dexter Lagan wrote:
>
On Thu, Apr 30, 2020 at 02:46:00PM -0400, David Storrs wrote:
> On Thu, Apr 30, 2020 at 11:16 AM Hendrik Boom
> wrote:
>
> > On Thu, Apr 30, 2020 at 09:36:15AM +0200, Dexter Lagan wrote:
> > > There’s one thing I noticed: if debugging is disabled, then
> > parenthesis highlighting is also
I think there are tiny bits of documentation that are automatically
generated(OpenGL?), but I think they are well labeled.
In general its not a problem, its mostly typed in by humans, typos and all.
s.
On Thu, Apr 30, 2020 at 2:16 PM Dexter Lagan wrote:
> Thanks, this guide is great. I'll
I put my foot in my mouth again, it's working. I must have had something
else disabled. I clearly remember not being able to make the cursor 'jump'
around expressions.
Dex
On Thu, Apr 30, 2020 at 9:16 PM Sorawee Porncharoenwase <
sorawee.pw...@gmail.com> wrote:
> I have debugging disabled,
Also, if I remember correctly, the timings given in the said (excellent)
tutorial are very conservative or outdated. If you have a multicore
machine, it will speed up the process by up to a factor 8.
On Thu, Apr 30, 2020, 15:42 Sam Tobin-Hochstadt
wrote:
> On Thu, Apr 30, 2020 at 9:09 AM Ben
>
> I hate being at the mercy of whatever editor I'm stuck using.
I agree with this in principle, but in practice, it's really a matter of
what mainstream editors support. Editors in the past don't universally
support automatic indentation, and I could imagine a criticism like
"Indentation
On Thu, 30 Apr 2020 at 20:01, Hendrik Boom wrote:
> [...]
> > Also is there a programming editor that *won't* do parenthesis matching?
>
> Evidently the Racket editor whan debugging is disabled,
I’m not sure that’s true.
Kind regards
Stephen
--
--
You received this message because
On 4/30/2020 5:40 PM, Sorawee Porncharoenwase wrote:
:
To clarify what I mean: non S-exp languages usually have a line as a
unit of code, so editors need to support "jump to the beginning/end of
line" to make editing pleasant.
Actually, in the majority of programming languages there is
No it’s not, I checked again and couldn’t reproduce the problem. Please
ignore my earlier comment.
I’ve been tracking a bug that causes the colouring of a part of the code as
comment and disable parenthesis handling, and since I switch debugging on and
off often, I assumed it was related.
Thanks for sharing. I see "Nested parentheses" only one way to represent
tree structure. There are certainly other cleverer ways to do it. Once it
appears, the representation of the tree transform (macro) may also be
better. I'm looking forward to seeing better representation.
On Thu, Apr 30, 2020 at 02:40:00PM -0700, Sorawee Porncharoenwase wrote:
> >
> > I hate being at the mercy of whatever editor I'm stuck using.
>
>
> I agree with this in principle, but in practice, it's really a matter of
> what mainstream editors support. Editors in the past don't universally
>
Hi Jay,
Thanks for the recap. I suspected that I had enough context,
so it helps to have confirmation from a core dev.
It seems I should leverage a patchwork of sources to support
different use cases.
~slg
‐‐‐ Original Message ‐‐‐
On Thursday, April 30, 2020 8:57 AM, Jay McCarthy
Only a small number of zone formats are supported in parsing mode.
This is discussed a bit in https://github.com/97jaz/gregor/issues/25.
The situation could definitely be improved.
- Jon
On Thu, Apr 30, 2020 at 11:33 AM Tim Hanson wrote:
>
> p.s. I'm stuck on parsing one pattern that comes up
Thanks for the quick reply, Jon!
OK, good to know. Maybe I can add the ones I need (if I can figure out how...).
:)
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
Hi Sage,
Racket has a very high standard of backwards compatibility where we
strive for programs to work continuously after many many years. In
most cases, we've been able to live up to the standard with the core
pieces of Racket. I can think of only a few times where we broke
compatibility and
Thanks, this guide is great. I'll make sure I fix whatever problem I find
when I scour the docs. I do have a question however: say I find a typo in a
function definition, is there any part of the doc that is automatically
generated, and should not be updated, or updated with specific attention?
On Thu, Apr 30, 2020 at 9:09 AM Ben Greenman
wrote:
>
> On 4/29/20, Sorawee Porncharoenwase wrote:
> > (Not directly related to Rhombus) Speaking of “how to contribute”, I find
> > that it is not friendly at all to setup stuff in order to contribute to
> > Racket core and main distribution.
On Thu, 30 Apr 2020 11:16:10 -0400, Hendrik Boom
wrote:
>I stongly recommend that we get a language with less of a
>parenthesis problem so that code is readable without having to haul
>it into a specialised editor.
>
>It is possible to do this without creating a hugely complicated and
On Thu, Apr 30, 2020 at 09:36:15AM +0200, Dexter Lagan wrote:
> There’s one thing I noticed: if debugging is disabled, then parenthesis
> highlighting is also disabled (as well as other visual aids, if I remember
> well?). The editor also feels faster because of this, but navigating
>
On 4/29/20, Sorawee Porncharoenwase wrote:
> (Not directly related to Rhombus) Speaking of “how to contribute”, I find
> that it is not friendly at all to setup stuff in order to contribute to
> Racket core and main distribution. According to
>
p.s. I'm stuck on parsing one pattern that comes up in my data. Here's a
corresponding test:
(parameterize ([current-locale "en"])
(check-equal?
(parse-datetime "Sun, 21 Jun 2015 17:50:44 -0500 (CDT)" "EEE, dd MMM
HH:mm:ss ()") (datetime 2015 6 21 17 50
I just read myself, I meant runtime errors, not compile-time errors. One big
complain I hear from people used to compiled languages - when they first use
dynamic and interpreter languages - is the idea of having errors occur at
runtime, which ‘should’ have been picked up by the interpreter
I'd forgotten the tutorial to contributing - someone kindly reminded me
recently
https://blog.racket-lang.org/2017/09/tutorial-contributing-to-racket.html
This covers everything from fixing a typo to contributing to the racket
language and the main distribution.
it is worth the read!
S
On
Yo Racketeers!
Someone recently mentioned that is was tricky to update documentation. it
can be.
I thought I'd provide the steps I took to create a PR for the DrRacket
documentation in the hope that they are useful for others who see an issue
with documentation but finding locating the right
Alex, that looks like an interesting workflow. Maybe worth a blog post? ;)
On Thu, Apr 30, 2020 at 12:11 AM Alex Harsanyi
wrote:
>
> You could both send packages to the package catalog and instruct your
> users to use a different package source if they wish to use old versions.
> I don't see
There’s one thing I noticed: if debugging is disabled, then parenthesis
highlighting is also disabled (as well as other visual aids, if I remember
well?). The editor also feels faster because of this, but navigating
parentheses becomes slightly more tedious without it.
Dex
> On Apr 25,
*hello i need again your help i have an examen in one day i need to
understand this programme : Define an anagr function taking as a parameter
a character string and returning the list of all anagrams of this string.
We are not concerned in this question of whether an anagram appears several
28 matches
Mail list logo
