Comments for Syntactic Sugar http://friggeri.net Adrien Friggeri's blog Sun, 06 Jul 2008 21:01:25 +0000 http://wordpress.org/?v=2.6-bleeding2 Comment on Vimpress ! by mobiphil » Blog Archive » press that word with vim … or posting wordpress blog with vim http://friggeri.net/blog/2007/07/13/vimpress#comment-492 mobiphil » Blog Archive » press that word with vim … or posting wordpress blog with vim Sun, 08 Jun 2008 13:14:36 +0000 http://www.friggeri.net/blog/2007/07/13/vimpress/#comment-492 [...] another vimpress [...] [...] another vimpress [...]

]]> Comment on Vimpress ! by Manuel http://friggeri.net/blog/2007/07/13/vimpress#comment-485 Manuel Thu, 05 Jun 2008 23:33:41 +0000 http://www.friggeri.net/blog/2007/07/13/vimpress/#comment-485 It's wonderful! I've started a wordpress blog yesterday and after editing just two post I understood I wouldn't be able to live with the online wordpress editor. Thank you so much for this vim plugin! I only have one problem: when I try getting one post with :BlogOpen, I get only the part before the <!--more--> sign. Have you any idea how I can avoid this problem? I would search it myself but unfortunately I don't speak python nor php... Currently I just refrain from using the <!--more--> sign. Thanks again! It's wonderful! I've started a wordpress blog yesterday and after editing just two post I understood I wouldn't be able to live with the online wordpress editor. Thank you so much for this vim plugin!

I only have one problem: when I try getting one post with :BlogOpen, I get only the part before the sign. Have you any idea how I can avoid this problem? I would search it myself but unfortunately I don't speak python nor php… Currently I just refrain from using the sign.

Thanks again!

]]> Comment on Vimpress ! by .log : Гворит Москва http://friggeri.net/blog/2007/07/13/vimpress#comment-476 .log : Гворит Москва Sun, 01 Jun 2008 17:01:51 +0000 http://www.friggeri.net/blog/2007/07/13/vimpress/#comment-476 [...] vimpress & PHP Markdown. [...] [...] vimpress & PHP Markdown. [...]

]]> Comment on Vimpress ! by .log : Говорит Москва http://friggeri.net/blog/2007/07/13/vimpress#comment-475 .log : Говорит Москва Sun, 01 Jun 2008 16:54:19 +0000 http://www.friggeri.net/blog/2007/07/13/vimpress/#comment-475 [...] vimpress & PHP Markdown: 1. italic 2. bold 3. [...] [...] vimpress & PHP Markdown: 1. italic 2. bold 3. [...]

]]> Comment on Google treasure hunt by kevin http://friggeri.net/blog/2008/05/18/google-treasure-hunt#comment-471 kevin Fri, 30 May 2008 10:27:22 +0000 http://friggeri.net/?p=130#comment-471 Well put. If you fill in the no of paths value from each square to the finish you can easily observe it as a piece cut from the pascal's triangle ... I solved it by observing the pascal's triangle :) Well put.
If you fill in the no of paths value from each square to the finish you can easily observe it as a piece cut from the pascal's triangle …
I solved it by observing the pascal's triangle :)

]]> Comment on Vimpress ! by sefr0m http://friggeri.net/blog/2007/07/13/vimpress#comment-434 sefr0m Sat, 17 May 2008 19:56:05 +0000 http://www.friggeri.net/blog/2007/07/13/vimpress/#comment-434 when i try to post to my blog i get this error msgs Traceback (most recent call last): File "", line 1, in File "", line 77, in blog_send_post File "/usr/lib/python2.5/xmlrpclib.py", line 1147, in __call__ return self.__send(self.__name, args) File "/usr/lib/python2.5/xmlrpclib.py", line 1437, in __request verbose=self.__verbose File "/usr/lib/python2.5/xmlrpclib.py", line 1201, in request return self._parse_response(h.getfile(), sock) File "/usr/lib/python2.5/xmlrpclib.py", line 1335, in _parse_response p.feed(response) File "/usr/lib/python2.5/xmlrpclib.py", line 547, in feed self._parser.Parse(data, 0) xml.parsers.expat.ExpatError: junk after document element: line 2, column 0 when i try to post to my blog i get this error msgs

