From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: [babel] Bugs for Emacs Lisp code blocks Date: Mon, 15 Apr 2013 16:09:36 +0200 Message-ID: <86vc7nevhb.fsf@somewhere.org> References: <868v4v1x6k.fsf@somewhere.org> <871uamo4e9.fsf@gmail.com> <86d2u6z6kg.fsf@somewhere.org> <87d2u65dr1.fsf@gmail.com> <86wqsbcws2.fsf@somewhere.org> <86mwt6ddm5.fsf@somewhere.org> <87ehefe5kn.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Eric, Eric Schulte wrote: >>> What is still unclear to me as well, is why =()= and =nil= aren't the same >>> from Babel's point of view? >> >> However, I think I understood this one: it is because nil is interpreted as a >> string, not as the empty list; right? >> >> That's because strings aren't quoted, right? > > Yes. Apart from the automatic (and, maybe, sometimes unwished) coercion of a symbol into a string (case of `nil'), are you aware of other tricky stuff? For my own understanding, why didn't we force the user to quote all strings, and avoid the above problem? Best regards, Seb -- Sebastien Vauban