-
Single key to switch command shells?
From
Razor@VERT/SILENT to
All on Sun Feb 28 08:47:39 2010
I'd like to "quit" from my custom shell back to the "default" shell. What I'mãdoing so far doesn't seem to change the user config option for command shell &ãdisconnects me from telnet. Here's my current code:ãcase 'Q':ã user.command_shell="DEFAULT";ã exit(0);ããDoes anyone see an obvious error in my logic? This is similar to code used forãchanging shells through the user config editor.ããã---ã þ Synchronet þ The Silent Strike - bbs.thesilentstrike.comã
-
From
Digital Man@VERT to
Razor on Sun Feb 28 17:25:06 2010
Re: Single key to switch command shells?ã By: Razor to All on Sun Feb 28 2010 08:47 amãã > I'd like to "quit" from my custom shell back to the "default" shell. Whatã > I'm doing so far doesn't seem to change the user config option for commandã > shell & disconnects me from telnet. Here's my current code:ã > case 'Q':ã > user.command_shell="DEFAULT";ã > exit(0);ã >ã > Does anyone see an obvious error in my logic?ããThe setting of the command shell looks correct, but I don't understand the useãof exit(). Shells are not normally "nested". An exit() would just stop theãshell.ãã digital manããSnapple "Real Fact" #77:ãNo piece of paper can be folded more than 7 times.ã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã
-
From
Razor@VERT/SILENT to
Digital Man on Sun Feb 28 22:09:46 2010
Re: Single key to switch command shells?ã By: Digital Man to Razor on Sun Feb 28 2010 05:25 pmãã > Re: Single key to switch command shells?ã > By: Razor to All on Sun Feb 28 2010 08:47 amã > > I'd like to "quit" from my custom shell back to the "default" shell.ã > > case 'Q':ã > > user.command_shell="DEFAULT";ã > > exit(0);ã > The setting of the command shell looks correct, but I don't understand theã > use of exit(). Shells are not normally "nested". An exit() would just stopã > the shell.ããAhh, I was never executing the new shell. I still don't quite have it, but Iãmight come back to that later.ãNow I'm trying to choose a shell from logon.js & no matter which I choose, Iãalways get DEFAULT. Here's my code for that.ããif(!console.noyes("Quick logon"))ã{ã user.command_shell="RQSHELL";ã}ãelseã{ã user.command_shell="DEFAULT";ã}ãããã---ã þ Synchronet þ The Silent Strike - bbs.thesilentstrike.comã
-
From
Digital Man@VERT to
Razor on Sun Feb 28 23:04:34 2010
Re: Single key to switch command shells?ã By: Razor to Digital Man on Sun Feb 28 2010 10:09 pmãã > Re: Single key to switch command shells?ã > By: Digital Man to Razor on Sun Feb 28 2010 05:25 pmã >ã > > Re: Single key to switch command shells?ã > > By: Razor to All on Sun Feb 28 2010 08:47 amã > > > I'd like to "quit" from my custom shell back to the "default" shell.ã > > > case 'Q':ã > > > user.command_shell="DEFAULT";ã > > > exit(0);ã > > The setting of the command shell looks correct, but I don't understandã > > the use of exit(). Shells are not normally "nested". An exit() wouldã > > just stop the shell.ã >ã > Ahh, I was never executing the new shell. I still don't quite have it, butã > I might come back to that later.ã > Now I'm trying to choose a shell from logon.js & no matter which I choose,ã > I always get DEFAULT. Here's my code for that.ã >ã > if(!console.noyes("Quick logon"))ã > {ã > user.command_shell="RQSHELL";ã > }ã > elseã > {ã > user.command_shell="DEFAULT";ã > }ããYou discovered a bug with the Synchronet JS "User" class, which I just fixed.ãWhen setting the command_shell property, it was writing to the host_name /ãcomputer property instead. If you get tonight's development build (dated mar-1)ãthis should be fixed.ãã digital manããSnapple "Real Fact" #158:ãThe first MTV video was "Video Killed the Radio Star," by the Buggles. ã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã
-
From
Razor@VERT/SILENT to
Digital Man on Mon Mar 1 11:25:11 2010
Re: Single key to switch command shells?ã By: Digital Man to Razor on Sun Feb 28 2010 11:04 pmãã > You discovered a bug with the Synchronet JS "User" class, which I justã > fixed. When setting the command_shell property, it was writing to theã > host_name / computer property instead. If you get tonight's developmentã > build (dated mar-1) this should be fixed.ããVery cool, thanks DM.ããã---ã þ Synchronet þ The Silent Strike - bbs.thesilentstrike.comã