Traceback (most recent call last):
File "", line 1, in
File "", line 77, in blog_send_post
File "/usr/lib/python2.5/xmlrpclib.py", line 1147, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.5/xmlrpclib.py", line 1437, in __request
verbose=self.__verbose
File "/usr/lib/python2.5/xmlrpclib.py", line 1201, in request
return self._parse_response(h.getfile(), sock)
File "/usr/lib/python2.5/xmlrpclib.py", line 1335, in _parse_response
p.feed(response)
File "/usr/lib/python2.5/xmlrpclib.py", line 547, in feed
self._parser.Parse(data, 0)
xml.parsers.expat.ExpatError: junk after document element: line 2, column 0

]]> Comment on Vimpress ! by HaHaGood http://friggeri.net/blog/2007/07/13/vimpress#comment-432 HaHaGood Fri, 16 May 2008 11:59:44 +0000 http://www.friggeri.net/blog/2007/07/13/vimpress/#comment-432 It is seems that vimpress can't work in windows. I can use it in Ubuntu perfectly. But in windows, I failed. It is seems that vimpress can't work in windows. I can use it in Ubuntu perfectly. But in windows, I failed.

]]> Comment on Namespacing JavaScript by Peter Michaux http://friggeri.net/blog/2008/05/12/namespacing-javascript#comment-424 Peter Michaux Mon, 12 May 2008 19:36:06 +0000 http://friggeri.net/?p=129#comment-424 So you are after a simpler way to define a serious of nested namespace objects. Something that will make intermediate objects as needed. Like YAHOO.namespace http://developer.yahoo.com/yui/yahoo/#namespace or even similar to UNIX's mkdir -p. That is a fine idea to save the labor of checking if each level of namespacing is already defined and then defining the level if it is not. You could easily make an xjs module with your code. I would caution strongly against the use of JavaScript's "with" as it causes virtual chaos. The main problem is how many levels of namespacing are required vs the performance hit? Using more than one level of object namespacing seems like an unecessary performance hit when underscores do the same job with respect to namespacing as periods do. They are just characters after all. Using pure underscore namespacing is sufficient also and in my very casual tests with Rhino it didn't seem to be a problem to have many global objects. In fact, if that is something you would like to investigate in detail I would be very interested in reading your results for accessing namespaced objects using different namespacing schemes. So you are after a simpler way to define a serious of nested namespace objects. Something that will make intermediate objects as needed. Like YAHOO.namespace

http://developer.yahoo.com/yui/yahoo/#namespace

or even similar to UNIX's mkdir -p.

That is a fine idea to save the labor of checking if each level of namespacing is already defined and then defining the level if it is not. You could easily make an xjs module with your code. I would caution strongly against the use of JavaScript's "with" as it causes virtual chaos.

The main problem is how many levels of namespacing are required vs the performance hit? Using more than one level of object namespacing seems like an unecessary performance hit when underscores do the same job with respect to namespacing as periods do. They are just characters after all. Using pure underscore namespacing is sufficient also and in my very casual tests with Rhino it didn't seem to be a problem to have many global objects. In fact, if that is something you would like to investigate in detail I would be very interested in reading your results for accessing namespaced objects using different namespacing schemes.

]]> Comment on Namespacing JavaScript by Adrien Friggeri http://friggeri.net/blog/2008/05/12/namespacing-javascript#comment-423 Adrien Friggeri Mon, 12 May 2008 19:25:40 +0000 http://friggeri.net/?p=129#comment-423 I think you misunderstood what I was saying. I totally agree that these simples techniques solve every imaginable problem. What I'm suggesting here is, instead of going through the trouble of defining your object net.friggeri.foo, and then manually defining net.friggeri.foo.someFunction, net.friggeri.foo.someOtherFunction, you can use a more concise way of writing it. Same thing for fetch, it just gives the ability to "open" a package, avoiding the necessity to type the whole package name everytime. I'm not trying to reinvent the wheel here ;) I think you misunderstood what I was saying. I totally agree that these simples techniques solve every imaginable problem. What I'm suggesting here is, instead of going through the trouble of defining your object net.friggeri.foo, and then manually defining net.friggeri.foo.someFunction, net.friggeri.foo.someOtherFunction, you can use a more concise way of writing it.

Same thing for fetch, it just gives the ability to "open" a package, avoiding the necessity to type the whole package name everytime.

I'm not trying to reinvent the wheel here ;)

]]> Comment on Namespacing JavaScript by Peter Michaux http://friggeri.net/blog/2008/05/12/namespacing-javascript#comment-422 Peter Michaux Mon, 12 May 2008 19:09:47 +0000 http://friggeri.net/?p=129#comment-422 I don't think a packaging system beyond what JavaScript provides naturally is necessary. Avoiding global namespace collisions is easy and fast by either using the macromedia style (e.g. MM_someFunction) or using a object (e.g. MM.someFunction). If you want more elaborate namespacing you could use net_friggeri_someFunction or net_friggeri.someFunction or if even slower performance is desired net.friggeri.someFunction. These all "solve" the problem simply and are all reasonably efficient. Which problems do these simple techniques not solve? I don't think a packaging system beyond what JavaScript provides naturally is necessary. Avoiding global namespace collisions is easy and fast by either using the macromedia style (e.g. MM_someFunction) or using a object (e.g. MM.someFunction). If you want more elaborate namespacing you could use net_friggeri_someFunction or net_friggeri.someFunction or if even slower performance is desired net.friggeri.someFunction. These all "solve" the problem simply and are all reasonably efficient. Which problems do these simple techniques not solve?

]]>