Re: Octave-maintainers Digest, Vol 120, Issue 73

[Jorge Alvarado]

Hi Raj,

Sure!

Thanks,

Jorge E. Alvarado
P: 787 426 1920
E: address@hidden

> On Mar 22, 2016, at 5:40 PM, address@hidden wrote:
> 
> Send Octave-maintainers mailing list submissions to
>    address@hidden
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    https://lists.gnu.org/mailman/listinfo/octave-maintainers
> or, via email, send a message with subject or body 'help' to
>    address@hidden
> 
> You can reach the person managing the list at
>    address@hidden
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Octave-maintainers digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: octave-4.0.1 strange echo (Keith Keith)
>   2. Re: octave-4.0.1 strange echo (Marco Atzeri)
>   3. Re: octave-4.0.1 strange echo (Marco Atzeri)
>   4. Re: strange echo (Rik)
>   5. Re: strange echo (Marco Atzeri)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 22 Mar 2016 16:23:13 -0400
> From: Keith Keith <address@hidden>
> To: Marco Atzeri <address@hidden>,    Octave Maintainers List
>    <address@hidden>
> Subject: Re: octave-4.0.1 strange echo
> Message-ID:
>    <address@hidden>
> Content-Type: text/plain; charset="utf-8"
> 
> On Tue, Mar 22, 2016 at 12:58 PM, Marco Atzeri <address@hidden>
> wrote:
> 
>> I just built from
>> ftp://ftp.gnu.org/gnu/octave/octave-4.0.1.tar.xz
>> 
>> plus adapted two 2 patches
>> http://hg.savannah.gnu.org/hgweb/octave/rev/8e5eca2c5a64
>> http://hg.savannah.gnu.org/hgweb/octave/rev/2ee20a290d61
>> 
>> and now i see a copy of
>> /usr/share/octave/4.0.1/m/startup/__finish__.m
>> any time I require a "echo on" and exit.
>> 
>> 
>> $ octave-cli --eval "echo on"
>> + ## Copyright (C) 2008-2015 Ben Abbott
>> + ##
>> + ## This file is part of Octave.
>> + ##
>> + ## Octave is free software; you can redistribute it and/or modify it
>> + ## under the terms of the GNU General Public License as published by
>> + ## the Free Software Foundation; either version 3 of the License, or (at
>> ....
>> + ## No test needed for internal helper m-file.
>> + ##!assert (1)
>> + endscript;
>> 
>> 
>> I doubt it is a an effect of the two patches, but could anyone
>> check on a clean octave-4.0.1 build ?
>> 
>> Thanks in advance
>> Marco
>> 
>> I get the same output on a fresh install.  I don't know whether it is the
> desired output or not, but that's what I got.
> 
> -Keith
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.gnu.org/archive/html/octave-maintainers/attachments/20160322/3a4308fd/attachment.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 22 Mar 2016 21:30:45 +0100
> From: Marco Atzeri <address@hidden>
> To: Keith Keith <address@hidden>,    Octave Maintainers List
>    <address@hidden>
> Subject: Re: octave-4.0.1 strange echo
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> 
> 
>> On 22/03/2016 21:23, Keith Keith wrote:
>> 
>>> On Tue, Mar 22, 2016 at 12:58 PM, Marco Atzeri  wrote:
>> 
>>    $ octave-cli --eval "echo on"
>>    + ## Copyright (C) 2008-2015 Ben Abbott
>>    + ##
>>    + ## This file is part of Octave.
>>    + ##
>>    + ## Octave is free software; you can redistribute it and/or modify it
>>    + ## under the terms of the GNU General Public License as published by
>>    + ## the Free Software Foundation; either version 3 of the License,
>>    or (at
>>    ....
>>    + ## No test needed for internal helper m-file.
>>    + ##!assert (1)
>>    + endscript;
>> 
>> 
>>    I doubt it is a an effect of the two patches, but could anyone
>>    check on a clean octave-4.0.1 build ?
>> 
>>    Thanks in advance
>>    Marco
>> 
>> I get the same output on a fresh install.  I don't know whether it is
>> the desired output or not, but that's what I got.
>> 
>> -Keith
> 
> I doubt is a desired output.
> 
> Thanks for the confirmation
> Marco
> 
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 22 Mar 2016 21:55:20 +0100
> From: Marco Atzeri <address@hidden>
> To: Octave Maintainers List <address@hidden>
> Subject: Re: octave-4.0.1 strange echo
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
>> On 22/03/2016 21:30, Marco Atzeri wrote:
>> 
>> 
>>> On 22/03/2016 21:23, Keith Keith wrote:
>>> 
>>>> On Tue, Mar 22, 2016 at 12:58 PM, Marco Atzeri  wrote:
>>> 
>>>    $ octave-cli --eval "echo on"
>>>    + ## Copyright (C) 2008-2015 Ben Abbott
>>>    + ##
>>>    + ## This file is part of Octave.
>>>    + ##
>>>    + ## Octave is free software; you can redistribute it and/or
>>> modify it
>>>    + ## under the terms of the GNU General Public License as
>>> published by
>>>    + ## the Free Software Foundation; either version 3 of the License,
>>>    or (at
>>>    ....
>>>    + ## No test needed for internal helper m-file.
>>>    + ##!assert (1)
>>>    + endscript;
>>> 
>>> 
>>>    I doubt it is a an effect of the two patches, but could anyone
>>>    check on a clean octave-4.0.1 build ?
>>> 
>>>    Thanks in advance
>>>    Marco
>>> 
>>> I get the same output on a fresh install.  I don't know whether it is
>>> the desired output or not, but that's what I got.
>>> 
>>> -Keith
>> 
>> I doubt is a desired output.
>> 
>> Thanks for the confirmation
>> Marco
> 
> 
> It seems a side effect of
> ---------------------------------------
> 2015-09-03  Rik  <address@hidden>
> 
>        __finish__.m: Change from function to script to stay in base 
> workspace (bug #45869).
> 
>        * __finish__.m: Remove function declaration changing it to a script.
>        Update docstring.
> 
>        Files: scripts/startup/__finish__.m
> ------------------------------------------
> 
> The simple workaround is to add "echo off" as last command
> to disable the "echo on" before __finish__.m is executed.
> 
> Regards
> Marco
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Tue, 22 Mar 2016 14:17:28 -0700
> From: Rik <address@hidden>
> To: address@hidden
> Subject: Re: strange echo
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="windows-1252"
> 
>> On 03/22/2016 12:16 PM, address@hidden wrote:
>> Subject: > octave-4.0.1 strange echo > From: > Marco Atzeri
> <address@hidden> > Date: > 03/22/2016 09:58 AM > To: > Octave
> Maintainers List <address@hidden> > List-Post: >
> <mailto:address@hidden> > Content-Transfer-Encoding: > 7bit >
> Precedence: > list > MIME-Version: > 1.0 > Message-ID: >
> <address@hidden> > Content-Type: > text/plain; charset=utf-8;
> format=flowed > Message: > 2 > > I just built from >
> ftp://ftp.gnu.org/gnu/octave/octave-4.0.1.tar.xz > > plus adapted two 2
> patches > http://hg.savannah.gnu.org/hgweb/octave/rev/8e5eca2c5a64 >
> http://hg.savannah.gnu.org/hgweb/octave/rev/2ee20a290d61 > > and now i see
> a copy of > /usr/share/octave/4.0.1/m/startup/__finish__.m > any time I
> require a "echo on" and exit. > > > $ octave-cli --eval "echo on" > + ##
> Copyright (C) 2008-2015 Ben Abbott > + ## > + ## This file is part of
> Octave. > + ## > + ## Octave is free software; you can redistribute it
> and/or modify it > + ## under the terms of the GNU General Public License
> as published by > + ## the Free Software Foundation; either version 3 of
> the License, or (at > .... > + ## No test needed for internal helper
> m-file. > + ##!assert (1) > + endscript; > > > I doubt it is a an effect of
> the two patches, but could anyone > check on a clean octave-4.0.1 build ?
> 
> This is expected.  'echo on' turns on echo for scripts, but not functions. 
> The __finish__.m *script* is set to be executed at the end of every Octave
> session so that any commands the user has in finish.m will be executed
> (e.g., saving the workspace, etc.).
> 
> The explanation for why __finish__.m is a script, rather than a function,
> is in the code itself.
> 
> -- __finish__.m --
> ## No function declaration, this is is an Octave script.  This means we are
> ## still in the base workspace with access to all user variables.
> 
> if (exist ("finish", "file"))
>  finish;  # No arg list here since finish might be a script.
> endif
> -- End Code --
> 
> This seems like a corner case, but if it is really a problem then we could
> switch to evalin.
> 
> -- New Code --
> function __finish__ ()
> 
>  if (exist ("finish", "file"))
>    ## No arg list for finish because it might be a script.
>    evalin ("base", "finish;");
>  endif
> 
> endfunction
> -- End Code --
> 
> I checked and this seems to do the right thing.
> 
> --Rik
> 
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.gnu.org/archive/html/octave-maintainers/attachments/20160322/71cd978a/attachment.html>
> 
> ------------------------------
> 
> Message: 5
> Date: Tue, 22 Mar 2016 22:40:27 +0100
> From: Marco Atzeri <address@hidden>
> To: address@hidden
> Subject: Re: strange echo
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=windows-1252; format=flowed
> 
>> On 22/03/2016 22:17, Rik wrote:
>> 
>> This is expected.  'echo on' turns on echo for scripts, but not
>> functions.  The __finish__.m *script* is set to be executed at the end
>> of every Octave session so that any commands the user has in finish.m
>> will be executed (e.g., saving the workspace, etc.).
> 
> I noted.
> 
>> 
>> This seems like a corner case, but if it is really a problem then we
>> could switch to evalin.
> 
> I will just add a echo off at the end of my script
> 
> 
>> 
>> --Rik
> 
> Regards
> Marco
> 
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Octave-maintainers mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/octave-maintainers
> 
> 
> End of Octave-maintainers Digest, Vol 120, Issue 73
> ***************************************************