[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49707] Windows 10 won't associate .m files wi
|
From: |
John Donoghue |
|
Subject: |
[Octave-bug-tracker] [bug #49707] Windows 10 won't associate .m files with Octave after re-install |
|
Date: |
Sun, 27 Nov 2016 00:16:03 +0000 (UTC) |
|
User-agent: |
Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 |
Follow-up Comment #1, bug #49707 (project octave):
Just to ensure that it is not Windows becoming confused with install and
install of application, have you checked the association after rebooting
Windows?
If it is still not working, can you check the value of the following registry
values:
HKEY_CURRENT_MACHINE\.m
The value of it should be Octave.Document.XXXXXXX
where XXXXX is the octave version.
There should also be a correctponding registry entry of
HKEY_CURRENT_MACHINE\Octave.Document.XXXXXX
that should have a key in it of 'shell\open\command" and a value that will be
something similar to:
wscript "OCTAVE_INSTALL_DIR\octave.vbs" --force-gui --persist --eval "edit
'%1'"
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49707>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/