Hi,
thanks for your prompt reply; I agree that there is also this ambiguity. This
would go away if we were to use `type` but as I said we don't dare to do that.
That's the problem with short names - they're always ambiguous at least to some
extent.
The only alleviation I can offer for the valid concern you are raising is that
the user will notice upon the very first use that Enter is not pressed after
the text has been typed in, and then (if necessary) add a `press(ENTER)`
afterwards.
It's a pity that `type` is taken... It's very tempting to just use it. But then
again you might have people trying to `type(ALT + TAB)`, which in our current
proposal can only be input using `press`...
What do the others think about this?
Cheers
On Thursday, November 22, 2012 8:08:39 PM UTC+1, Chris Angelico wrote:
> On Fri, Nov 23, 2012 at 5:00 AM, Michael Herrmann
>
> <...> wrote:
>
> > In our gut feeling, the words apart from `type` that would most normally be
> > used in an everyday conversation to express the three examples I have given
> > in my first mail are:
>
> > press(CTRL + 'a')
>
> > enter("Hello World")
>
> > press(ENTER)
>
>
>
> Looks fairly good, except for one possible problem: The verb "enter"
>
> often means "type this, and then press the Enter key". (For instance,
>
> "open up a terminal/shell and enter this command".) Is that likely to
>
> be a point of confusion?
>
>
>
> It's plenty plausible either way. I like the multiple-keystrokes version:
>
> > press(ALT + 'f', 's')
>
> and the split API does make good sense.
>
>
>
> ChrisA
--
http://mail.python.org/mailman/listinfo/python-list
