Control not returned to command line when opening file.

Erland Sommarskog · Post by **Erland Sommarskog** » Tue Oct 07, 2003 8:07 pm

This may be related to the issue with double-clicking on files in Explorer,
which according to Helios had its origin in a bug in VS .Net 2003.

Let's say that I have associated .txt with TextPad. If I'm in a command-line window say "charlie.txt" and in the current directory
there is a file with this name, it opens in TextPad. That works in all
versions, including 4.7.1. What is different in 4.7.1 in difference to
4.6.2 is that with 4.6.2 I got a new command prompt in my command-
line window, whereas with 4.7.1 I don't get any command prompt
until I close TextPad. It does not matter whether TextPad was already
running when I opened the file.

The workaround is fairly simple: "textpad charlie.txt" works as
before.

talleyrand · Post by **talleyrand** » Tue Oct 07, 2003 8:18 pm

Bizarre, I'm unable to reproduce your findings.

W2K, SP4, VS .Net, TP 4.7.1
TextPad is associated with .tex files
F:\latex>resume.long.tex
TextPad either pops up if no instance runing or opens document in current instance. Either time control is returned to the command prompt

Erland Sommarskog · Post by **Erland Sommarskog** » Thu Oct 09, 2003 6:54 pm

Then I bet you have set up the associations for .TEX to not use DDE. When I type slask.txt from the command line on my home machine,
control is returned to the command line. This is the one association,
where I don't have DDE. As you may recall, not using DDE was the
working around in 4.7.0 for the double-clicking problem.

I should add tha tthis happens on three machines that I have. One running Win 2K SP4, and the other two Win XP SP1.

talleyrand · Post by **talleyrand** » Thu Oct 09, 2003 9:55 pm

I could be mistaken, but it looks like DDE is enabled on my association.

Erland Sommarskog · Post by **Erland Sommarskog** » Fri Oct 10, 2003 8:22 pm

Mysterious. Some other setting is apparently involved too.