vermaneerajin / shellinabox

Automatically exported from code.google.com/p/shellinabox
Other
0 stars 0 forks source link

No apparent discussion forum (this submission also includes a couple of queries) #131

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
I cannot see how I can mark this as anything but a defect, so I'll say that the 
defect is that there does not seem to be a place to pose questions or 
suggestions, regarding this nice bit of software.

Now for a couple of questions:

*  When connecting to a bash shell, is there any way to make SiaB set an 
environmental variable, so that different actions could be executed in 
.profile, depending on its existence?  If that variable could also include 
which .css file is being used on login as well, that would be fantastic.  I 
would love this to be possible.

*  Is there any way to make client-side keybindings, like I can with my SSH 
client?  I would like to bind gnome-terminal CTRL-ArrowKeys bindings in 
particular.

Thanks.

Original issue reported on code.google.com by gomez...@gmail.com on 17 Aug 2011 at 8:29

GoogleCodeExporter commented 8 years ago
As well as the CTRL-ArrowKeys, I would like to change the keybinding for 
CTRL-Home, CTRL-End, CTRL-BackSpace and CTRL-Delete.

Is there a way to alter these keycodes in the source and recompile, if this is 
not possible through a settings file?

Original comment by gomez...@gmail.com on 18 Aug 2011 at 4:34

GoogleCodeExporter commented 8 years ago
While I cannot be sure without doing some digging, I don't believe that we have 
control over the environment for login shells.  Normally, this is the 
responsibility of the sysadmin policy and is controlled from system 
configuration files.

You may be able to determine that you are running in an SIAB session by looking 
at the attached tty.

If I discover a way to set environment variables or make some other user 
apparent change to the shell environment I'll let you know.

BTW, it is best to separate out queries that are not related.  It make it hard 
to track disparate feature requests when they share a common report.

Original comment by beewoo...@gmail.com on 31 Mar 2012 at 10:39