8000 Certain unicode characters in phrases are accepted when entered, but do not appear when triggered · Issue #1035 · autokey/autokey · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Certain unicode characters in phrases are accepted when entered, but do not appear when triggered #1035
Open
@jhertel

Description

@jhertel

AutoKey is a Xorg application and will not function in a Wayland session. Do you use Xorg (X11) or Wayland?

Xorg

Has this issue already been reported?

  • I have searched through the existing issues.

Is this a question rather than an issue?

  • This is not a question.

What type of issue is this?

Bug

Choose one or more terms that describe this issue:

  • autokey triggers
  • autokey-gtk
  • autokey-qt
  • beta
  • bug
  • critical
  • development
  • documentation
  • enhancement
  • installation/configuration
  • phrase expansion
  • scripting
  • technical debt
  • user interface

Other terms that describe this issue if not provided above:

No response

Which Linux distribution did you use?

Linux Mint 21.3

Which AutoKey GUI did you use?

GTK

Which AutoKey version did you use?

0.95.10

How did you install AutoKey?

I do not remember. Is there a way to find out?

Can you briefly describe the issue?

I tried making the phrase "CO₂" (with immediately triggered abbreviation co2), but when it expands, I only get CO. This is in the browser (Brave), in the Terminal, in various text boxes in the GUI, and everywhere else I tried.

Can the issue be reproduced?

Always

What are the steps to reproduce the issue?

  1. Add a phrase with name CO2, content "CO₂", trigger "co2", with the following .CO2.json file:
{
    "type": "phrase",
    "description": "CO2",
    "modes": [
        1
    ],
    "usageCount": 0,
    "prompt": false,
    "omitTrigger": false,
    "matchCase": false,
    "showInTrayMenu": false,
    "abbreviation": {
        "abbreviations": [
            "co2"
        ],
        "backspace": true,
        "ignoreCase": true,
        "immediate": true,
        "triggerInside": false,
        "wordChars": "[\\w]"
    },
    "hotkey": {
        "modifiers": [],
        "hotKey": null
    },
    "filter": {
        "regex": null,
        "isRecursive": false
    },
    "sendMode": "kb"
}
  1. Save.
  2. Type co2 anywhere.
  3. See only "CO" without the "₂" appearing.

What should have happened?

CO₂ should have appeared.

What actually happened?

CO appeared.

Do you have screenshots?

No response

Can you provide the output of the AutoKey command?

Anything else?

Even if there for some reason is trouble sending certain unicode characters in phrases, I intuitively expect the program to be automatically aware of that and use another method that works to send specifically these characters. So, if certain characters like "₂" cannot be sent directly, I would expect the program to send them in a way that works, like "<ctrl>+<shift>+u+2082 " in this case, without the user having to be aware of it.

I am not as such criticising the program as it is, as I am sure it in a sense works as intended, and it is certainly extremely useful already the way it is, especially because there are workarounds.

I am just describing how it feels like a bug when you write a certain text, it is accepted by AutoKey, and then discover that that text doesn't actually appear when the phrase is expanded. My mind have difficulty understanding why the program couldn't "just" convert unicode characters known not to work, or perhaps all the non-ANSI/ASCII ones.

If perhaps there can be problems with the "<ctrl>+<shift>+u+XXXX " solution in certain cases (I don't know), there could be a check box indicating that you do want it so send these unicode replacements for special unicode characters with this specific phrase. Maybe the "Paste using" dropdown could have a new method "Keyboard with unicode replacement" (and allow that to be set as the default in the Preferences). But I don't even know if there could be problems with the "<ctrl>+<shift>+u+XXXX " solution in certain cases, so I might be overthinking that.

I am a long time developer but new to Linux, and I am setting up my shortcuts and similar from Windows now, reporting things I find strange before I get too used to them and forget to report them.


This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #1035 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @jhertel (replace 20 with the amount, and @jhertel with the user to tip).

📖 If you want to learn more, check out our documentation.

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0