Trying it again now, I cannot get the results I thought to have seen when
using profile switches. (So maybe, didn't even kill the cat. Instead turned
my back from even observing cat's state too quickly, in haste to write
results down in the lab logbook.) So might be best erase what I said about
profiles.
All sorts of weird complexities, in the working with just the simple
switches.
Works fine:
mozilla.exe -nosplash -edit
mozilla.exe -nopslash -browser
Works fine:
mozilla.exe -nosplash -edit "d:\somefile.htm"
mozilla.exe -nopslash -browser "d:\somefile.htm"
Now the rules as I have always seen them in every other damn case in the
world, it says I can use a placeholder for that file.
mozilla.exe -nosplash -edit "%1"
mozilla.exe -nopslash -browser "%1"
Yet, when I drop a file onto the above shortcuts, or use sendto to hand them
the file, things fall apart. Mozilla accepts the document, but ignores all
and any of those commandline switches.
That is totally strange, and I can't come up with any clue at all why this
broken result.
Edit the file type, .html, or whatever.
Add a new action, "Edit", or modify an exisisting edit action.
Now. As to using sendto, or using the context menu, I am continuously
promoting and demoting programs between the two places. I use the same
string for either one. Since the same string works for either one, I'd
think the same string that fails would fail equally in both places.
Yet, here things get weirder yet. This does in fact work in the exmplorer
context menu:
mozilla.exe -nosplash -edit "%1"
That breaks down all the laws of gravity etc for me. Why it would work
there, and not the other place.
Oh, but not done yet. The other one in explorer context menu, it explodes,
falls all apart.
mozilla.exe -nosplash -browser "%1"
Mozilla gets lost, unable to do anything, and says to me: "d is not a
registered protocol." D is the drive letter where the file that I handed
it was located. All of a sudden, with the same command that works normally
(eg mozilla.exe -browser file.htm OR mozilla.exe -browser
www.site.com),
Mozilla expects that the argument be preceded by protocol type (eg file://
or
http://)
So I submit. I change the explore action to this:
mozilla.exe -nosplash -browser "file://%1"
What do I get? Mozilla now takes the file, loads it. In a kiosk mode! Full
screen, no menus of any kind. I didn't say anything to about it about kiosk!
I have never witnessed such a bizarre web of inconsistencies. In something
that is normally basically simple: putting an open command in various
places.
Except this. I am right now trying to remember what GUI programs I've set
up in sendto, which supported various extra commandline parameters, as does
Mozilla. I'm having trouble, at least offhand, comming up with examples.
The times I usually hand a string of switches, it in a batch. So no I've
typed a .bat file that has this line:
mozilla.exe -nosplash -edit %1 %2 %3 %4 %5 %6 %7 %8 %9
I put a .pif shortcut to that bat in my sendto. And it seems to work. Send
an htm there and mozilla opens it in composer mode.
Next, I try the same approach with the -browser switch. Same mess as when
the explorer context menu. Expects to be told what protocol. And that told
the file protocol, I assume again I'd get that weird result of kiosk mode.
Tres complique!!! And my original post was about how straightforward and
simple this kind of thing is. That accursed lizard, it's inhuman.