search

gavioto / stexbar

Automatically exported from code.google.com/p/stexbar
0 stars 1 forks source link

Console button broken #92

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Press Console button
2.
3.

What is the expected output? What do you see instead?
Expected: Console windows opens pre-initialized to the path of the explorer
window.
Instead: Nothing happens at all.

What version of the product are you using? On what operating system?
1.7.0, currently I'm using this old version due to the toolbar layout bug
of 1.7.1.

Please provide any additional information below.
I only have this issue on work computer, on my home computer everything
works fine with version 1.7.0.

Original issue reported on code.google.com by christia...@gmail.com on 12 Oct 2009 at 3:11

GoogleCodeExporter commented 9 years ago 
I guess you're using XP? If however you're using Win7, then you either have to 
use
1.7.1 or wait for 1.7.2 (I'll create a release as soon as I have some time...)

Original comment by tortoisesvn on 12 Oct 2009 at 7:16

GoogleCodeExporter commented 9 years ago 
Sorry, forgot to add that. Yes I'm using Windows XP SP3 with IE8.

Original comment by christia...@gmail.com on 12 Oct 2009 at 7:21

GoogleCodeExporter commented 9 years ago 
try creating a new command:
name: test
command line: cmd /k dir

and then click on the new test button.
A console window should pop up and executing the 'dir' command. Maybe we can 
get some
information from that directory.

Original comment by tortoisesvn on 12 Oct 2009 at 7:49

GoogleCodeExporter commented 9 years ago 
Adding a custom command with just cmd.exe works. When invoking this command the
console comes up open in the current directory of the explorer window.

Original comment by christia...@gmail.com on 13 Oct 2009 at 8:33

GoogleCodeExporter commented 9 years ago 
Can you try version 1.7.2? Maybe this one works better.

Original comment by tortoisesvn on 13 Oct 2009 at 6:48

GoogleCodeExporter commented 9 years ago 
The problem still exists with 1.7.2.

Original comment by christia...@gmail.com on 14 Oct 2009 at 5:35

GoogleCodeExporter commented 9 years ago 
Check your environment variable "COMSPEC". If that variable is set, it must 
contain a
full and valid path to either the windows cmd.exe or a custom command line
interpreter to use.
If it doesn't, that would explain why it doesn't work for you.

Original comment by tortoisesvn on 14 Oct 2009 at 6:46

GoogleCodeExporter commented 9 years ago 
Yepp, that was it! Somehow COMSPEC wasn't set as a system level environment 
variable.
No idea how this got lost, I guess you never know what the IT department does 
on a
work laptop...

Thanks

Original comment by christia...@gmail.com on 15 Oct 2009 at 8:30

GoogleCodeExporter commented 9 years ago

Original comment by tortoisesvn on 15 Oct 2009 at 4:35