Closed GoogleCodeExporter closed 9 years ago
Original comment by tortoisesvn
on 17 Feb 2009 at 7:07
Ah - this makes more sense now than for grepWin :)
But are you aware that pressing backspace (not delete!) in explorer should do
exactly
that?
Original comment by tortoisesvn
on 17 Feb 2009 at 7:40
Actually, the delete button in explorer is "Back" and will navigate to the
previous
directory, not the parent directory (unless that is where you just were). I
know you
can also click on a folder in the path bar, but this also becomes cumbersome
when you
have long/deep paths. The "up" button worked so well in previous versions of
windows
and I am not sure why they would not make it at least customizable in Vista so
it can
be added back.
Original comment by oldgra...@gmail.com
on 17 Feb 2009 at 7:53
Right, that's just for "Back" - for me that's usually "up". I guess I just
browse
differently :)
Original comment by tortoisesvn
on 17 Feb 2009 at 8:05
Original comment by tortoisesvn
on 2 May 2009 at 7:32
Marking as "wontfix" since this already is implemented in explorer: just hit
Alt-Up
instead of backspace.
(that's the "alt" key and the "cursor up" key together).
Original comment by tortoisesvn
on 2 May 2009 at 7:35
Please rethink your decision again. For most Vista users, it is very
inconvenient to
change from mouse to keyboard only for switching to an upper folder. btw: the
Vista
feature by clicking on the address bar is not very useful because folder names
are
often too long.
Thanks a lot!
Original comment by thomassc...@gmail.com
on 18 Jun 2009 at 11:20
Problem solved :)
Original comment by thomassc...@gmail.com
on 19 Jun 2009 at 12:26
Attachments:
could you also provide the sourcecode or a script only instead of an exe file?
Not many people are willing to download and execute such files.
Original comment by tortoisesvn
on 19 Jun 2009 at 5:16
of cause no problem:
it is not difficult at all. only these command:
"Send, {ALTDOWN}{UP}{ALTUP}"
Original comment by thomassc...@gmail.com
on 21 Jun 2009 at 6:24
Attachments:
Original issue reported on code.google.com by
oldgra...@gmail.com
on 17 Feb 2009 at 7:02