Re: Command Shell best practices
  By: Paulie420 to Digital Man on Thu May 14 2020 12:39 am

 >   Re: Command Shell best practices
 >   By: Digital Man to Paulie420 on Wed May 13 2020 09:51 pm
 >
 >  >> > Gosh I hope I'm making a little sense. I sometimes feel that my mind
 > is
 >  >> jumbled when discussing sync... but I'm trying.
 >
 >  DM> I totally get what you're saying. If you know that you aren't going to
 >  DM> be making *any* other command shells available to your users, then just
 >  DM> move the text/menu/renegade/* files into text/menu, copy
 >  DM> exec/renegade.src to exec/yourshell.src and then remove the "renegade/"
 >  DM> parts of the menu paths in the file. Then edit all the menu files
 >  DM> (*.msg is preferred) to suit your style/command-keys.
 >
 >  DM> digital man
 >
 > Dude I get what you're saying too... perfect, and thanks for taking the time
 > to type that out... I'd be correct, then, that if I just name my one shell
 > to default (my RG one...) then ALL those menu's (preferably .msg) will be in
 > the /menu section... and not /menu *and* /menu/renegade (or /yourshell)...

It doesn't matter what you name your shell. I would avoid "default" however
just as that name is sort of already taken by the Synchronet classic shell. And
the name of the shell (the base filename of the .src or .bin file) has no
direct impact on what, if any, subdirectories off of text/menu are used.


                                            digital man

Synchronet "Real Fact" #34:
The back-up synchro.net nameserver and CVS repository is hosted by Deuce.
Norco, CA WX: 74.4øF, 51.0% humidity, 5 mph NNW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.11-Linux