[go: nahoru, domu]

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

can't exclude espanso in specific apps #1957

Open
1 task
davidawad opened this issue Apr 24, 2024 · 2 comments
Open
1 task

can't exclude espanso in specific apps #1957

davidawad opened this issue Apr 24, 2024 · 2 comments
Labels
bug something isn't working needs-triage more investigation is needed on this issue to understand the problem

Comments

@davidawad
Copy link

Description

i'm using macos latest

$ uname -a
Darwin sodium 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000 arm64

For some reason, I can't get espanso to NOT expand when using iterm2 or vscode.

Steps to reproduce

Neither of these options in espanso edit work. I can confirm the expansions still work in these apps.
global:
exclude:
- "Terminal"
- "iTerm2"
- "Visual Studio Code"

filter_title:

  • "Visual Studio Code"
  • "iTerm2"
    enable: false

How do I disable them?

thanks

Expected behavior

it shouldn't expand in iterm

Screenshots

not needed

Logs

avid@sodium ~/Desktop> espanso log 127
17:51:03 [daemon(75142)] [INFO] reading configs from: "/Users/david/Library/Application Support/espanso"
17:51:03 [daemon(75142)] [INFO] reading packages from: "/Users/david/Library/Application Support/espanso/match/packages"
17:51:03 [daemon(75142)] [INFO] using runtime dir: "/Users/david/Library/Caches/espanso"
17:51:03 [daemon(75142)] [INFO] system info: Darwin v14.0 - kernel: 23.0.0
17:51:03 [daemon(75142)] [INFO] watching for changes in path: "/Users/david/Library/Application Support/espanso"
17:51:03 [daemon(75142)] [INFO] espanso version: 2.2.1
17:51:03 [daemon(75142)] [INFO] spawning the worker process...
17:51:03 [daemon(75142)] [INFO] binded to IPC unix socket: /Users/david/Library/Caches/espanso/espansodaemonv2.sock
17:51:03 [worker(75143)] [INFO] reading configs from: "/Users/david/Library/Application Support/espanso"
17:51:03 [worker(75143)] [INFO] reading packages from: "/Users/david/Library/Application Support/espanso/match/packages"
17:51:03 [worker(75143)] [INFO] using runtime dir: "/Users/david/Library/Caches/espanso"
17:51:03 [worker(75143)] [INFO] system info: Darwin v14.0 - kernel: 23.0.0
17:51:04 [worker(75143)] [INFO] using CocoaAppInfoProvider
17:51:04 [worker(75143)] [INFO] binded to IPC unix socket: /Users/david/Library/Caches/espanso/espansoworkerv2.sock
17:51:04 [worker(75143)] [INFO] monitoring the status of the daemon process
17:51:04 [worker(75143)] [INFO] monitoring the status of secure input
17:51:04 [worker(75143)] [INFO] using CocoaSource
17:51:04 [worker(75143)] [INFO] using MacInjector
17:51:04 [worker(75143)] [INFO] using CocoaClipboard
17:51:14 [worker(75143)] [WARN] detected inconsistent modifier state for keys [(Meta, 55)], sending compensating events...
17:52:52 [worker(75143)] [WARN] detected inconsistent modifier state for keys [(Meta, 55)], sending compensating events...
17:53:19 [worker(75143)] [WARN] detected inconsistent modifier state for keys [(Meta, 55)], sending compensating events...
17:53:28 [worker(75143)] [WARN] detected inconsistent modifier state for keys [(Meta, 55)], sending compensating events...
david@sodium ~/Desktop>

Your environment

  • Public source code: espanso 2.2.1
  • Environment name and version (e.g., Rust 1.59.0):
  • Operating system and version (e.g., Ubuntu 20.04.2 LTS): mac OS (uname above)
  • Espanso version (e.g., 2.1.4-beta): 2.2.1

Self-service

  • I'd be willing to fix this bug myself.
@davidawad davidawad added the bug something isn't working label Apr 24, 2024
@davidawad
Copy link
Author
davidawad commented Apr 24, 2024

these also didn't work, I feel like i'm losing my mind here it absolutely must be possible to say "I don't want espanso here" in the global config file.

global:
  exclude:
    - "Terminal"
    - "iTerm2"
    - "Visual Studio Code"
    - "com.googlecode.iterm2"
    - "com.microsoft.VSCode"

filter_title:
  - "Visual Studio Code"
  - "com.googlecode.iterm2"
  - "com.microsoft.VSCode"
  - "iTerm2"
enable: false

@smeech
Copy link
Collaborator
smeech commented Apr 24, 2024

Have another look at https://espanso.org/docs/configuration/app-specific-configurations/
As I understand it, you need to be using #detect# in each program, to determine the filter_class:,filter_title: or filter_exec: (mainly Windows), in that order of priority, and construct a separate espanso/config file for each program.

For example, #detect# reports

title: 'Bash'
exec: ''
class: 'Xfce4-terminal

for my terminal emulator, so my espanso/config file for that program begins: filter_class: terminal. I would follow that with enable: false from Options Reference if I didn't want Espanso to work in my Terminal sessions.

The use_standard_includes: false command would probably do the same, but I've only begun trying it.

@AucaCoyan AucaCoyan added the needs-triage more investigation is needed on this issue to understand the problem label Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working needs-triage more investigation is needed on this issue to understand the problem
Projects
None yet
Development

No branches or pull requests

3 participants