Message188532
| Author |
pitrou |
| Recipients |
belopolsky, cben, eric.araujo, ezio.melotti, flox, giampaolo.rodola, lesmana, loewis, mark.dickinson, ned.deily, pitrou, python-dev, r.david.murray, ronaldoussoren, serhiy.storchaka, steven.daprano, tshepang |
| Date |
2013年05月06日.13:24:02 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1610220362.19668887.1367846636497.JavaMail.root@zimbra10-e2.priv.proxad.net> |
| In-reply-to |
<1367844413.46.0.88202212782.issue5845@psf.upfronthosting.co.za> |
| Content |
> Now I don't know if I'm missing something painfully obvious, but
> having to bang out space-space-space-space for every indent is
> surely not going to be a win for usability ;-) Even if I am missing
> something, surely so will a lot of other users.
What *looks* painfully obvious to me is that Python doesn't force you
to use 4 spaces (or tabs) for indents :-)
> I use a readline completer that (in my opinion) does the Right Thing:
> at the start of the line, hitting TAB inserts a tab, otherwise it
> does completion. It also sets a history file, adds a couple of key
> bindings that I sometimes find useful, and wraps it all up in a
> class.
The "indent at beginning of line" thing sounds useful. The rest seems
to conflate the concept of a completer with the readline module itself.
Even though it's called rlcompleter, the rlcompleter module is
actually generic and could be used with other input schemes, so I don't
think it's the right place to set history options or key bindings.
In any case, you should post your patch as part of a separate issue, IMO. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年05月06日 13:24:02 | pitrou | set | recipients:
+ pitrou, loewis, ronaldoussoren, mark.dickinson, cben, belopolsky, giampaolo.rodola, ned.deily, ezio.melotti, eric.araujo, steven.daprano, r.david.murray, flox, lesmana, tshepang, python-dev, serhiy.storchaka |
| 2013年05月06日 13:24:02 | pitrou | link | issue5845 messages |
| 2013年05月06日 13:24:02 | pitrou | create |
|