Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Is there a way to use Helium on a remote machine through rmate?

Open
#116 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
jupyter, python
Domain
tooling

Research direction

No file, test, or entry point is identified. Reproduce the reported workflow with Helium, Jupyter Notebook, Sublime Text, and rmate, then determine whether remote execution and imports from the remote server are supported; done means documenting a verified workaround or defining the required feature.

Written by the indexing model from the issue text.

Description

feature

Hi,

I've been wondering if it's possible to have both jupyter notebook's interactive mode and sublime text's editing interface at the same time for a code/notebook on a remote machine, and it seems that Helium might provide such an environment.

My workflow is to edit locally and run remotely codes on a remote server using rmate. I tested if it is possible to execute a code that is locally open via rmate but saved on a remote server through Helium. There was a crucial problem: it seemed that Helium interprets this code as a local file (in /tmp folder where rmate temporarily saves the code in the local machine), and therefore it could not "import" python modules saved on the remote server. rmate doesn't suffer from such problems, because once I save the code, it immediately transfers through ssh to the remote server and update the code there. After that, I can run the updated code on the remote server.

Is there any way to work around the above problem?

Dominant language
Python
Stars
255
Forks
16
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SublimeText/Helium

All issues in SublimeText/Helium

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.