Problem when used with AppImage #3537

vinismarques · 2024-09-24T21:05:11Z

vinismarques
Sep 24, 2024

Describe the bug
I am using Cursor.AI (VSCode-based) to develop and mise does not work when my shell is Zsh.

To Reproduce

Add eval "$(mise activate zsh)" on the zshrc file
Set Cursor to use Zsh as default shell
Open a project that uses node and try using the integrated terminal. It will open two new unsaved tabs/files in the current window called "activate", and "zsh".

Expected behavior
Shell should be set to the correct node version.

mise doctor output

version: 2024.9.7 linux-x64 (743b7a7 2024-09-23)
activated: yes
shims_on_path: no

build_info: 
  Target: x86_64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS, OPENSSL
  Built: Mon, 23 Sep 2024 21:09:00 +0000
  Rust Version: rustc 1.81.0 (eeb90cda1 2024-09-04)
  Profile: release

shell: 
  /usr/bin/zsh
  zsh 5.9 (x86_64-pc-linux-gnu)

dirs: 
  data: ~/.local/share/mise
  config: ~/.config/mise
  cache: ~/.cache/mise
  state: ~/.local/state/mise
  shims: ~/.local/share/mise/shims

config_files: 
  ~/.config/mise/config.toml
  ~/.mise.toml

backends: 
  cargo
  core
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins: 


toolset: 
  node@20.12.1  

env_vars: 
  MISE_SHELL=zsh

settings: 
  activate_aggressive = false
  all_compile = false
  always_keep_download = false
  always_keep_install = false
  asdf = true
  asdf_compat = false
  cache_prune_age = "30d"
  cargo_binstall = true
  color = true
  disable_default_shorthands = false
  disable_hints = []
  disable_tools = []
  experimental = false
  go_default_packages_file = "~/.default-go-packages"
  go_download_mirror = "https://dl.google.com/go"
  go_repo = "https://github.com/golang/go"
  go_set_gopath = false
  go_set_goroot = true
  go_skip_checksum = false
  http_timeout = 30
  jobs = 4
  legacy_version_file = true
  legacy_version_file_disable_tools = []
  libgit2 = true
  node_compile = false
  not_found_auto_install = true
  paranoid = false
  pipx_uvx = false
  plugin_autoupdate_last_check_duration = "7d"
  python_default_packages_file = "~/.default-python-packages"
  python_pyenv_repo = "https://github.com/pyenv/pyenv.git"
  raw = false
  trusted_config_paths = []
  quiet = false
  use_versions_host = true
  verbose = false
  vfox = false
  yes = false
  ci = false
  debug = false
  trace = false
  log_level = "info"
  python_venv_auto_create = false

  [ruby]
  default_packages_file = "~/.default-gems"
  ruby_build_repo = "https://github.com/rbenv/ruby-build.git"
  ruby_install = false
  ruby_install_repo = "https://github.com/postmodern/ruby-install.git"

  [status]
  missing_tools = "if_other_versions_installed"
  show_env = false
  show_tools = false

No warnings found
No problems found

Additional context
I posted about it in #921, but since that was closed before I commented, I figured I should open a new one.

Things I tried (Zsh):

Using eval "$(mise activate zsh)" on the zshrc file: when starting a new integrated terminal on Cursor, it opens two new unsaved tabs/files in the current window called "activate", and "zsh".
Using eval "$(mise activate --shims)": when starting a new integrated terminal on Cursor, it opens one new unsaved tab/file called "activate" in the current window and prints "Warning: 'shims' is not in the list of known options, but still passed to Electron/Chromium." to the terminal.
Using export PATH="$HOME/.local/share/mise/shims:$PATH": does not open any weird tabs when starting a new integrated terminal, nor outputs any error/warning message to the terminal, but when I try something like node -v it opens a new Cursor window, instead of printing the version.
Running mise doctor on the integrated terminal: opens unsaved file called "doctor".
Running mise one two three on the integrated terminal: will open unsaved files called "one", "two", and "three" in the current window.
Running just mise on the integrated terminal: opens a new IDE window.

On Bash, it seems to work fine with all methods... eval "$(mise activate bash)", eval "$(mise activate --shims)" and export PATH="$HOME/.local/share/mise/shims:$PATH". It prints the node version as expected when using node -v and does not open any weird tab or window.

I also have VSCode (non-AppImage), which Cursor is based on and it works with Zsh, so it seems something weird is going on only when using Zsh+AppImage.

smujaddid · 2024-11-22T14:56:56Z

smujaddid
Nov 22, 2024

I have the same problem, can't activate mise in integrated terminal of Cursor editor (AppImage) and ZSH.

mise ERROR cursor-0.42.5x86_64_3aad2fcb25d24d988a41f8c6ac0bc2f1.AppImage is not a valid shim
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

It is working for bash only though.

0 replies

smujaddid · 2024-11-23T23:13:06Z

smujaddid
Nov 23, 2024

I ended up extracting the Cursor AppImage and run Cursor from there. No more error when using mise, just like in the vscode.

0 replies

hoshsadiq · 2025-03-26T15:04:03Z

hoshsadiq
Mar 26, 2025

@jdx any updates on this? It would be nice to have to extract Cursor due to various reasons.

0 replies

wasdee · 2025-04-30T04:15:37Z

wasdee
Apr 30, 2025

https://forum.cursor.com/t/i-cannot-run-the-appimage-file-on-ubuntu-24-04/6289

Xupack
You need to change the “/home/{USER}/Applications/cursor/*.AppImage” in file “/etc/apparmor.d/cursor-appimage” to where your > Cursor AppImage is located, for me, I changed it to “/home/xupack/cursor/cursor-0.37.1x86_64.AppImage” and then ran the “sudo > apparmor_parser -r /etc/apparmor.d/cursor-appimage” command. Hope this helps!

0 replies

hoshsadiq · 2025-05-05T10:23:54Z

hoshsadiq
May 5, 2025

As a temporary workaround, you can get it working again by relaunching your shell, and then source mise again:

$ exec $SHELL --login
...
$ source <(mise activate $SHELL)
...
$ mise ls --current
...
$ go version
go version go1.24.2 linux/amd64

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Problem when used with AppImage #3537

{{title}}

Replies: 5 comments

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Problem when used with AppImage #3537

vinismarques Sep 24, 2024

Replies: 5 comments

smujaddid Nov 22, 2024

smujaddid Nov 23, 2024

hoshsadiq Mar 26, 2025

wasdee Apr 30, 2025

hoshsadiq May 5, 2025

vinismarques
Sep 24, 2024

smujaddid
Nov 22, 2024

smujaddid
Nov 23, 2024

hoshsadiq
Mar 26, 2025

wasdee
Apr 30, 2025

hoshsadiq
May 5, 2025