I do not know what was the intention about functionality of the newly added feature in 4.6:
7. Add open relative file path from command line feature.
It is clear, however, that is has spoiled the original command line behaviour that is our main mode of operation. If I type a command line like this:
notepad++ foobar.txt
the program will try to find the foobar.txt file in the folder where the notepad++.exe file is placed, rather than in the current folder which would be the "naturally expected" behaviour :-(
Will you please comment on this?
G, 16:55 dark time
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, this works. But anyway, what is the rationale behind changing the the behaviour? I do not think that storing the data files in the notepad's++ folder might have any sense. What is the situation where this new feature will make life easier?
Regards,
V, 13:05 Sunny Time Again :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Don,
I do not know what was the intention about functionality of the newly added feature in 4.6:
7. Add open relative file path from command line feature.
It is clear, however, that is has spoiled the original command line behaviour that is our main mode of operation. If I type a command line like this:
notepad++ foobar.txt
the program will try to find the foobar.txt file in the folder where the notepad++.exe file is placed, rather than in the current folder which would be the "naturally expected" behaviour :-(
Will you please comment on this?
G, 16:55 dark time
Don,
Yes, this works. But anyway, what is the rationale behind changing the the behaviour? I do not think that storing the data files in the notepad's++ folder might have any sense. What is the situation where this new feature will make life easier?
Regards,
V, 13:05 Sunny Time Again :-)
Try
notepad++ ./foobar.txt
Don