8000 FAQ: "permission denied" when running your Racket program · Issue #666 · greghendershott/racket-mode · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
FAQ: "permission denied" when running your Racket program #666
Open
@greghendershott

Description

@greghendershott
  • When you use Racket as installed from https://snapcraft.io/racket, it runs using strict confinement.

    Among other restrictions, Racket won't be able to read from directories named starting with a dot -- for example: ~/.emacs.d/elpa.

    AND...

  • When you install Racket Mode as a normal Emacs package from MELPA, its files go under ~/.emacs.d/elpa.

    Therefore when Racket Mode starts its "back end", written in Racket, it does racket ~/.emacs.d/elpa/racket-mode-xxx/main.rkt. Ergo the permission error.

Ways to avoid this problem

To avoid the problem, avoid either of the above conditions:

  • Install Racket directly from https://download.racket-lang.org/. Racket's Linux installer is easy to use and flexible.

    (Facts: Distro packages of Racket tend to be very old versions. Although the snap package is newer, unfortunately it comes with strict confinement.

    Opinions: Sometimes it's best to get things direct, and, with freedom to use a programming language to write/use any program you wish... even a program that reads from certain directories. 😄)

    OR...

  • Install Racket Mode so its files are not under a dot directory. Any of the following can work:

    • Clone the files from here on GitHub, and add that directly to load-path in your Emacs init file.

      OR...

    • Move your entire elpa subdirectory from under ~/.emacs.d to somewhere else, like ~/emacs-packages, and add (setq package-user-dir "~/emacs-packages") early in your Emacs init file, before any other package-xxx expressions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    FAQFor pinning at top of issues list.ubuntu/snap

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0