Wednesday, February 15
Quick launch workspaces
Hack Attack: Quick launch workspaces - Lifehacker
An interesting article. The issue I have with it is that, properly coded, you can deal with spaces in a shortcut. I would make a comment about this, but I find their way of getting commenters to be absolutely assinine, with an emphasis on ass.
Now, how do you start a shortcut with spaces in the name?
start "" "shortcut with spaces in the name.lnk"
Yeah, you just put in a null string as the first parameter (which Windows takes as the name of the created window, which I find absolutely f---ed up), and then the next quoted string is taken as the shortcut.
So, you can create a .bat/.cmd file called st.cmd and make that
@echo off
start "" %*
Or, you can do what I did, which was to take the Windows 95 start.exe, and rename that to st.exe and use
st "shortcut with spaces in the name.lnk"
You can't just use start.exe, unless you spell it completely out with extension because start (no extension) is a built in command to cmd.exe.
And then, if you want to start everything in a folder by itself, you can just code this short little .cmd file:
@echo off
for %%j in (*.lnk) do start "" "%%j"
for %%j in (*.url) do start "" "%%j"
This way, you can just drag the URLs from the title bar to the folder, and not even have to worry about setting a shortcut to Firefox/Opera/Internet Explorer. Reading further, I see the reason why he setup a shortcut to Firefox. With my setup, if I start another .LNK, it opens in a tab anyways, but I can seen an issue that if Firefox isn't already started, starting separate links will probably make Firefox open them up in separate windows.
I just tried an experiment. If I just type (say) linkblog for LinkBlog.lnk in the command line, it won't execute the link (I need to use the .lnk extension). But if I use start linkblog, then start does indeed start the link. An interesting finding. Permanent link posted by bytehead @ 2/15/2006 03:06:00 PM
0 comments
Links to this post
