Fixed Starting editor from VIEW

Aug 20, 2012
7
0
There is a bug in how VIEW handles starting the configured editor: It passes the original file path+name that was used to open VIEW, but with the working directory set to the directory containing the file:

Code:
C:\Data> VIEW subdir\file.txt

shows the contents of file.txt. If I then press Ctrl+E or select File|Edit, my editor starts up and tries to open C:\Data\subdir\subdir\file.txt.
 
It passes the original file path+name that was used to open VIEW, but with the working directory set to the directory containing the file

In the Editor/CMD section of the VIEW Preferences, specify %f as the Editor Options. This should force VIEW to use the full path. Does this fix the problem?
 
May 20, 2008
11,400
99
Syracuse, NY, USA
In the Editor/CMD section of the VIEW Preferences, specify %f as the Editor Options. This should force VIEW to use the full path. Does this fix the problem?
The help says:
Code:
F    The selected file name(s) - includes fully qualified path
 
f    File name only (no path)

Please clarify. When I start VIEW this way
Code:
v:\> view ip2c\ip2c.btm
and ask to edit the file with %F as the editor option, my editor (TextPad) asks if it's OK to create "V:\ip2c\ip2c\ip2c.btm". So it would seem we don't want VIEW to use full paths.

And when I start VIEW with multiple file names, there is very little indication that there are two files open (a couple of toolbar icons activated). Is there a way to get a greater indication that there are more than one file open? And when there are more than one file open, File\Close terminates VIEW, just like File\CloseAll does. Given that the two menu items exist, I'd expect "Close" to close only one file.
 
Aug 20, 2012
7
0
Same here. With %f, it works because only the actual file name is passed. The behavior with %F is the same as without any option, so I think the "full path" that %F is supposed to produce does not refer to "the absolute file system path", but instead to "the full path as originally passed to VIEW". Same with %D, which is not the fully qualified path to the current directory, but instead the directory portion of whatever VIEW was started with.
 
With %f, it works because only the actual file name is passed.

You are right - %f happens to work by good fortune and not by design. %f and %F should work as stated in the Help file.

I will fix the bug in the next VIEW update.


And when I start VIEW with multiple file names, there is very little indication that there are two files open
Is there a way to get a greater indication that there are more than one file open?

In a word, no.

Given that the two menu items exist, I'd expect "Close" to close only one file

You should be able to implement this behavior as follows:

1. Enable View Next File in the Keyboard section of Preferences
2. Enable Closing File Window to behave like pressing ESC key in the File Options section

Selecting Close from the File menu should now take you to the next file - just like pressing ESC.

However, there is a bug which is stopping this from working. I will fix this too in the next update.
 
May 20, 2008
11,400
99
Syracuse, NY, USA
Charles, I purchased "V" in 2010 (May?) and since had a big crash. I moved to Windows 7 and though "V" still sits on my "Apps" drive and I have access to the old registry and the "Prineas" key, I can't find registration info. And I can't find reg info among my thousands of emails. If you have records confirming this, could you supply me with new registration info?
 
May 20, 2008
11,400
99
Syracuse, NY, USA
I sent an email to the address I had on file for you.

If you haven't received it, send me an email at v at fileviewer.com.
Yes, I got it this morning, quite promptly, but I didn't have time to respond. So ... thanks!

And, as it is, Esc will take me to the next file. But it doesn't cycle back to the first after the last. Is (should there be) a way to do that (or a way to go to the previous file).
 
Similar threads
Thread starter Title Forum Replies Date
C How to? starting TCC/TCMD v25 Support 2
samintz Starting Terminal from TakeCommand Support 3
vefatica Starting *.xlsm? Support 34
Steve Pitts _TCTAB when first starting Take Command Support 2
vefatica Starting Office apps Support 8
W Starting program for word to pdf conversion (difference cmd and tcc) Support 13
vefatica Starting Office 365 apps? Support 3
D WAD STARTing WUP apps Support 1
D Occasional TCMD 17 crash when starting additional TCC Support 4
D Folders pane display problem when starting Support 4
samintz Fixed DO /L with stringset starting with /n /e Support 2
M Starting Windows GUI programs from the command line... Support 10
ehab aboudaya WAD starting tcmd.exe with dir that has Boost C++ Libraries zip file delays Support 2
vefatica Starting shell objects Support 6
C starting TC/LE on the command line Support 1
C starting a shortcut from desktop Support 14
J starting in chosen directory Support 4
C starting tcmd with alternate INI file Support 15
F unexpected %1 while starting ide Support 6
T Starting a process blocks TCC window... Support 2
T Problem Starting Vim & gVIM Support 5
millardjk IDE dies without starting Support 4
S Starting TCC with double click on tab bar Support 0
Phileosophos LIST edit not invoking my specified editor Support 4
J Console editor for TCC12 Support 10
B Bdebugger / IDE editor doesn't display called batch file Support 1
T VIEW only works from command line Support 14
vefatica VIEW ... remember the UTF-8 setting? Support 0
Alpengreis Documentation Minor issue in help file for view /E Support 1
vefatica VIEW wrap searches? Support 2
R Documentation Help Nit > bdebugger View Menu Support 0
Joe Caverly Why does TCCRT return VIEW as an internal command? Support 6
Joe Caverly Pipe into VIEW and search Support 12
vefatica VIEW ... CommandPrompt ... TC21 ... unregistered Support 6
vefatica Start VIEW with the toolbar showing? Support 5
rps How to? Piping to View /gb Support 1
vefatica VIEW ... remember no toolbar Support 0
E Fixed View command broken in version 21.0 build 22 Support 9
vefatica File Explorer ... remember view settings? Support 5
vefatica "View" settings still not remembered Support 10
vefatica TCMD ... remember View settings? Support 7
C View Print Wrap - please break at whitespace Support 3
C VIEW PRINT /Wrap doesn't work Support 0
C VIEW PRINT - Documentation corrected - Font size Support 8
C WAD VIEW print multiple files - switches fail Support 10
MickeyF TCC v16 crashes when I hit F1 to view help Support 9
R V19 - 'V' and 'View" Support 6
cgunhouse Crash on View/Folder Support 1
M View doesn't recognize Ctrl+End and Ctrl+Pos1 Support 2
vefatica Speaking of VIEW Support 18

Similar threads