|
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 19:21:21 +0000 (UTC) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586 |
Follow-up Comment #3, bug #49707 (project octave): Sorry that should have been HKEY_CLASSES_ROOT\.m and HKEY_CLASSES_ROOT\Octave.Document.4.2.0 Doing a fresh install on mine, for HKEY_CLASSES_ROOT\Octave.Document.4.2.0 it should be similar to: Octave.Document.4.2.0 - (default) GNU Octave script - Default Icon - (default) path to icon file - shell - open - command - (default) "C:\Octave\Octave-4.2.0\octave.vbs" --force-gui --persist --eval "edit '%1'" Mine is based on selecting "Install for all users" when running the installer. What option did you use in the install? Also, if you double click on a .m file, what happens? _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?49707> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |