[Octave-bug-tracker] [bug #49707] Windows 10 won't associate .m files with Octave after re-install

[Brandon Graham]

Follow-up Comment #2, bug #49707 (project octave):

Computer restart doesn't fix the problem.

Please forgive my limited knowledge of the Registry.
I can't find HKEY_CURRENT_MACHINE in the registry

In HKEY_CLASSES_ROOT/.m the value is Octave.Document.4.2.0
In HKEY_CLASSES_ROOT/Octave.Document.4.2.0 the value is GNU Octave Script
In HKEY_CLASSES_ROOT/Octave.Document.4.2.0/DefaultIcon is a path to the Octave
icon which seems correct although the icon doesn't show up on my .m files
right now.
There is a folder for HKEY_CLASSES_ROOT/Octave.Document.4.2.0/shell/open but
the value is not set. There is no "command" under the "open" folder

In HKEY_CURRENT_USER/Software/Classes/.m the value is Octave.Document.4.2.0.
There doesn't seem to be an Octave folder in there.

In HKEY_LOCAL_MACHINE/Software/Classes/ there is no ".m" directory, but there
is
HKEY_LOCAL_MACHINE/Software/Classes/Octave.Document.4.2.0/shell/open/command
which has a value of wscript "C:\Octave\Octave-4.2.0\octave.vbs" --force-gui
--persist --eval "edit '%1'"

Seems confusing that there are 3 places (at least that I know of from Google)
to store all of this stuff. I hope this info helps.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49707>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/