emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] [babel] Bugs for Emacs Lisp code blocks


From: Eric Schulte
Subject: Re: [O] [babel] Bugs for Emacs Lisp code blocks
Date: Mon, 15 Apr 2013 09:26:46 -0600
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

"Sebastien Vauban" <address@hidden> writes:

> 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?
>

We have to consider named blocks or data as well as strings and Emacs
Lisp.

>
> Best regards,
>   Seb

-- 
Eric Schulte
http://cs.unm.edu/~eschulte



reply via email to

[Prev in Thread] Current Thread [Next in Thread]