Hi Kevin
Wishing you well. Your comment gave me some cause to think, and doa bit of
experimenting.
My interpretation of the behaviour was not true; and the a short-cut in a
system directory doesn't make any different either. I cna make sense of
things now.
Firstly "notepad", is notpad.exe and not a short-cut. If there is a
shortcut it is for the menu system. Back to Windows architecture, programs
are either command or GUI (windows) apps.
My 'problem' is that I forgot I made a shoes.bat; which is a commany
program. So my issues were self-induced.
When I run the real shoes.exe from the command line, it fires off like a
fork()
* C:\bin\shoes\0.r1134\shoes.exe
and I am greeted by the next command prompt, just like notepad.
My poor memory. I had the idea of keeping one folder to fire-up Shoes in my
PATH string, to save having to edit it when there are changes. NOW, this
was good because I learned somethign about .LNK (short-cut) files and here's
how you CAN use the short-cut to fire-up Shoes.
Just pretend you have a bin\shoes directory like c:\bin\shoes\
1. Use the file explorer (Windows exporer) to create a short-cut to
Shoes.exe
- In my case it is in the Raisins release folder:
C:\bin\shoes\0.r1134\shoes.exe
2. You need to edit theshort-cut file's properties to do two things:
1. Rename the short-cut from "shoes.exe" to "shoes". (The full
internal file name will actually be "Shoes.lnk")
2. In the [Shortcut] tab on the properties page clear the "Start in"
textbox.
- If you don't do that, shoes fires-up in the 0.r1134 folder instead
of your current folder.
- This process is really only for running short-cuts from the
command line. There may be implications for not having a
start-in directory
if you run programs from the start menu.
3. Move the short cut to the folder you keep in your path string
you want to keep your shoes start-up command. E.g. c:\bin\shoes\; or now
that I know how this works, I might put it in c:\bin\util -- with the other
handy files.
4. Go to the environment variables by right-clicking My Computer select:
- Properties; then the
- Advanced tab; and press the
- *Environment Variable* button
5. Select the PATHEXT (path extentsions) variable and add the
short-cut extension to the list. It might look something like this:
- .COM;.EXE;.BAT;.CMD;.WSH;.RB;.RBW;.LNK
6. Start a new command prompt window and test it out.
That gets me what, I wanted a single start Shoes file in a fixed place that
I can maintain when I update shoes. Allowing .LNK files to be used in your
command-line search path should be OK, because it is right at the very end
of the list of options.
aloha,
\_w_/
___________________________________
º http://mbimarketing.wordpress.com
º http://adroit-process.blogspot.com
2009/8/3 kevin van oosterhout <[email protected]>
> Hi,
>
> This happend to me as well.
>
> I solved it by putting a shortcut in the "/WINDOWS" directory.
> This is quite the same as how the other commands (notepad, regedit, etc.)
> work.
>
> Hope this helps..
>
> btw I already wrote a mail about this earlier.
>
> ----- Original Message -----
> *From:* * William <[email protected]>
> *To:* [email protected]
> *Sent:* Saturday, August 01, 2009 3:41 PM
> *Subject:* Re: Run Shoes from command line?
>
> Shoes doesn't quite work the way I expected with the Windows Start command.
>
> For the non-Windows people, I'll explain .. Start is like:
>
> $ shoes myShinyApp.rb &
>
> But actually, under windows when one kick-s a GUI application is _should_
> fire off to the windows message-loop as a window program. For example; look
> at the difference
>
>
