emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Sebastien Vauban <sva-news@mygooglest.com>, emacs-orgmode@gnu.org
Subject: Re: [Babel] :colnames "no" no longer default for Emacs Lisp [Was] Lisp error: (wrong-type-argument listp hline)
Date: Tue, 01 Oct 2013 12:04:39 -1000	[thread overview]
Message-ID: <m11u44myvc.fsf@poto.myhome.westell.com> (raw)
In-Reply-To: <87d2ntw22n.fsf@gmail.com> (Eric Schulte's message of "Sat, 28 Sep 2013 06:21:04 -0600")

Hi Eric,

I think this breaks Marc-Oliver Ihm's lob-table-operations.org.

I use these a lot with #+call: lines.

Any tips on how to get the old behavior back? I tried :colnames no with
one of Marc-Oliver's code blocks, (and kept :colnames yes with my
#+call: line) but this didn't seem to change anything. Instead of the
column names from the original tables, which I used to get, I now get
names like "t1c2".

All the best,
Tom

Eric Schulte <schulte.eric@gmail.com> writes:

>>
>> I always wondered why emacs-lisp is the _only_ language with ":colnames no" as
>> its default. Is there a reason therefore?  If no really good reason, could we
>> suppress that?
>>
>
> This seemed to make sense early on because Emacs Lisp could easily
> process hlines itself, but at this point it adds more confusion than it
> is worth.  I've reverted this default for elisp, hopefully it doesn't
> break too many peoples existing Org-mode files.
>
> Best,

-- 
Thomas S. Dye
http://www.tsdye.com

  parent reply	other threads:[~2013-10-01 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23 14:16 [Babel] Lisp error: (wrong-type-argument listp hline) Sebastien Vauban
2013-09-23 23:26 ` Eric Schulte
2013-09-24  8:43   ` Sebastien Vauban
2013-09-28 12:21     ` [Babel] :colnames "no" no longer default for Emacs Lisp [Was] " Eric Schulte
2013-09-30  9:03       ` Sebastien Vauban
2013-10-01 22:04       ` Thomas S. Dye [this message]
2013-10-02 13:13         ` Eric Schulte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m11u44myvc.fsf@poto.myhome.westell.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    --cc=sva-news@mygooglest.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).