I fork the codebase on my local computer. Then I .configure & make & make
install, as a result, there are many compiled things like bin or *.o files.
To avoid add them to my commit, I modify .gitignore to ignore them all.
But I can't avoid add .gitignore at all, isn't it?
So how do you solve thi
On 12/13/12 9:22 AM, Chen Xiao wrote:
I fork the codebase on my local computer. Then I .configure & make &
make install, as a result, there are many compiled things like bin or
*.o files.
To avoid add them to my commit, I modify .gitignore to ignore them all.
But I can't avoid add .gitignore at
Edit .gitgnore and then use
git update-index --assume-unchanged .gitignore
to tell git to ignore the changes.
Revert with
git update-index --no-assume-unchanged .gitignore
if needed.
Tobias
On Thu, 13 Dec 2012 15:22:29 +0100, Chen Xiao
wrote:
I fork the codebase on my local computer
If you are doing a git status and only wish to see changes applicable to
tracked files:
$ git status -uno -- .
If you are a Linux commandline type of guy, I like doing commit work using
'tig'.
On Thu, Dec 13, 2012 at 9:46 AM, Tobias Hammer wrote:
> Edit .gitgnore and then use
> git update-i
On Wed, Dec 12, 2012 at 4:01 PM, Ryan Culpepper wrote:
> On 12/12/2012 03:58 PM, Jay McCarthy wrote:
>>
>> I agree with Carl.
>>
>> But I would make an even stronger suggestion, I would suggest that you
>> completely drop support for old Racket versions and if necessary
>> release "webapis-lts" an
On Wed, Dec 12, 2012 at 8:55 PM, Asumu Takikawa wrote:
> On 2012-12-12 14:29:32 -0500, Ryan Culpepper wrote:
>> I'm trying to understand how things are supposed to work in planet2
>> without version information.
>
> Maybe this was discussed in the other (quite long) thread about Planet
> 2, but an
On Wed, Dec 12, 2012 at 11:48 PM, David Vanderson
wrote:
> I was professionally writing Ruby code as that community struggled through
> package issues. I hope that experience can shed some light here. Also I'd
> like to understand the basic use cases and how they work in planet2.
>
> As a user,
At Thu, 13 Dec 2012 08:17:32 -0700, Jay McCarthy wrote:
> As an aside in response to this whole thread, [...]
I recommend that further complaints and suggestions take the form of a
patch.
Creating a patch is more difficult, more time consuming, and you have
to understand even more details of Plan
On Thu, Dec 13, 2012 at 10:08 AM, Jay McCarthy wrote:
>
>> Finally, as a meta-point, is there any evidence that just throwing away
>> versions will work? Any precedents? So far, this seems like a classic case
>> of throwing the baby out with the bathwater: versions sometimes cause
>> problems... s
On Dec 13, 2012 9:22 AM, "Chen Xiao" wrote:
>
> I fork the codebase on my local computer. Then I .configure & make & make
install, as a result, there are many compiled things like bin or *.o files.
>
> To avoid add them to my commit, I modify .gitignore to ignore them all.
Add your local ignores
On 2012-12-13 08:17:32 -0700, Jay McCarthy wrote:
> Why aren't you just only using the development version?
This mainly comes up if I want to test the uploaded version to make sure
it works. I can probably figure out a better workflow though (such as
keeping around a release version of Racket to t
I just got tripped up, again, trying to traverse a list with `first' and
`rest' in a `racket/base' file. `first' and `rest' are only available in
`racket' and `racket/list', but not in `racket/base'.
If we want to encourage use of `first' and `rest' over `car' and `cdr'
and of `racket/base' when p
On Dec 13, 2012, at 6:37 AM, David Van Horn wrote:
> On 12/13/12 9:22 AM, Chen Xiao wrote:
>> I fork the codebase on my local computer. Then I .configure & make &
>> make install, as a result, there are many compiled things like bin or
>> *.o files.
>>
>> To avoid add them to my commit, I modify
On 2012-12-13 12:44:38 -0500, Vincent St-Amour wrote:
> Does this sound reasonable?
+1. While we're at it, might as well also put at least `empty` and
`empty?` in there too. These trip me up as well.
Cheers,
Asumu
_
Racket Developers list:
http://lists.racket-lang.org/
Throw cons? in with empty?, please.
Carl Eastlund
On Thu, Dec 13, 2012 at 2:13 PM, Asumu Takikawa wrote:
> On 2012-12-13 12:44:38 -0500, Vincent St-Amour wrote:
> > Does this sound reasonable?
>
> +1. While we're at it, might as well also put at least `empty` and
> `empty?` in there too. Thes
-1, since they are different from what some people would expect them
to do. -2 for the `empty', `cons?' etc aliases.
An hour and a half ago, Vincent St-Amour wrote:
> I just got tripped up, again, trying to traverse a list with `first'
> and `rest' in a `racket/base' file. `first' and `rest' are
On 12/13/2012 07:19 AM, Jay McCarthy wrote:
This is on my future plans to make a "raco pkg bundle" that will
produce a big tar ball that and can be installed on another machine
and get the same packages (even if they are no longer available at
their sources with those versions) installed. I just
If they do the wrong thing, we should fix them, not deprecate them. We're
not LISP, let's not promote car/cdr as the primary names for list
operations.
Carl Eastlund
On Thu, Dec 13, 2012 at 2:19 PM, Eli Barzilay wrote:
> -1, since they are different from what some people would expect them
>
I agree with Eli. first is not car and shouldn't be treated as it.
car : (Cons a b) -> a
first : (List a) -> a
I also agree with Carl that we should deprecate grandpa's names and
give nice names. I suggest "fst" and "snd" and "pair"
Jay
On Thu, Dec 13, 2012 at 12:26 PM, Carl Eastlund wrote:
>
Vincent's proposal wasn't "let's treat car as first", his proposal was
"let's export it in racket/base". If we don't like first/rest, we should
have a proposal to remove them from #lang racket... right? Otherwise,
let's put them in racket/base. They're very simple names for very, very
common ope
20 minutes ago, Carl Eastlund wrote:
> If they do the wrong thing, we should fix them, not deprecate them.
I'm not saying that they should be deprecated.
> We're not LISP, let's not promote car/cdr as the primary names for
> list operations.
And I'm not suggesting that either. (In fact, in *C*L
> I suggest that you pick a new name for the language that you'd like to
> have, and fix the docs to talk about that one. Then, we can leave
> `scribble/doclang' alone, documenting it as only for backward
> compatibility.
Ok, done. I've pushed up a scribble/doclang2 and documentation that
describ
> Ok, done. I've pushed up a scribble/doclang2 and documentation that
> describes how to use both scribble/doclang2 and scribble/doclang.
Ugh; I feel bad that I forgot to write proper test cases. Where are
the existing test cases for doclang? I'll add some for doclang2, but
I don't know where t
At Thu, 13 Dec 2012 14:51:42 -0500,
Eli Barzilay wrote:
> A few minutes ago, Jay McCarthy wrote:
> > I agree with Eli. first is not car and shouldn't be treated as it.
> >
> > car : (Cons a b) -> a
> > first : (List a) -> a
>
> Right -- it's a different type, and the `list?' check adds a cost.
>
>> I suggest building in a build/ directory as described in src/README. There's
>> already a .gitignore directive to ignore that directory.
I had a similar confusion a week ago, building Racket for the first
time ever, and got an answer on #racket.
I was following Joe Gibbs Politz's recent Racke
On 2012-12-13 15:34:04 -0500, Greg Hendershott wrote:
> I had a similar confusion a week ago, building Racket for the first
> time ever, and got an answer on #racket.
One thing that makes this easier is if you use the `plt-fresh-build`
script from this git repo:
https://github.com/takikawa/racke
> Unfortunately I don't have his email, so I hope he'll read this or
> perhaps someone here can forward this to him.
Got it, I'll add to the post this evening.
_
Racket Developers list:
http://lists.racket-lang.org/dev
I was following your blog too, haha.
2012/12/14 Joe Gibbs Politz
> > Unfortunately I don't have his email, so I hope he'll read this or
> > perhaps someone here can forward this to him.
>
> Got it, I'll add to the post this evening.
> _
> Racket Developers list:
> htt
> I was following your blog too, haha.
Glad to hear it was useful! I've updated the post on the blog.
_
Racket Developers list:
http://lists.racket-lang.org/dev
> Glad to hear it was useful! I've updated the post on the blog.
It was really helpful. Thank you for updating it.
_
Racket Developers list:
http://lists.racket-lang.org/dev
I figured this out. It was that vim was not being compiled with the precise
garbage collection when racket was, and a couple of bugs on the vim
allocation of racket objects. I'll hopefully have a patch soon.
On Mon, Dec 10, 2012 at 10:32 PM, Eric Dobson wrote:
> +correct vim group.
>
>
>
> On Mo
If you place provide/contract at the beginning of a module it makes
the interface clear but it is separated from its function. If you
place it right before its function and not at the top of the module,
it makes the function clearer but the module interface is not so
clear.
Is it possible (would
I have a program which is thread 'heavy' and runs much slower in embedded
racket (vim) than it does in pure racket.
The program: (note no #lang, as I'm doing this in the repl)
(require racket/async-channel)
(define (make-passer in)
(define chan (make-async-channel))
(thread (lambda ()
(a
33 matches
Mail list logo
