dandv

The last thing from DNOSP to be matched :-)

1. Create a file "doc(test).txt". 2. Drop the LFN to the command line by pressing Ctrl+Alt+Enter 3. Under Win2K, if you launch "doc(test).txt" at the command prompt, the application associated with .TXT (e.g. notepad) will launch. However, in NDN you'll get an error from cmd.exe: 'doc' is not recognized as an internal or external command, operable program or batch file. It looks like NDN truncated the filename at the '('. 5. Not so fast. Move the file to a folder called "c:\my documents". 6. Drop to the command line the full-path LFN by pressing Ctrl+Alt+Shift+Enter: "C:\my documents\doc(test).txt" 7. Press Enter. The cmd.exe error will be 'C:\my' is not recognized as an internal or external command, operable program or batch file. So NDN didn't cut at the '(' but at the first space. 8. By the way, there is an inconsistency regarding LFN+Pathnames: Ctrl+Alt+Shift+Enter copies to the command line the LFN+path Ctrl+Alt+Shift+Insert copies to the clipboard the SHORTFN+SHORTpath. I would propose that the Win32 NDN move the LFN shortcuts to the simpler key combinations and keep the SFN ones (in case they are ever needed) to the longer key combination. The reason is simple: suppose you have a converter from filetype .ABC to filetype .XYZ. So you'll run converter my_long_filename.ABC my_long_filename.XYZ Now you'll have my_long_filename.ABC in the file panel so you'll drop it to the command line with Ctrl+Enter, which gets you the SFN: my_lon~1.ABC. This is still OK, because the converter will find the file anyway. For the destination file, my_long_filename.XYZ, the simplest way to avoid typing it by hand would be to Ctrl+Enter again the .ABC file and just change the extension. But, Ctrl+Enter will get you the SFN, so you'll end up with converter my_lon~1.ABC my_lon~1.XYZ , which is NOT what you want because you'll get my_lon~1.XYZ instead of my_long_filename.XYZ. So here's what I propose: Ctrl+Enter => LFN Ctrl+Shift+Enter => LongPath+LFN Ctrl+Alt+Enter => SFN Ctrl+Alt+Shift+Enter => ShortPath+SFN The same would go for copying to clipboard (just replace Enter with Insert). So basically, Shift toggles path output and Alt toggles SFN/LFN output. What do you think? By the way, with regard to your post about NDN not receiving sufficient attention, if we decide to make changes, let's make the while NDN still has a small user base, so only few people will need to adapt.

Hi AH! I think I found a way to solve the "doc(test).txt" problem. So, 1. If in the NDN command line you type "doc(test).txt" you'll get an error about "doc" not being recognized. 2. If in a cmd.exe command prompt you type the same thing, "doc(test).txt" will be launched (not recognized) but no truncation due to '('. 3. If in NDN you double the quotes, i.e. ""doc(test).txt"", step 2. will happen. Does that help? Dan

When NDN copies a whole directory and one file happens to not be readable (assume the most fatal hardware error, like unplugging the network cable or scratched CD), NDN will generate a <<"Hardware failure on drive X:" (12)>> message (which is wrong by itself if we were copying from a \\network\path, but that's another story). What would be very useful is for NDN NOT to stop on such an error but offer the option to SKIP copying the file (and keep/delete the portion already copied to destination). Even more useful, this option should be settable in the copy dialog box, before the copying begins. So, one wants to copy as much as possible from a damaged CD. They select all directories on the CD, press F5, select the option to "Skip unreadable files" and "Delete partial copies", and press Enter. After the copying is done, they can compare directories (with a Branch - Ctrl+H first) and re-attempt to copy the missing files. What do you think?

1. In the current directory, have subfolders a\b and an archive a\b\arch.zip 2. From the current directory, search for a file in the arch.zip archive, with "Search in archives" checked 3. When NDN finds the file, press Enter on it. You'll be taken inside the ZIP archive 4. Press Enter on the '..' entry in the archive. 5. Instead of taking you to the folder of the archive, with the cursor over the archive, NDN takes you back to the Find: panel 6. If you press Enter over '..' again, you'll be taken to the current directory. This practically makes finding files in archives impossible (well, you can look at the path of the file in the Find panel, but that's not the point). Hope (fixing) that helps, Dan Dascalescu

Shift+Enter would be great! Indeed, the current approach can be viewed as better than DNOSP's, where if you press Enter on an archive, the Find results are gone.

It would be great if you could do a bunch of replaces with a macro, and I see a 'Replace' command at the end of the NDN.HGL file. What is the syntax for this command? I tried Replace string1 string2 but only the replace dialog showed up.

This is a Windows command shell bug: if you activate "delayed environment variable expansion" (http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/set.mspx), any ! or ^ characters in batch files will be stripped (unless they do expand an environment variable)

1. Enter an archive 2. F3 on a file. NDN will extract it using the current settings for the archiver 2. Exit the viewer, F3 the file again. NDN will extract it using the DEFAULT settings. I noticed that for ZIP, where I have as unpacker pkzipc.exe, and NDN launched PKUNZIP.EXE, which was not in PATH. If you re-enter the archive, NDN uses the correct settings. This applies to any two or more operations, not just two extractions. Hope that helps, Dan Dascalescu

1. Ctrl+Insert on a file inside a folder inside an archive copies to the Clipboard the entire path, \Folder\File, which Ctrl+Shit+Insert does the same. (in a normal directory, this works as expected) 2. Shift+F1 on a file in the active panel with an open archive in the passive panel adds the file to the passive archive instead of adding to a new archive in the active panel. Hope that helps, Dan Dascalescu

Hi AH! Great beta! I'm especially happy about the archive handling improvements and about the timer (Alt+/)! The bug: Ctrl+F5 doesn't work on the viewer window if in hex mode: on a file, F3, F4, Ctrl+F5. While in disassembler, Ctrl+F5 does something, in hex and dump views it appears to do nothing. Hope that helps, Dan Dascalescu

That's pretty confusing... can you provide a list of steps to follow, as I do in my bug reports? Anyway, try closing the edited file, removing it from the File Edit History (Alt+PgUp) and editing again. Hope that helps, Dan Dascalescu

1. Add the following NDN.HGL definition: FILES *.bug Keywords1 \n END 2. Create a file 'ndn.bug' and type "line1\n line2". Notice NDN not highlighting '\n'. It only highlights \n if you insert a non-alphanumeric character before '\' Hope that helps, Dan Dascalescu

1. Add the following NDN.HGL definition: FILES *.bug GeneralFlags 1 RegKeywords COLOR Red [A-Z]+ END 2. Create a file "ndn.bug" and type words in lowercase only. Notice NDN highlighting them in red. Hope that helps, Dan Dascalescu

I frequently find myself wanting to change directory in DNOSP to a directory of a filename in clipboard. So I type 'cd ', paste the complete path of the file from the clipboard, delete the filename, then press Enter. If I don't delete the filename, the CD command (when interpreted by DNOSP) won't work. NDN nicely handles this case and actually CDs to only the path, not to the filename, instead of doing nothing! That really helps me!

Almost all the time, I create archives in the same directory as the files from which I make up the archive, while the passive panel displays a totally different directory. If one wants to create an archive in the passive panel from files in the active panel, they can simply select the files, press F5 and insert "rar:" or "zip:" or "whatever_archiver:" before the path displayed in the Copy dialog. Alternatively, they could copy the path of the current directory and paste it in the "Archive files" dialog. So I'd rather have the archive created in the current directory. If the majority decides to create it in the passive panel, NDN can highlight only the path from the target archive name (now it highlights the entire ame), so that with a single "Del", the user can delete the path and create the archive in the same directory. Hope that helps, Dan Dascalescu

Sorry for replying to myself, but I found the archiver I was looking for: WinRAR! (not to mention the better compression rate than PkBloatWare's PkZIPc) Here are the settings: And by the way, tell PkWare and InfoZip to go shoot themselves.

Basil, these settings do not work correctly with Pkzipc 4.00 because the option "directories" causes a file to be added from all the directories it exists in. Example: in "c:\temp", you have "a.txt" and subfolder "sub", containing another "a.txt". Press Shift+F1 on the "c:\temp\a.txt". With the options you mentioned above for pkzipc 4.00 (and probably other versions as well), you'll get a zip containing two "a.txt" files. Can anyone recommend a ZIP archiver that: - supports LFNs, including LFNs with spaces - supports @ list files - supports passwords - does not have the problem mentioned above? Thanks, Dan

Just wanted to let you know that for a critical application, NDN's editor proved a life-saver: When editing .RTF files, spaces at the end of the line are important because they appear verbatim in the .RTF if you open it in Word (RTFs have a line length limit of 255 characters). Since DNOSP automatically deletes spaces at the end of the line, you'll end up with concatenatedwords in the .RTF. NDN's Editor option "Del right spaces" can be turned off, so you get a "clean" editor, preserving important spaces in .RTF. Well done!

1. Press Alt+/ twice to get the {} timing prompt (btw what does the [] mode do?) 2. Type "notepad somefile.txt" 3. After one second, close Notepad 4. Notice the spurious elapsed time recorded by NDN. Check video at http://home.arcor.de/stasis/NDNtimerBug.gif Hope that helps, Dan Dascalescu

In Win32, autocompletion can be enabling by setting CompletionChar to '9' in [HKEY_Current_User\Software\Microsoft\Command Processor] "CompletionChar"="9" It would be lovely if NDN allowed Tab autocompletion in the Ctrl+O Output window, for: - files/paths (you can use Ctrl+Enter to drop the file, but only if it's in a panel) - executables in the PATH (more useful; e.g. I have tools called 'xliffanalysis' and I'd rather not rename them; NDN.EXT is a solution but not flexible enough when it comes to piping/indirection, which the command line allows) What do you think?

I know there's no connection between NDN and the shell; I was suggesting is that when in the Output window you type "c:\ut" and press Tab, NDN will fill in "c:\utils\". Now you add 'p' and you get "c:\utils\p". Each time you press Tab again, it will fill in the files in c:\utils\ starting with 'p': c:\utils\pkunzip.exe etc. Support for executables in the PATH might be more difficult to do. I.e. if c:\utils\ is in the PATH, NDN could autocomplete "pkunzip" when you type 'p', Tab.

1. Shift+F4, empty.txt, F2 2. Notice the file was not created, probably because NDN found no changes to save to it. Could this special case be processed intuitively, that is, by creating the 0-byte file?

1. Create an archive out of one file 2. In the right panel, enter the archive 3. From the left panel, copy one file to the archive 4. After the archiver finishes running, notice that NDN did NOT update the archive's contents! (you have to press Ctrl+R) You might even think the archiver did not execute or it failed. Hope that helps, Dan Dascalescu

Suppose you need to append a bunch of files into one big file. You select the files, press F5, enter the destination file name, choose the "Append to all existing files" option and press OK. After some time, you just need to copy a file over another file. But surprise, you get no overwrite prompt! What happened is that NDN silently appended to the target file and now you have to cut out the start of the (possibly binary) file in order to recover your source file. If there are no file markers and you don't remember the size, you're gonna have a difficult job. This behavior is inherited from DNOPS, and I'd like to post this poll and ask for your opinion: Should NDN always start with the safe "Ask for overwrite" option or remember the previous option, like "Append to all existing files" ?