Comments for blog.jacius.info

Comment on Git Submodules Cheat Sheet by hit9

hit9 — Sat, 06 Apr 2013 07:43:53 +0000

such a beautiful blog! I am wondering if I can use `git add` some files under submodule to parent repo

Comment on Git Submodules Cheat Sheet by Mohsin Hijazee

Mohsin Hijazee — Fri, 05 Apr 2013 17:34:43 +0000

And if you want to update all the submodules of a project:

$ git submodule foreach git pull origin master

Comment on A Rubyist’s Impressions of Common Lisp by Alpheus

Alpheus — Fri, 05 Apr 2013 06:20:10 +0000

I’d have to agree that I’ve found the Ruby culture to be somewhat off-putting myself. In my exposures to the Ruby culture, I have the impression that their conferences tend to be mysogenic (and in ways that are particularly offensive to a religious person like myself), and Ruby blogposts tend to be filled with vulgarity. And while I wanted to get through “Why’s Poignant Guide to Ruby” (I like weird, off the wall things), the guide was a bit *too* weird for me (although I still have great admiration for it).

Having said that, this culture hasn’t been the primary reason why I haven’t gotten into Ruby. I’m pretty good at ignoring culture when I have to. I think the biggest reason I haven’t gotten into Ruby is because I’ve spent so many years in Python, and I don’t see what I could learn from Ruby, that’s going to be all that different from Python…and I have also concluded that I would learn everything that Ruby can offer me, but Python can’t, by learning Common Lisp.

I would also add that the Python community has had a bit of a reputation for being “cold”, particularly compared to the Perl community…so it probably can’t be held up as the best standard, either…

Comment on A Rubyist’s Impressions of Common Lisp by Alpheus

Alpheus — Fri, 05 Apr 2013 06:02:48 +0000

I’ve been working on SIP parsing lately, and so I’ve had a lot of exposure to character names of many types. In the process, I reviewed the Intercal names of characters that I had originally been exposed to many years ago. The funny thing is, many or most of those names are rather…inspiring.

Under Incercal, “!” is called “wow”, and “?” is called “what” (although I also like A.H.’s “eh”). For some reason unbeknownst to me, I’ve taken a dislike to calling “!” a “bang”, and “exclamation” is a bit long…I might just adopt “wow”.

I would have to admit that I don’t like all of Intercal’s names, though, but they are nonetheless thought-provoking. I particularly like “wax” for “(” and “wane” for “)”; this inspired me to refer to “” as “rex” (for their roles in XML)…and I’m still in the thought-process of renaming other characters.

Of course, this is somewhat academic, because in Java (which is what my work uses), you have to be Formal with your names, and when I tinker with this at home in Common Lisp, I have found that all the names have already been taken care of with the syntax.

Comment on A Personal Lisp Crisis by Ahmed Fasih

Ahmed Fasih — Thu, 31 Jan 2013 15:21:49 +0000

You mentioned Clojure, Racket, Chicken, et al., any thoughts on Guile (Scheme) or Lua, both designed from the ground up to embed into C?

Comment on Git tip: Fix a mistake in a previous commit by Tom

Tom — Wed, 23 Jan 2013 17:22:23 +0000

This saved my evening !

I didn’t knew that you could rebase a branch on itself.

Thanks

Comment on Your Git Submodule and You by ach

ach — Thu, 10 Jan 2013 09:32:21 +0000

Hi
Cloning is not working properly for sub modules.
I have a Main repo and added two repos as sub modules.Inside that sub modules also i have some repos.

for Eg: Repo main ->sub module repo A(A having two repos as sub modules B and C).

While cloning (git clone –recursive git @IP…:Repo main)

I am able to see sub module repo A.but it is not listing the sub module repos inside A(B and C)

But i am able to clone submodule repo B and C seperately.

Comment on Git Submodules Cheat Sheet by dave

dave — Wed, 12 Dec 2012 23:31:38 +0000

In the first recipe, shouldn’t the last line be:

[main]$ git commit .gitmodules -m "Added submodule as ./subm"

Comment on Git tip: Fix a mistake in a previous commit by Andreas

Andreas — Fri, 09 Nov 2012 17:34:43 +0000

Thanks for the blog, just used that process.

For those who forgot to add a file to the index before committing and stumbled upon it a while later:
After step 6, you can apply the stash, add the missed file to the index and commit as in step 7. After that you ‘git stash’ again.

If you stash again _before_ step 7 the file will not be committed, it will be staged.

Comment on A Personal Lisp Crisis by Faré

Faré — Wed, 31 Oct 2012 12:22:04 +0000

I can’t blame you for leaving the CL community. I myself am attached by my job and by mental inertia, as well as by the relative performance of SBCL.

However, there are many people who are making the CL community better. Xach is one of them, with quicklisp. As for cleaning up the language, I believe it is better to provide and document new APIs such as LIL and make them 100% solutions than to vainly try to organize existing APIs.

Chicken is a nice choice, but I believe you are short-selling Racket by rejecting it on license grounds. Many people do proprietary software on top of Racket. Please pick a better reason to reject Racket (or not).