Problems using latest build

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Problems using latest build

José Abílio Matos
Hi,
  when running the latest build, HG ID for this build is "39b4341c3376", I
noticed two problems:

1) Starting the editor (in --gui mode), typing a program, and the saving
(using the Ctr+S shortcut) results in a long delay (almost a minute). During
this period octave is frozen and the graphical interface does not react. This
is reproducible for me.


2) In the same script if I try to run it and the script has an error (in my
case I had a line "for ii in 1:N" -- wrong language, I know :-) ) the output
says:

parse error near line 12 of file /home/jamatos/tmp/inbox/test_subassgn.m

  syntax error

>>> N = 100;
            ^

The line number is right, but the line shown is the first line of the script
and not the place where the error occurs.

In this particular case octave 5.1.0 reports

parse error near line 12 of file /home/jamatos/tmp/inbox/test_subassgn.m

  syntax error

>>> for ii in 1:N
            ^

For what is worth this happens using Fedora 30.

Regards,
--
José Matos



Reply | Threaded
Open this post in threaded view
|

Re: Problems using latest build

Dmitri A. Sergatskov


On Sat, May 4, 2019 at 8:13 PM José Abílio Matos <[hidden email]> wrote:
Hi,
  when running the latest build, HG ID for this build is "39b4341c3376", I
noticed two problems:

1) Starting the editor (in --gui mode), typing a program, and the saving
(using the Ctr+S shortcut) results in a long delay (almost a minute). During
this period octave is frozen and the graphical interface does not react. This
is reproducible for me.


I cannot reproduce this problem.
Try to remove ~/.config/octave and start octave as
octave --gui -f

 

2) In the same script if I try to run it and the script has an error (in my
case I had a line "for ii in 1:N" -- wrong language, I know :-) ) the output
says:

parse error near line 12 of file /home/jamatos/tmp/inbox/test_subassgn.m

  syntax error

>>> N = 100;
            ^


I can reproduce this problem.


 
José Matos


Dmitri.
--
Reply | Threaded
Open this post in threaded view
|

Re: Problems using latest build

siko1056
On Sun, May 5, 2019 at 4:08 AM Dmitri A. Sergatskov <[hidden email]> wrote:

On Sat, May 4, 2019 at 8:13 PM José Abílio Matos <[hidden email]> wrote:
Hi,
  when running the latest build, HG ID for this build is "39b4341c3376", I
noticed two problems:

1) Starting the editor (in --gui mode), typing a program, and the saving
(using the Ctr+S shortcut) results in a long delay (almost a minute). During
this period octave is frozen and the graphical interface does not react. This
is reproducible for me.


I cannot reproduce this problem.
Try to remove ~/.config/octave and start octave as
octave --gui -f


@José Matos: Does the delay only occurs the first time saving this new file?  Or does the delay persists, each time you call "save as" or type CTRL+s?
Does this delay occur, if you UNcheck the preference > General > Use native file dialogs?

Then it might be a known bug: https://savannah.gnu.org/bugs/?56116 

Best,
Kai
Reply | Threaded
Open this post in threaded view
|

Re: Problems using latest build

José Abílio Matos
On Sunday, 5 May 2019 09.53.13 WEST Kai Torben Ohlhus wrote:
> On Sun, May 5, 2019 at 4:08 AM Dmitri A. Sergatskov <[hidden email]>
> >
> > I cannot reproduce this problem.
> > Try to remove ~/.config/octave and start octave as
> > octave --gui -f

Calling octave like this does not return any error or warning.
 

> @José Matos: Does the delay only occurs the first time saving this new
> file?  Or does the delay persists, each time you call "save as" or type
> CTRL+s?
> Does this delay occur, if you UNcheck the preference > General > Use native
> file dialogs?
>
> Then it might be a known bug: https://savannah.gnu.org/bugs/?56116
>
> Best,
> Kai

Thank you Kai. I think that is the problem. I am using kde like the bug
reporter.

On you request I found that the problem only occurs the first time. After that
long delay (~ 2 minutes waiting) any later calls to save shows the file dialog
immediately. :-)

FWIW I found another gotcha. When changing the preferences the way you
suggested, and just that knob, pressing Enter turns the command window fonts
into a gibberish look because in my case the proposed font for the Command
Window is CCIcons (?!). That was surprising. :-)

Best regards,
--
José Matos



Reply | Threaded
Open this post in threaded view
|

Re: Problems using latest build

siko1056


On Sun, May 5, 2019 at 11:42 AM José Abílio Matos <[hidden email]> wrote:
On Sunday, 5 May 2019 09.53.13 WEST Kai Torben Ohlhus wrote:

> Does this delay occur, if you UNcheck the preference > General > Use native
> file dialogs?
>
> Then it might be a known bug: https://savannah.gnu.org/bugs/?56116

Thank you Kai. I think that is the problem. I am using kde like the bug
reporter.

On you request I found that the problem only occurs the first time. After that
long delay (~ 2 minutes waiting) any later calls to save shows the file dialog
immediately. :-)

FWIW I found another gotcha. When changing the preferences the way you
suggested, and just that knob, pressing Enter turns the command window fonts
into a gibberish look because in my case the proposed font for the Command
Window is CCIcons (?!). That was surprising. :-)

Best regards,
--
José Matos


This is indeed pretty weird.  Does this also happen, if you freshly restart Octave?  Do you have any specific language settings for you KDE (fonts, ...) ?  Does this now always happen for each fresh Octave session, that you only see "gibberish" fonts?

Best,
Kai
Reply | Threaded
Open this post in threaded view
|

Re: Problems using latest build

