[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #39179] Warn or fall back to external editor i

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #39179] Warn or fall back to external editor if built without QScintilla
Date: Sun, 01 Feb 2015 16:35:40 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.91 Safari/537.36

Update of bug #39179 (project octave):

                Severity:              3 - Normal => 1 - Wish               
                Priority:              5 - Normal => 3 - Low                
              Item Group:        Incorrect Result => Feature Request        
                 Summary: octave_qt_link::do_edit_file always returns true
even when QScintilla not present => Warn or fall back to external editor if
built without QScintilla


Follow-up Comment #13:

I'm updating the description and goal of this dormant bug.

The current default branch still silently does nothing if the user tries to
"edit filename" from the command window in the GUI.

The GUI already has a facility for launching an external editor if the user's
preferences say so. The file_editor class checks the preference and opens the
file itself or launches the external program when it gets the
edit_file_signal. We do want to support this, so we can't just return false
from do_edit_file if we have no QScintilla.

If the GUI is built without QScintilla, there could either be some kind of
warning that the built-in editor can't be used, or it could automatically fall
back to forcing the external editor preference to be used by default.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]