Suggestion: Start in last opened dirs only if they are local
Moderators: white, Hacker, petermad, Stefan2
Suggestion: Start in last opened dirs only if they are local
Hi all,
the idea of opening up the TC with thw two shells starting where they where when the TC was last closed is great ! I love it, but not when I've closed the TC with one of the shells (or both) showing a drive/directory on another machine, and then open TC with that machine turned off.
I would really like it if it was possible to set up the TC to only go to the last positions if they are local, just as an option of course.
take care all
hatecaps
[mod]
I have changed the thread title to make it more meaningful.
Lefteous (Moderator) [/mod]
the idea of opening up the TC with thw two shells starting where they where when the TC was last closed is great ! I love it, but not when I've closed the TC with one of the shells (or both) showing a drive/directory on another machine, and then open TC with that machine turned off.
I would really like it if it was possible to set up the TC to only go to the last positions if they are local, just as an option of course.
take care all
hatecaps
[mod]
I have changed the thread title to make it more meaningful.
Lefteous (Moderator) [/mod]
- SanskritFritz
- Power Member
- Posts: 3693
- Joined: 2003-07-24, 09:25 UTC
- Location: Budapest, Hungary
It's for compatibility reasons. There are many plugins etc. who search for wincmd.ini. If there is the name changed all author had to update their plugins. Or the plugins would not work further.hatecaps wrote: (and why isn't it called totalcmd.ini now ?)
2Raymond
The noreread option is for speed reasons implemented. If TC starts with a network drive in one pane while this drive is momentarily not available it takes few minutes sometimes before Windows reports it to TC. Until that very moment TC is frozen. To prevent this there is the noreread feature - TC does not try to connect to drives that mentioned here. The' \' stands for the whole network - although it is described as 'network neighbourhood' in TC help. So each path beginning with \\server\netshare is simply not opened in the window, even if its explicit saved, but instead the C:\ drive.
If you have opened the 'network neighbourhood' in one pane there's no speed problem at all.
So if you don't like to open the 'Network neighbourhood' at start there is a workaround:
Open some different directories in both windows.
Press [Alt]+[o] for configuration and then [v] for save settings.
Then disable 'directories' in Configuration->Options->Operation:Save on exit.
This way next time TC will open the directories you've saved with 'save settings' at start
sheepdog
"A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
This way would lose the feature that at startup I will be in the place last time I were. I only specifically want to avoid "Network Neightbourhood".Sheepdog wrote:So if you don't like to open the 'Network neighbourhood' at start there is a workaround:
Open some different directories in both windows.
Press [Alt]+[o] for configuration and then [v] for save settings.
Then disable 'directories' in Configuration->Options->Operation:Save on exit.
This way next time TC will open the directories you've saved with 'save settings' at start
Pity. If you set in wincmd.iniRaymond wrote:This way would lose the feature that at startup I will be in the place last time I were. I only specifically want to avoid "Network Neightbourhood".
Code: Select all
[configuration]
allowed=abcdefghijklmnopqrstuvwxyz
So I have no idea to get the desired behaviour.
sheepdog
"A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams