From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: =?UTF-8?B?UmU6IG9yZ3RibC1pbnNlcnQtcmFkaW8tdGFibGXCoGZvcmJpZCBi?= =?UTF-8?B?bGFua3MgaW4gdGhlIHRhYmxlIG5hbWU=?= Date: Thu, 11 Oct 2012 14:35:55 +0200 Message-ID: <87fw5l4250.fsf@gmail.com> References: <5073CC9D.8030100@gmx.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:53487) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TMI3d-0001Kh-GS for emacs-orgmode@gnu.org; Thu, 11 Oct 2012 08:40:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TMI3R-0007Co-V7 for emacs-orgmode@gnu.org; Thu, 11 Oct 2012 08:40:07 -0400 Received: from mail-wi0-f171.google.com ([209.85.212.171]:47514) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TMI3R-0007Cd-OI for emacs-orgmode@gnu.org; Thu, 11 Oct 2012 08:39:57 -0400 Received: by mail-wi0-f171.google.com with SMTP id hj13so6984535wib.12 for ; Thu, 11 Oct 2012 05:39:56 -0700 (PDT) In-Reply-To: <5073CC9D.8030100@gmx.net> (Pascal Wittmann's message of "Tue, 09 Oct 2012 09:05:01 +0200") 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@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Pascal Wittmann Cc: emacs-orgmode@gnu.org Hello, Pascal Wittmann writes: > I noticed that its possible to enter a name containing blanks when > calling orgtbl-insert-radio-table. I don't think that this is intended, > because blanks are used as separators in the "#+ORGTBL" line. > > Entering a the name "first table" will result in the following error > message: > > "No such transformation function table" > > For me (as a novice) it was at first not obvious what I did wrong. My > suggestion is to chose an other input method that forbids blanks. Documentation uses table_name in order to describe the name of the table, implying there shouldn't be any space in that name. Maybe it could be made more explicit, with, i.e. a footnote somewhere. > I fixed this locally with the attached patch, but I'm sure there are > better solutions (I find it unintuitive that blanks terminate the > input). Another possibility is to return an error if the string read contains any whitespace character. Regards, -- Nicolas Goaziou