[Octave-bug-tracker] [bug #44402] spurious undo button

[Torsten]

Follow-up Comment #10, bug #44402 (project octave):

> The "new" and "open" are only used on text editor and already appear on the
editor widget.

The editor might be hidden, tabbed under another widget, or a custom editor is
in use. In these cases the buttons in the main window are quite useful.

> The copy, and paste buttons are like the undo buttons. They already appear
on the editor for that use, and would be of little use on the command line.

These buttons are for all widgets. Moreover, while the use of the "undo"
action is really limited to the current input line, it might be useful to copy
some output from the terminal window.

> The current directory does the same as the bar on the file browser

Yes and no. The file browser can be synchronized with the octave directory. In
this case both combo boxes show the same directory. In the other case, both
directories can be used independantly or browsing files outside the current
octave directory.

> May actually be a good idea to add a "browse directories" button next to the
"One directory up" button on the File browser widget actually

The button is in the drop-down menu next tot he "up" button due to less
space.

> This tab widget can float but can't be closed like the others so it will
take up valuable space whether the user wants it or not.

I will check if the tool bar can be made closeable.

> The shortcuts for the command line are provided by readline and it seems to
me that the GUI is capturing them. I just tried to define a few shortcuts on
.inputrc and they all worked fine without gui. With the gui, they failed when
they clashed

There is a preference for disabling the shortcuts of the gui in order to avoid
conflicts with readline.

> The control-z shortcut is not a very good on the command line since without
the GUI sends the process to the background.

The default shortcut for undo (and other actions) is the one that Qt provides
as default for the target platform.

> We already a quite powerful library to control what happens at the prompt,
and fully configurable.

I agree with you but I doubt that many users who are working with non-*ix
systems are used to readline or .inputrc files.

    _______________________________________________________

Reply to this item at:

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

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