Re: [racket-dev] Racket and Text Editors

2011-08-05 Thread Vincent St-Amour
I've added an updated version of the document to the Guide.

If you think it's not in the right place, I'm fine with putting it
elsewhere.

Vincent


At Thu, 04 Aug 2011 16:30:47 -0400,
Vincent St-Amour wrote:
> 
> 
> As I mentioned at RacketCon, I've been working (with help from Asumu
> Takikawa and Jon Rafkind) on a document that provides pointers to
> tools for using Racket with popular text editors.
> 
> I now have a draft of it on my webpage:
> http://www.ccs.neu.edu/home/stamourv/using-racket-with-your-editor-of-choice.html
> 
> I think this would be a nice resource to have somewhere in the Racket
> documentation. Does anyone have an idea where it should go?
> 
> I'd also like feedback on the document itself. It's not especially
> detailed, and I'm sure I forgot a lot of useful things.
> 
> Vincent
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Racket and Text Editors

2011-08-05 Thread Vincent St-Amour
At Fri, 5 Aug 2011 03:22:07 -0400,
Eli Barzilay wrote:
> The problem is that the meta collection is not intended for
> distribution.  Even if it's moved to some collection that will get
> included, it's an abuse of what `collects' means at the moment.

I see. How about a `contrib' directory at the top level of the
distribution? That would be a good place if we ever want to
distribute, say, quack as part of the Racket distribution.

> > > * `check-requires' is even less important than that...  Including
> > >   it means including a whole bunch of other things (for example,
> > >   the macro stepper's textual interface).  If anything, add it as
> > >   an xrepl command.
> > 
> > Adding it to xrepl is a good idea.
> 
> Tell me how to call it, and I'll add it.

`check-requires' sounds good. Maybe with `cr' as an available
abbreviation?

As for inclusion in xrepl, `show-requires' (from
`macro-debugger/analysis/check-requires.rkt') may be a better starting
point than `check-requires-script.rkt'.

Vincent
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Racket and Text Editors

2011-08-05 Thread Eli Barzilay
9 hours ago, Vincent St-Amour wrote:
> At Thu, 4 Aug 2011 18:08:58 -0300, Rodolfo Carvalho wrote:
> > 
> > About Bash completion, [...]
> 
> That's a good point.
> 
> I think it would be nice to have it be part of the regular
> distribution. Eli, is there a way to do that?

The problem is that the meta collection is not intended for
distribution.  Even if it's moved to some collection that will get
included, it's an abuse of what `collects' means at the moment.


9 hours ago, Vincent St-Amour wrote:
> 
> I didn't want to repeat information that was already in the xrepl
> documentation, but you're right that highlighting some of the
> features is probably a good idea.

Yes, these highlights fit well with this text.


> > * `check-requires' is even less important than that...  Including
> >   it means including a whole bunch of other things (for example,
> >   the macro stepper's textual interface).  If anything, add it as
> >   an xrepl command.
> 
> Adding it to xrepl is a good idea.

Tell me how to call it, and I'll add it.

-- 
  ((lambda (x) (x x)) (lambda (x) (x x)))  Eli Barzilay:
http://barzilay.org/   Maze is Life!
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Racket and Text Editors

2011-08-04 Thread Vincent St-Amour
I agree with most of your points, and will fix the document
accordingly.

At Thu, 4 Aug 2011 17:02:26 -0400,
Eli Barzilay wrote:
> > I'd also like feedback on the document itself. It's not especially
> > detailed, and I'm sure I forgot a lot of useful things.
> 
> * xrepl should be mentioned at the top, since its main goal is to make
>   it easy to live with *any* random editor, even notepad.  The
>   specific highlights to mention is that it gives you an ,enter
>   command to go into a module and an ,edit command that can be used to
>   invoke your $EDITOR on a file (and it defaults to the file you
>   entered into).  Also, there's a ,drracket command that can start
>   drracket, which makes it easy to use  to write code,
>   and drracket to test things.

I didn't want to repeat information that was already in the xrepl
documentation, but you're right that highlighting some of the features
is probably a good idea.

> * Also might good to mention that Neil is in the process of writing
>   something new?

I'm planning to add it once he releases it.

> * Did you verify that paredit treats []s properly?  (At least at some
>   point in the past I think that it didn't.)

I've been using paredit daily for years, and I don't recall having any
issues.

> * `check-requires' is even less important than that...  Including it
>   means including a whole bunch of other things (for example, the
>   macro stepper's textual interface).  If anything, add it as an xrepl
>   command.

Adding it to xrepl is a good idea.

Vincent
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Racket and Text Editors

2011-08-04 Thread Vincent St-Amour
That's a good point.

I think it would be nice to have it be part of the regular
distribution. Eli, is there a way to do that?

And yes, it's available as part of the Racket Full distribution.

Vincent



At Thu, 4 Aug 2011 18:08:58 -0300,
Rodolfo Carvalho wrote:
> 
> [1  ]
> Hello,
> 
> About Bash completion, is seems to me that it is not part of the "normal"
> distribution.
> Maybe available through the "Racket full" nightly installer or the git repo.
> 
> []'s
> 
> Rodolfo Carvalho
> [2  ]
> 
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Racket and Text Editors

2011-08-04 Thread Eli Barzilay
Three minutes ago, Rodolfo Carvalho wrote:
> Hello,
> 
> About Bash completion, is seems to me that it is not part of the
> "normal" distribution.  Maybe available through the "Racket full"
> nightly installer or the git repo.

Through a URL, it's accessible at our git server or github as:

  
http://git.racket-lang.org/plt/blob_plain/HEAD:/collects/meta/contrib/completion/racket-completion.bash
  
https://raw.github.com/plt/racket/master/collects/meta/contrib/completion/racket-completion.bash

-- 
  ((lambda (x) (x x)) (lambda (x) (x x)))  Eli Barzilay:
http://barzilay.org/   Maze is Life!
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Racket and Text Editors

2011-08-04 Thread Rodolfo Carvalho
Hello,

About Bash completion, is seems to me that it is not part of the "normal"
distribution.
Maybe available through the "Racket full" nightly installer or the git repo.

[]'s

Rodolfo Carvalho
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev

Re: [racket-dev] Racket and Text Editors

2011-08-04 Thread Eli Barzilay
30 minutes ago, Vincent St-Amour wrote:
> 
> As I mentioned at RacketCon, I've been working (with help from Asumu
> Takikawa and Jon Rafkind) on a document that provides pointers to
> tools for using Racket with popular text editors.
> 
> I now have a draft of it on my webpage:
> http://www.ccs.neu.edu/home/stamourv/using-racket-with-your-editor-of-choice.html
> 
> I think this would be a nice resource to have somewhere in the
> Racket documentation. Does anyone have an idea where it should go?

In the guide, IMO.


> I'd also like feedback on the document itself. It's not especially
> detailed, and I'm sure I forgot a lot of useful things.

* xrepl should be mentioned at the top, since its main goal is to make
  it easy to live with *any* random editor, even notepad.  The
  specific highlights to mention is that it gives you an ,enter
  command to go into a module and an ,edit command that can be used to
  invoke your $EDITOR on a file (and it defaults to the file you
  entered into).  Also, there's a ,drracket command that can start
  drracket, which makes it easy to use  to write code,
  and drracket to test things.

* Maybe even move all of ยง3 to the top for a similar reason.  (But
  within that, xrepl should be first since its explicit purpose is to
  make it convenient to work with any editor)

* For Emacs, it should mention that `scheme-mode' is *still* good
  enough for most Racket code, although Racket obviously has many more
  forms.  Probably good to mention it last, since it's intended for
  some people who really don't want to try a new package.

* If "Quack and Geiser can be used together" and the reference is in
  the Geiser manual, then it makes more sense for Geiser to be
  mentioned second, and say it there.

* Also might good to mention that Neil is in the process of writing
  something new?

* For the Scribble mode entry, it should advise people that don't want
  to use Neil's thing to either try `texinfo-mode' or just a plain
  text mode.  The thing here is to prevent people from trying some
  random Scheme mode which can look @emph{pretty
  bad}.

* Did you verify that paredit treats []s properly?  (At least at some
  point in the past I think that it didn't.)

* You should use @exec{...} for all of the executable names (like some
  uses of "vi").

* Not to be outdone by vi(m), emacs has everything you want with paren
  highlighting, and more...  http://lemonodor.com/archives/001207.html
  Also, enter "emacs rainbow" and see what google suggest to end it
  with...

* I'm not sure that there's any point in mentioning `raco' -- it's as
  useful with drracket too.

* `check-requires' is even less important than that...  Including it
  means including a whole bunch of other things (for example, the
  macro stepper's textual interface).  If anything, add it as an xrepl
  command.

-- 
  ((lambda (x) (x x)) (lambda (x) (x x)))  Eli Barzilay:
http://barzilay.org/   Maze is Life!

_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev

[racket-dev] Racket and Text Editors

2011-08-04 Thread Vincent St-Amour

As I mentioned at RacketCon, I've been working (with help from Asumu
Takikawa and Jon Rafkind) on a document that provides pointers to
tools for using Racket with popular text editors.

I now have a draft of it on my webpage:
http://www.ccs.neu.edu/home/stamourv/using-racket-with-your-editor-of-choice.html

I think this would be a nice resource to have somewhere in the Racket
documentation. Does anyone have an idea where it should go?

I'd also like feedback on the document itself. It's not especially
detailed, and I'm sure I forgot a lot of useful things.

Vincent
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev