added -trace to TestRig. fixed code gen issue for trace listener

[parrt]

trying my first pull from parrt/antlr4 to antlr/antlr4. Should go from dev to dev.

[anatol]

Well, you don't have to create a pull request for every your change. You already a project developer and have "push" permission. Pull requests are for contributors.

[parrt]

yeah, just testing / using as you suggested. ;) how do i get a freakin dev branch in antlr/antlr4 btw?
Ter
On Jan 30, 2012, at 5:01 PM, Anatol wrote:

Well, you don't have to create a pull request for every your change. You already a project developer and have "push" permission. Pull requests are for contributors.

---

Reply to this email directly or view it on GitHub:
#2 (comment)

[anatol]

Hi

On Mon, Jan 30, 2012 at 5:10 PM, Terence Parr <
reply@reply.github.com

wrote:

yeah, just testing / using as you suggested. ;) how do i get a freakin dev
branch in antlr/antlr4 btw?

cd your_project
git checkout -b foobar

// hack your project
...

// commit your changes
git commit -am "This is a foo change"

// Double-check your commit
git show

// create a new remote branch and set upstream for local one
// set upstream means that next "git pull" it will pull from just-created
branch
git push -u origin HEAD:refs/heads/new_branch

Ter
On Jan 30, 2012, at 5:01 PM, Anatol wrote:

Well, you don't have to create a pull request for every your change. You
already a project developer and have "push" permission. Pull requests are
for contributors.

---

Reply to this email directly or view it on GitHub:
#2 (comment)

---

Reply to this email directly or view it on GitHub:
#2 (comment)

[parrt]

hmm…well, i got one easily by checking out antlr/antlr4 quickly.

Now i'm learning about remote vs upstream and my forked stuff. fetch vs pull. ugh.
ter
On Jan 30, 2012, at 5:14 PM, Anatol wrote:

Hi

On Mon, Jan 30, 2012 at 5:10 PM, Terence Parr <
reply@reply.github.com

wrote:

yeah, just testing / using as you suggested. ;) how do i get a freakin dev
branch in antlr/antlr4 btw?

cd your_project
git checkout -b foobar

// hack your project
...

// commit your changes
git commit -am "This is a foo change"

// Double-check your commit
git show

// create a new remote branch and set upstream for local one
// set upstream means that next "git pull" it will pull from just-created
branch
git push -u origin HEAD:refs/heads/new_branch

Ter
On Jan 30, 2012, at 5:01 PM, Anatol wrote:

Well, you don't have to create a pull request for every your change. You
already a project developer and have "push" permission. Pull requests are
for contributors.

---

Reply to this email directly or view it on GitHub:
#2 (comment)

---

Reply to this email directly or view it on GitHub:
#2 (comment)

---

Reply to this email directly or view it on GitHub:
#2 (comment)

[parrt]

Wow. got it all figured out ;) Well, I was quite confused because I was in the wrong directory in one moment, but I think I'm working things out. Did you see my mail about antlr3-main vs main from p4? I want to make sure we have the right directory before we move on and turnoff p4.
Ter