-
Notifications
You must be signed in to change notification settings - Fork 17
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
emacs and lsst-lspdev #56
Comments
Emacs commands that fail on
|
@kadrlica we definitely understand the problem with the
The |
I've also been having this issue with emacs (with the Chrome browser catching up alt/option before the terminal emulator). I've heard there has been an effort to enable logging in to standard interactive login shells on the |
I'd like to know from whom you heard about that effort, because I hope we haven't done anything to raise false hopes about what you're likely to get.
Your JupyterLab instance is running in a kubernetes-managed container, which is:
a) only accessible via HTTPS routed through an external ingress, to JupyterHub, through a user-routing proxy, to an ephemeral JupyterLab container,
b) whose lifecycle is managed by Kubernetes--it is created when you launch an image from the JupyterHub menu, and is destroyed when you log out of Hub (or are idle 18 hours),
c) is dynamically scheduled onto an available node within the Kubernetes cluster, which does not have an Internet-routeable address, and further is on a virtual kubernetes container network, which
d) is also externally-unrouteable RFC 1918 address space, and is dynamically assigned at container creation time, and
e) the container has no ssh daemon running inside itself.
So, if by "login shell" you mean, "can I ssh to it and run emacs in my terminal window?" the answer is going to remain "no." Yes, the environment looks like an unprivileged user login on a shared Unix system. No, it isn't really such a thing at all.
We are attempting to debug why some keystrokes, such as C-_, aren't registering properly in the Terminal, but there's nothing we can do (other than suggest you change your browser bindings, or move to a workflow where you edit locally and then push your changes either with the JL Upload feature or by pushing to/pulling from GitHub) about keypress events consumed by the browser before the JupyterLab application ever sees them.
…________________________________
From: Justin Myles <[email protected]>
Sent: Friday, August 10, 2018 10:29 AM
To: LSSTScienceCollaborations/StackClub
Cc: Subscribed
Subject: Re: [LSSTScienceCollaborations/StackClub] emacs and lsst-lspdev (#56)
I've also been having this issue with emacs (with the Chrome browser catching up alt/option before the terminal emulator). I've heard there has been an effort to enable logging in to standard interactive login shells on the lsst-lspdev.ncsa.illinois.edu server. Is it possible to use a login shell on this server?
-
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#56 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ACVurXbq1pxJUX8HMEak-pNWnlbBA2pHks5uPcMGgaJpZM4VOQ1L>.
|
To narrow the range of investigation, I think I'm going to focus on trying to get Option+w (⌥+w) to copy text. This means that the focus is:
To accomplish this, I've followed @SimonKrughoff fourth bullet to globally remap the default keybindings. I've edited
This appears to work. It passes |
I've been trying Firefox and Chrome on Linux. Firefox is a nightmare due to the
|
A positive update, |
This is a reminder to track down the issues with emacs on lsst-lspdev. They should eventually be documented in an issue here: https://community.lsst.org/c/support/lsp
The text was updated successfully, but these errors were encountered: