[IPython-dev] Min: Cmd-P/Ctrl-P for new print code question..
Tue Oct 26 16:29:57 CDT 2010
On Tue, Oct 26, 2010 at 14:24, Fernando Perez <email@example.com> wrote:
> On Tue, Oct 26, 2010 at 1:35 PM, MinRK <firstname.lastname@example.org> wrote:
> > Hm, that's annoying, sorry I didn't catch it.
> No worries, I didn't notice either until a while later.
> > One of my very favorite things about OSX is that since the standard meta
> > is cmd instead of ctrl, all regular GUI bindings (entirely cmd-based) and
> > all emacs-style bindings (ctrl-based) have no degeneracy, so you don't
> > to choose between having ctrl-a be home or select-all, or this cmd/ctrl-P
> > behavior, and basic emacs navigation works in *all* GUI apps by default.
> Indeed. And if only Apple had the decency to include a right Ctrl-key
> (in addition to Cmd and Alt/Option) on their laptop/small desktop
> keyboards, I might actually own an Apple machine! :) [I can't stand
> having to chord on only left-Ctrl key for everything on the smaller
> Apple keyboards, despite loving them].
> > Yes, we should do a platform check, since it would be completely hideous
> > be the only Mac app in the world that doesn't use cmd-P for print.
> > Questions:
> > Is it just Linux, or will there also be a conflict in Windows?
> > Specifically: is OSX the only one without a problem, or is Linux the
> > one with a problem?
> OSX is the only one *without* a problem. So the fix is to leave your
> current version for OSX, and switch out to Ctrl-Shift-P for all others
> (*nix, Windows).
Done and done:
It specifically checks if the print key is ctrl-P, and changes to
ctrl-shift-P if that's the case.
If, for some reason, the print key on the platform is something else, then
it won't change.
> > Is there a similar conflict on ctrl-S?
> In principle yes, except that we have no other keybinding for Ctrl-S
> yet, so I'm not that worried about that one.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-dev