bugGNU Octave - Bugs: bug #60091, Editor disabled in Octave 6.2.0

 
 

bug #60091: Editor disabled in Octave 6.2.0

Submitter:  None
Submitted:  Sun 21 Feb 2021 10:01:17 PM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Other
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  Peter Fonon Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * other
Operating System:  * GNU/Linux Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sun 28 Feb 2021 05:55:24 PM UTC, comment #20: 

Thank you all for your help. Your comments helped to fix the Octave bug in PCLinunOS.

Peter Fonon <fonon>
Fri 26 Feb 2021 12:11:32 PM UTC, comment #19: 

I'm not exactly sure if I understood your question correctly.
But if the Octave you are using had been built with QScintilla, ` _octave_config_info_.build_features.QSCINTILLA` would have returned 1.

This doesn't look like a bug in Octave atm. But more like a packaging issue in downstream PCLinuxOS.

Closing report.

If it should turn out there is an issue in Octave's build scripts or you need more information, please post a new comment here.

Markus Mützel <mmuetzel>
Group administrator
Fri 26 Feb 2021 07:28:14 AM UTC, comment #18: 


comment #17:

> Something wrong with the build from the PCLinuxOS developers as it was built without qscintilla - either because it wasnt installed when built, or wasnt detected correctly.
>
> The fix is either PCLinuxOS rebuilds it with qscintilla enabled  or you compile your own working version.
>
>

Thank you for answer. What are correct values of the test?

Peter Fonon <fonon>
Fri 26 Feb 2021 01:54:38 AM UTC, comment #17: 

Something wrong with the build from the PCLinuxOS developers as it was built without qscintilla - either because it wasnt installed when built, or wasnt detected correctly.

The fix is either PCLinuxOS rebuilds it with qscintilla enabled  or you compile your own working version.


John Donoghue <lostbard>
Group Member
Thu 25 Feb 2021 09:40:36 PM UTC, comment #16: 

comment #12:

> The previous post removed the double'__' so again:
>


> __octave_config_info__.build_features.QSCINTILLA
>
> __octave_config_info__.build_features.Q5
>
> __octave_config_info__.build_features.Q4


>


>> _octave_config_info_.build_features.QSCINTILLA

ans = 0

>> _octave_config_info_.build_features.QT5

ans = 1

>> _octave_config_info_.build_features.QT4

ans = 0

>>

Peter Fonon <fonon>
Thu 25 Feb 2021 05:35:32 PM UTC, comment #15: 

comment #9: It was not clear to me that you were referring to the menu entry.

Torsten Lilge <ttl>
Group Member
Thu 25 Feb 2021 03:15:09 PM UTC, comment #14: 

:) i would get it right finally - maybe

John Donoghue <lostbard>
Group Member
Thu 25 Feb 2021 03:01:55 PM UTC, comment #13: 

To avoid possible confusion. John probably meant:

__octave_config_info__.build_features.QSCINTILLA
__octave_config_info__.build_features.QT5
__octave_config_info__.build_features.QT4


Markus Mützel <mmuetzel>
Group administrator
Thu 25 Feb 2021 01:33:13 PM UTC, comment #12: 

The previous post removed the double'__' so again:


__octave_config_info__.build_features.QSCINTILLA

__octave_config_info__.build_features.Q5

__octave_config_info__.build_features.Q4


John Donoghue <lostbard>
Group Member
Thu 25 Feb 2021 01:32:09 PM UTC, comment #11: 

Chances are PCLinuxOS has build octave without the editor support.

What doe the following commands run in octave show:

_octave_config_info_.build_features.QSCINTILLA

_octave_config_info_.build_features.Q5

_octave_config_info_.build_features.Q4

John Donoghue <lostbard>
Group Member
Thu 25 Feb 2021 09:44:20 AM UTC, comment #10: 

I have not seen that there are Octave versions without an editor. All the versions I used, except the one which had the same bug, had a built-in editor. I have never intentionally used emacs.

Peter Fonon <fonon>
Thu 25 Feb 2021 09:37:55 AM UTC, comment #9: 


comment #8:

> Is the entry for the editor widget in the menu "Windows" of the main window disabled (grayed out)?
>

Yes, it is disabled (as I wrote in the first post).

Peter Fonon <fonon>
Thu 25 Feb 2021 06:44:01 AM UTC, comment #8: 

Is the entry for the editor widget in the menu "Windows" of the main window disabled (grayed out)?

Torsten Lilge <ttl>
Group Member
Wed 24 Feb 2021 08:58:35 PM UTC, comment #7: 

comment #6:

> How have you installed the new octave version. Is it a build with or without the internal editor? Have you used emacs int version 6.1.0 or the internal editor?


I'm using PCLinuxOS and Octave was installed via Synaptic from OS repository.
I don't know what version (with or without the internal editor) it is. I used only internal editor in 6.1.0 and previous versions. The same problem occurred once in past but I don't remember what version it was.

Peter Fonon <fonon>
Wed 24 Feb 2021 06:18:30 AM UTC, comment #6: 

How have you installed the new octave version. Is it a build with or without the internal editor? Have you used emacs int version 6.1.0 or the internal editor?

Torsten Lilge <ttl>
Group Member
Tue 23 Feb 2021 10:25:32 PM UTC, comment #5: 


comment #3:

> Do you have (possibly accidentally) enabled the custom editor resulting in the shown error message instead of opening the gui internal editor.


No, the problem occurred after Octave update.

> What happens when you hit the shortcut Ctrl+4?


Nothing.

Peter Fonon <fonon>
Tue 23 Feb 2021 10:21:23 PM UTC, comment #4: 


comment #2:

> Does it work if you call emacs directly with that command from within Octave?


> [r, s] = system("emacs +0 /home/gal/xcx.m")


Yes, it works. The new emacs window is open.

>
> You could also try using the built-in editor (if the Octave you are using was built with QScintilla). On the "Editor" tab of the preferences, check if you can disable the checkbox in front of "Use custom file editor".


The checkbox is disabled.

Peter Fonon <fonon>
Mon 22 Feb 2021 06:20:43 PM UTC, comment #3: 

Do you have (possibly accidentally) enabled the custom editor resulting in the shown error message instead of opening the gui internal editor. What happens when you hit the shortcut Ctrl+4?

Torsten Lilge <ttl>
Group Member
Mon 22 Feb 2021 06:54:18 AM UTC, comment #2: 

Does it work if you call emacs directly with that command from within Octave?

[r, s] = system("emacs +0 /home/gal/xcx.m")


You could also try using the built-in editor (if the Octave you are using was built with QScintilla). On the "Editor" tab of the preferences, check if you can disable the checkbox in front of "Use custom file editor".

Markus Mützel <mmuetzel>
Group administrator
Mon 22 Feb 2021 03:04:12 AM UTC, comment #1: 



Preview screenshot.

Kai Torben Ohlhus <siko1056>
Group Member
Sun 21 Feb 2021 10:01:17 PM UTC, original submission:  

The Editor window is disabled in 6.2.0. In 6.1.0 worked properly. PCLinuxOS

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #50903:  Screenshot_20210221_225424.jpg added by None (193KiB - image/jpeg)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by lostbard (Posted a comment)
  • -email is unavailable- added by fonon (Posted a comment)
  • -email is unavailable- added by ttl (Posted a comment)
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by siko1056 (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-02-26 mmuetzel StatusNeed Info Invalid / Not an Octave Bug
        Open/ClosedOpen Closed
    2021-02-22 mmuetzel StatusNone Need Info
    2021-02-21 None Attached File- Added Screenshot_20210221_225424.jpg, #50903

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code