José Abílio Matos
On Tuesday, 7 May 2019 21.13.34 WEST Kai Torben Ohlhus wrote:
> This is indeed pretty weird.  Does this also happen, if you freshly restart
> Octave?  Do you have any specific language settings for you KDE (fonts,
> ...) ?  Does this now always happen for each fresh Octave session, that you
> only see "gibberish" fonts?
>
> Best,
> Kai

Before changing the preferences I had a readable font (honestly I do not know
which).

When I changed the preference not to use the native file dialog (and I have
just changed that preference). Saving the preferences also changed the font
used for the command window.

The list of available fonts are all mono (typewriter) fonts. It happens that
in my case, for some reason that escapes me, I have the CCIcons font installed
and since the list is ordered alphabetically that font is picked when saving
the preferences even if I have not selected that font.

I called that "gibberish" fonts because I was taken by surprise. It was
clearly unexpected, at least for me.

I hope that this explanation makes sense. :-)

Best regards,
--
José Matos



Reply | Threaded
Open this post in threaded view
|

Re: Problems using latest build

siko1056
On Wed, May 8, 2019 at 8:15 AM José Abílio Matos <[hidden email]> wrote:
On Tuesday, 7 May 2019 21.13.34 WEST Kai Torben Ohlhus wrote:
> This is indeed pretty weird.  Does this also happen, if you freshly restart
> Octave?  Do you have any specific language settings for you KDE (fonts,
> ...) ?  Does this now always happen for each fresh Octave session, that you
> only see "gibberish" fonts?
>
> Best,
> Kai

Before changing the preferences I had a readable font (honestly I do not know
which).

When I changed the preference not to use the native file dialog (and I have
just changed that preference). Saving the preferences also changed the font
used for the command window.

The list of available fonts are all mono (typewriter) fonts. It happens that
in my case, for some reason that escapes me, I have the CCIcons font installed
and since the list is ordered alphabetically that font is picked when saving
the preferences even if I have not selected that font.

I called that "gibberish" fonts because I was taken by surprise. It was
clearly unexpected, at least for me.

I hope that this explanation makes sense. :-)

Best regards,
--
José Matos



Thank you for the detailed explanation.  If you now have the binary choice between saving in less than two minutes or reading text in the command line, I suggest to open a bug report about this [1]. To me it seems, that the current situation makes Octave unusable for you and maybe others using the same system.

Best,
Kai

Reply | Threaded
Open this post in threaded view
|

Re: Problems using latest build

José Abílio Matos
On Wednesday, 8 May 2019 07.41.36 WEST Kai Torben Ohlhus wrote:

> Thank you for the detailed explanation.  If you now have the binary choice
> between saving in less than two minutes or reading text in the command
> line, I suggest to open a bug report about this [1]. To me it seems, that
> the current situation makes Octave unusable for you and maybe others using
> the same system.
>
> Best,
> Kai
>
> [1] https://savannah.gnu.org/bugs/?func=additem&group=octave

Sure.

Where are the gui preferences saved?

Best regards,
--
José Matos



Reply | Threaded
Open this post in threaded view
|

Re: Problems using latest build

Torsten Lilge
On Wed, 2019-05-08 at 07:50 +0100, José Abílio Matos wrote:

> On Wednesday, 8 May 2019 07.41.36 WEST Kai Torben Ohlhus wrote:
> > Thank you for the detailed explanation.  If you now have the binary
> > choice
> > between saving in less than two minutes or reading text in the
> > command
> > line, I suggest to open a bug report about this [1]. To me it seems,
> > that
> > the current situation makes Octave unusable for you and maybe others
> > using
> > the same system.
> >
> > Best,
> > Kai
> >
> > [1] https://savannah.gnu.org/bugs/?func=additem&group=octave
>
> Sure.
>
> Where are the gui preferences saved?
>
> Best regards,

José, when using the default-branch, the prefs are stored in
~/.config/octave/octave-gui.ini

When you select another font in the prefs, is this font then used in the
terminal ans does the dialog still show CCIcons as the chosen font next
time you open the dialog?

Best,
Torsten


Reply | Threaded
Open this post in threaded view
|

Re: Problems using latest build

José Abílio Matos
In reply to this post by José Abílio Matos
On Wednesday, 8 May 2019 08.08.13 WEST Kai Torben Ohlhus wrote:
> It should be save in $HOME/.config/octave/.  Maybe you can try to remove all
> files there and create a fresh config.
>
> Best,
> Kai

Coming back to this issue, moving the files away and starting fresh I do not
have those issues anymore. So for the moment I will ignore this since I am not
able to reproduce or to get a minimal setup where this happens.

Thank you for your help. :-)
--
José Matos



Reply | Threaded
Open this post in threaded view
|

Re: Problems using latest build

José Abílio Matos
In reply to this post by Torsten Lilge
On Wednesday, 8 May 2019 18.24.47 WEST Torsten Lilge wrote:
> José, when using the default-branch, the prefs are stored in
> ~/.config/octave/octave-gui.ini
>
> When you select another font in the prefs, is this font then used in the
> terminal ans does the dialog still show CCIcons as the chosen font next
> time you open the dialog?

If I choose a different font tha option sticks. It only happened the first
time I made a change in the  preferences. It was almost as if I did not had a
font set in the preferences and the code default to the first available font
name...

Specifically I got into trouble when I saved the preferences for the first
time when I decided to use the native dialogs option because of the long delay
that I was having.

> Best,
> Torsten

Moving the preference files made this problem disappear and since I have not
been able to get a minimal example where this fails I will leave this problem
for now.

Thank you. :-)
--
José Matos