Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IDLE: config-main.def contains windows-specific settings #43624

Closed
ronaldoussoren opened this issue Jul 6, 2006 · 7 comments
Closed

IDLE: config-main.def contains windows-specific settings #43624

ronaldoussoren opened this issue Jul 6, 2006 · 7 comments
Labels
topic-IDLE type-bug An unexpected behavior, bug, or error

Comments

@ronaldoussoren
Copy link
Contributor

BPO 1517993
Nosy @terryjreedy, @kbkaiser, @ronaldoussoren, @ned-deily
Superseder
  • bpo-20580: IDLE should support platform-specific default config defaults
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2014-06-10.00:27:05.664>
    created_at = <Date 2006-07-06.08:29:03.000>
    labels = ['expert-IDLE', 'type-bug']
    title = 'IDLE: config-main.def contains windows-specific settings'
    updated_at = <Date 2014-06-10.00:27:05.581>
    user = 'https://github.com/ronaldoussoren'

    bugs.python.org fields:

    activity = <Date 2014-06-10.00:27:05.581>
    actor = 'terry.reedy'
    assignee = 'none'
    closed = True
    closed_date = <Date 2014-06-10.00:27:05.664>
    closer = 'terry.reedy'
    components = ['IDLE']
    creation = <Date 2006-07-06.08:29:03.000>
    creator = 'ronaldoussoren'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 1517993
    keywords = []
    message_count = 7.0
    messages = ['29066', '29067', '29068', '84287', '220124', '220127', '220132']
    nosy_count = 5.0
    nosy_names = ['terry.reedy', 'kbk', 'ronaldoussoren', 'gpolo', 'ned.deily']
    pr_nums = []
    priority = 'low'
    resolution = 'duplicate'
    stage = None
    status = 'closed'
    superseder = '20580'
    type = 'behavior'
    url = 'https://bugs.python.org/issue1517993'
    versions = ['Python 2.7', 'Python 3.4', 'Python 3.5']

    @ronaldoussoren
    Copy link
    Contributor Author

    The default values in config-main.def contain values that are specific for
    Windows. This means that the key-bindings for other platforms, such as
    OSX will be wrong (because config-main selects the windows keybindings
    as the default keybindings).

    I've worked around this by copying a mac version of config-main.def over
    the installed version of config-main.def from Mac/IDLE/Makefile.in. That
    is obviously a crude hack, but I know of no better solution.

    @kbkaiser
    Copy link
    Contributor

    Logged In: YES
    user_id=149084

    Not so crude, since there is a Mac/IDLE/ dir? I
    gather this works ok for 2.5 installs on OSX?

    Perhaps IDLE should be modified to try to detect
    the platform and only use the entry in
    config-main.def if detection fails. The [keys]
    section is necessary, I believe, to mirror the
    [keys] section in the user's config-main.cfg if
    he changes keybindings.

    But you would still need Mac/IDLE/, would you not?

    @ronaldoussoren
    Copy link
    Contributor Author

    Logged In: YES
    user_id=580910

    Mac/IDLE contains support code for building and installing an application
    bundle for IDLE, which gives us a nice icon to click on :-)

    Detecting the platform and automaticly using platform-specific settings
    would be nice and would mostly solve my problem. "Mostly" because config-
    extensions.def also contains key-binding definitions; which could well be
    platform-specific (AquaTk doesn't seem to support the ALT modifier).

    IMHO the current workaround is crude because I maintain a seperate copy of
    several configuration files just to change a small number of settings. I have
    lowered the priority of this issue because I don't think this is very important.

    @gpolo
    Copy link
    Mannequin

    gpolo mannequin commented Mar 27, 2009

    For config-extensions.def:
    What do you think about moving all shortcuts to config-keys and then
    always use the name of the shorcut in config-extensions instead of the
    shorcut ?

    For config-main.def:
    For the [Keys] section I believe it would be better to rename the
    "default" option to "custom". If custom is true, then idle uses the key
    set defined by the name option, otherwise it uses the one that fits
    better the platform. If the user changes the key set that supposedly
    fits better his platform through the "Configure IDLE" dialog then we set
    custom to True (independently of this new key set being a custom one or
    a default one but that is not the default for his platform) and set the
    name option to the name of the key set. Any thoughts ?

    @BreamoreBoy BreamoreBoy mannequin added type-bug An unexpected behavior, bug, or error labels Jun 9, 2014
    @terryjreedy
    Copy link
    Member

    In 3.4, the only Windows-specific settings I see in config-main.def is
    [Keys]
    default= 1
    name= IDLE Classic Windows

    I have presumed that this is somehow changed on other systems. If not, that is an issue.

    Config-keys.def actions (should) have a Meta variant when Alt is used.
    close-window=<Alt-Key-F4> <Meta-Key-F4>

    If 'Alt' were automatically changed to 'Meta' on Mac, before sending to tk, the Meta entries could be removed, with a note in the key-setting dialog about the auto translation. The file would be easier to read; setting keys would then be easier; and Macs would automatically get key bindings.

    (I notice that some actions have two Alt bindings and only one Meta binding. Is that because Meta in not value for all uses of Alt?)

    @ned-deily
    Copy link
    Member

    bpo-20580 covers much the same grounds; I was unaware of this issue when I opened it.

    @terryjreedy
    Copy link
    Member

    Since bpo-20580 has a much more specific plan, I am closing this one as a duplicate and back-referencing this from there.

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    topic-IDLE type-bug An unexpected behavior, bug, or error
    Projects
    None yet
    Development

    No branches or pull requests

    4 participants