octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #41136] GUI Editor: should warn about incorrec


From: Julien Bect
Subject: [Octave-bug-tracker] [bug #41136] GUI Editor: should warn about incorrect file names
Date: Tue, 07 Jan 2014 15:40:43 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:26.0) Gecko/20100101 Firefox/26.0

URL:
  <http://savannah.gnu.org/bugs/?41136>

                 Summary: GUI Editor: should warn about incorrect file names
                 Project: GNU Octave
            Submitted by: jbect
            Submitted on: mar. 07 janv. 2014 15:40:42 GMT
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.8.0
        Operating System: GNU/Linux

    _______________________________________________________

Details:

A typical error for Octave novices is to create a script with spaces in its
name. It would be nice if the GUI could warn about such errors.

Let us consider a simple scenario.

1) Create a new script from the GUI (File > New > Script)

2) Put some stuff in it and save as "to to.m"

3) Run the script from the menu in the editor

After stage 2), nothing happens. A warning dialog would be useful here,
indicating that spaces in script names should be avoided (and perhaps that
this script can be run using run ("to to.m") anyway, if the user insists on
having spaces in its filename).

After stage 3), the editor itself doesn't tell me anything, and I can see the
following message in the command window:

error: 'to' undefined near line 1 column 1

It would clearer if, instead, an error dialog could pop up and tell me that
the script cannot be run because it has a space in its filename.
Alternatively, the editor could use run ("to to.m"), in which case there would
be no error.






    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/




reply via email to

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