I was optimistic this could work because when you launch DrRacket with bad flags it tries to open files with these names, at least on Ubuntu: $ drracket my-file.rkt --line will try to open the file "--line" and complain with a GUI message. So I guess that means the non recognized flags are sent to the `command-line` arguments of DrRacket's main.rkt.
I didn't know about raco pkg update --clone, that's cool! On Fri, May 29, 2015 at 12:22 AM, Robby Findler <ro...@eecs.northwestern.edu > wrote: > This is fine advice. > > If you wanted to prepare just a little bit more, you might run "raco > pkg update --clone drracket" (and then respond "yes" to the prompt). > This would, in the directory you're in, create a "drracket" sub > directory and a few others that contain the source code of DrRacket, > linked to the git repository where the source lives. You could then > use the usual git commands to set up a pull request. > > As for the earlier comments, about the "files-to-open" definitions, > etc, I'm not sure that that path works since the OS is in control of > what information gets set to Racket (and then interpreted by DrRacket) > I believe. But creating a little script that makes a network > connection could work. > > Alternatively, you could write something inside DrRacket that mimic'd > the GUI and then make direct calls to open the files and jump to > appropriate line numbers. You would start by reading the documentation > about DrRacket plugins, either way, I suppose. > > hth, > Robby > > > On Thu, May 28, 2015 at 12:42 PM, Laurent <laurent.ors...@gmail.com> > wrote: > > Regarding contribution, this should at least be a good start: > > http://blog.racket-lang.org/2012/11/tutorial-contributing-to-racket.html > > > http://www.greghendershott.com/2013/04/a-guide-for-infrequent-contributors-to-racket.html > > > > However, note that racket has been split into many different packages > > relatively recently, leading to DrRacket being in a separate package. > > > > But if you just want to hack it without having to think about > contributing > > for now, I think you can just download and install Racket normally in a > > local directory, make the changes you want to the files in the drracket > > subdirectory, make sure you recompile the collections with `raco setup > > drracket` for example, and restart drracket. Once you're happy with your > > result, you can start wondering about how to submit your changes. > (Someone > > correct me if this is a bad advice!) > > > > On Thu, May 28, 2015 at 6:18 PM, Laurent <laurent.ors...@gmail.com> > wrote: > >> > >> For what it's worth, I think these are some of the relevant lines: > >> > >> > https://github.com/racket/drracket/blob/21c155c46c58c5d01ff984df27a77c19f4481640/drracket/drracket/private/drracket-normal.rkt#L19 > >> > >> > https://github.com/racket/drracket/blob/21c155c46c58c5d01ff984df27a77c19f4481640/drracket/drracket/private/drracket-normal.rkt#L48 > >> > >> > https://github.com/racket/drracket/blob/21c155c46c58c5d01ff984df27a77c19f4481640/drracket/drracket/private/main.rkt#L832 > >> > >> > https://github.com/racket/drracket/blob/21c155c46c58c5d01ff984df27a77c19f4481640/drracket/drracket/private/main.rkt#L850 > >> > >> Instead of keeping only the #:args arguments and treat them all as > files, > >> one could then add more parsing to the command-line form and retrieve > line > >> numbers. > >> > >> The last line above might be where something about setting the carret > >> position could be done. > >> > >> On Thu, May 28, 2015 at 5:20 PM, Josh Grams <j...@qualdan.com> wrote: > >>> > >>> On 2015-05-28 09:59AM, Matthias Felleisen wrote: > >>> >I know DrRacket has some downsides, but I sure wish many more people > >>> >would see the light, use it, and help identify and better yet fix the > >>> >problems. > >>> > >>> I was interested in that, but couldn't figure out how to build it. > >>> > >>> I had found a couple of things which seemed like they might be easy > >>> beginner tasks and started to dive into the source code, but...it took > >>> me a while to even *find* the git repository containing DrRacket, and > >>> then I couldn't figure out how to build it, even after a couple of > hours > >>> of tinkering and digging through the code and docs. > >>> > >>> I asked how to build it from source, but just got pointed to the > >>> snapshot binaries instead of getting a real answer. > >>> > >>> --Josh > >>> > >>> -- > >>> 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 > >>> email to racket-users+unsubscr...@googlegroups.com. > >>> For more options, visit https://groups.google.com/d/optout. > >> > >> > > > > -- > > 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 > > email to racket-users+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > -- 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 email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
