From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.help Subject: Re: completing-read does not accept spaces Date: Thu, 23 Jan 2014 15:20:09 +0100 Message-ID: <871tzyg4py.fsf@wanadoo.es> References: <52d7f748$0$29470$862e30e2@ngroups.net> <8761pj3lek.fsf@wanadoo.es> <52E10B26.5060300@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1390486846 17804 80.91.229.3 (23 Jan 2014 14:20:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 23 Jan 2014 14:20:46 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Miguel Guedes Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jan 23 15:20:53 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W6L9I-0007wr-Nc for geh-help-gnu-emacs@m.gmane.org; Thu, 23 Jan 2014 15:20:52 +0100 Original-Received: from localhost ([::1]:41430 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6L9I-0005YD-9G for geh-help-gnu-emacs@m.gmane.org; Thu, 23 Jan 2014 09:20:52 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6L8o-0005Qm-4o for help-gnu-emacs@gnu.org; Thu, 23 Jan 2014 09:20:29 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W6L8g-0002CP-P1 for help-gnu-emacs@gnu.org; Thu, 23 Jan 2014 09:20:22 -0500 Original-Received: from smtp10.acens.net ([86.109.99.134]:33612 helo=smtp.movistar.es) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6L8g-0002C3-FK for help-gnu-emacs@gnu.org; Thu, 23 Jan 2014 09:20:14 -0500 X-CTCH-RefID: str=0001.0A0B020D.52E1251B.00B3, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-Spam: Unknown Original-Received: from qcore (83.41.62.231) by smtp.movistar.es (8.6.117.05) (authenticated as 981711563$telefonica.net) id 52DC28FB003CE698; Thu, 23 Jan 2014 14:20:11 +0000 In-Reply-To: <52E10B26.5060300@gmail.com> (Miguel Guedes's message of "Thu, 23 Jan 2014 12:29:26 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 86.109.99.134 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:95572 Archived-At: Miguel Guedes writes: > But would it be fair to say that the command `timeclock-out' shouldn't > be making use of `completing-read' for entering a reason (to clock > out) and thus a bug should be filed? I'm not sure about the intent of the timeclock author about that. The same as `project', `reason' could be expected to be a keyword ("finished", "pause", "lunch".) You can use non-blank separators to cheat ("walk-dog"). Anyways, if the author's plans was to allow full strings, there is a bug related to completing-read usage; if not, the documentation of timeclock should be expanded to explain how `reason' should look like. So I'll go ahead and file a bug (M-x report-emacs-bug)