I created the FogBugz case 17747 for it (https://pharo.fogbugz.com/f/cases/17747/Nautilus-history-navigation-hotkeys-prevent-entering-square-brackets-on-german-spanish-Mac-OS-X).

CU,

Udo



On 02/03/16 18:44, Miguel Campusano wrote:
I have the same problem with a spanish layout

On Wed, Mar 2, 2016 at 10:27 AM Udo Schneider
<udo.schnei...@homeaddress.de
<mailto:udo.schnei...@homeaddress.de>> wrote:

    Ok - found it.

    Somewhere in the last updates the Nautilus Keybinding for previous/next
    was changed from Cmd+[ / Cmd+] to Meta+[ / Meta+] (defined in
    (AbstractNautilisUI>>#buildClassShortcutsOn:)

    Could we please change this? Having these shortcuts make it impossible
    to enter square brackets in Nautilus when using a german keyboard.

    CU,

    Udo


    On 02/03/16 12:33, Udo Schneider wrote:
    > Quick update:
    >
    > Test on Windows (US-english, DE Keyboard) with newest VM
    > (stable-20160218): NO ISSUES
    >
    > Test on Windows (US-english, DE Keyboard) with newest VM
    (stable-20160218):
    > * Does work w/o any problem in Playgrounds
    > * Does not work in Nautilus.
    >
    > From a quick before freezing I saw that somewhere along that stack
    that
    > KMKeymap tried to interpret the square brackets as Meta+[ and Meta+].
    > This would be in line with the german Mac OS X keyboard mapping where
    > the brackets are on Option+5 and Option+6. As on Mac OS X Option is
    > equivalent to Alt I assume this is what is interpreted as Meta+[ and
    > Meta+].
    > Still I'm not quite sure why in this case (only in Nautilus it seems)
    > the pressed Meta/Alt/Option key is interpreted in this case as this is
    > simply required to enter square brackets on a german keyboard. It does
    > not imply a command or something like this.
    >
    > Any thoughts? Anything you want me to debug?
    >
    > CU,
    >
    > Udo
    >
    >
    > On 01/03/16 22:13, Udo Schneider wrote:
    >> All,
    >>
    >> I'm currently chasing a strange problem with new 5.0 based Images.
    >>
    >> In the regular Pharo 5.0 Beta Image and current Moose (5.1) Image you
    >> can't enter square brackets anymore. It seems to change the
    >> class/category/method selection in Nautilus and causes a
    non-breakable
    >> loop of discarding/ignoring/saving the changes dialog for changed
    >> methods...
    >>
    >> Checking the same VM with older 5.0 images works w/o any problem.
    So I
    >> assume an image problem - not a VM problem.
    >>
    >> Has anyone seen this?
    >>
    >> I'm currently testing on Mac OS X with a german keyboard and
    US-English
    >> locale. Will test on Windows tomorrow.
    >>
    >> CU,
    >>
    >> Udo
    >>
    >>
    >>
    >> Pharo 5.0 Details:
    >>
    >> Smalltalk image version.
    >> "'Pharo5.0'"
    >>
    >> SystemVersion current imageVersionString.
    >> "'Pharo-5.0-50622-'"
    >>
    >> Smalltalk vm version.
    >> "'CoInterpreter * VMMaker.oscog-rmacnak.1586 uuid:
    >> 8e44b2a7-68ee-4fc9-8513-a04520267053 Dec 13 2015
    >> StackToRegisterMappingCogit * VMMaker.oscog-rmacnak.1586 uuid:
    >> 8e44b2a7-68ee-4fc9-8513-a04520267053 Dec 13 2015
    >> https://github.com/estebanlm/pharo-vm.git Commit:
    >> 6dc730123e8f2b0327839b235d16e0604a92288e Date: 2015-12-13
    00:23:41 +0100
    >> By: Esteban Lorenzano
    >> <esteba...@gmail.com
    <mailto:esteba...@gmail.com>> Jenkins
    build #456
    >> '"
    >>
    >> Moose Details:
    >>
    >> Smalltalk image version.
    >> "'Pharo5.0'"
    >>
    >> SystemVersion current imageVersionString.
    >> "'Pharo-5.0-50622-'"
    >>
    >> Smalltalk vm version.
    >> "'CoInterpreter * VMMaker.oscog-rmacnak.1586 uuid:
    >> 8e44b2a7-68ee-4fc9-8513-a04520267053 Dec 13 2015
    >> StackToRegisterMappingCogit * VMMaker.oscog-rmacnak.1586 uuid:
    >> 8e44b2a7-68ee-4fc9-8513-a04520267053 Dec 13 2015
    >> https://github.com/estebanlm/pharo-vm.git Commit:
    >> 6dc730123e8f2b0327839b235d16e0604a92288e Date: 2015-12-13
    00:23:41 +0100
    >> By: Esteban Lorenzano
    >> <esteba...@gmail.com
    <mailto:esteba...@gmail.com>> Jenkins
    build #456
    >> '"
    >>
    >>
    >>
    >
    >
    >
    >






Reply via email to