all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miguel Guedes <miguel.a.guedes@gmail.com>
To: "Drew Adams" <drew.adams@oracle.com>, "Óscar Fuentes" <ofv@wanadoo.es>
Cc: help-gnu-emacs@gnu.org
Subject: Re: completing-read does not accept spaces
Date: Thu, 23 Jan 2014 12:29:26 +0000	[thread overview]
Message-ID: <52E10B26.5060300@gmail.com> (raw)
In-Reply-To: <a6cf7fbc-dfb6-4824-b623-1bd582d40701@default>

On 16/01/14 18:13, Drew Adams wrote:
<snip>
> No.  There is no bug here.  This is the behavior by design, like
> it or not.
>
> Do I personally think that `SPC' should generally be self-inserting
> during completion?  You bet I do.  And so should `?'.  And so should
> `C-j' (newline).  (And this is the case in Icicle mode, for instance.)
>
> But that is not the opinion of Emacs Dev.  It took decades to finally
> get `SPC' to be self-inserting for file-name completion (see variable
> `minibuffer-local-filename-completion-map', in the same Elisp manual
> node).  Patience. ;-)
>

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?

Many thanks for your replies.



  parent reply	other threads:[~2014-01-23 12:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 15:14 Command timeclock-out Miguel Guedes
2014-01-16 17:07 ` completing-read does not accept spaces (was: Command timeclock-out) Óscar Fuentes
2014-01-16 18:13   ` Drew Adams
2014-01-16 18:36     ` completing-read does not accept spaces Óscar Fuentes
2014-01-16 18:50       ` Drew Adams
2014-01-16 19:01     ` Stefan Monnier
2014-01-23 12:29     ` Miguel Guedes [this message]
2014-01-23 14:20       ` Óscar Fuentes
2014-01-23 17:20       ` Drew Adams

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

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

  git send-email \
    --in-reply-to=52E10B26.5060300@gmail.com \
    --to=miguel.a.guedes@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=ofv@wanadoo.es \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.