Stack exchange: Octve

[J Stasko]

Since it has been brought up...

I despise stack exchange.  I relish this mailing list.  I wish I could
block google from sending me answers from stack exchange.

I distrust stack exchange.  I suspect they will soon charge to view
its compendium of information.  It will become as academic publishing,
with guilds and extreme amounts of money changing hands.  I find their
system oppressive.

Aren't we using open software here?

How else do they make money to keep their servers open?

2012/4/10  <address@hidden>:
> Send Help-octave mailing list submissions to
>       address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://mailman.cae.wisc.edu/listinfo/help-octave
> 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 Help-octave digest..."
>
>
> Today's Topics:
>
>   1. Re: edit error (Jordi Guti?rrez Hermoso)
>   2. Re: edit error (Michael Goffioul)
>   3. Re: edit error (Jordi Guti?rrez Hermoso)
>   4. Re: edit error (Michael Goffioul)
>   5. Undefined mat2gray (Olli Alatalo)
>   6. Re: Undefined mat2gray (Jordi Guti?rrez Hermoso)
>   7. Stack Exchange: Octve (JuanPi)
>   8. Re: Undefined mat2gray (Andy Buckle)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 10 Apr 2012 10:30:13 -0400
> From: Jordi Guti?rrez Hermoso <address@hidden>
> To: Miikka Tulonen <address@hidden>
> Cc: address@hidden
> Subject: Re: edit error
> Message-ID:
>        <address@hidden>
> Content-Type: text/plain; charset=UTF-8
>
> On 8 April 2012 14:54, Miikka Tulonen <address@hidden> wrote:
>> Old 3.2.0 opened the editor without problems so I was slightly annoyed by
>> this sort of BS with the newer versions. In my case fiddling with the
>> Octave?s startup script helped to solve the problem. (Took a whole day to
>> figure out this very simple fix)
>
> You don't need to modify edit.m to do this. Do you have an octaverc?
> That's where you can select your editor.
>
> I imagine Ben Lindner's old 3.2.4 Windows build set this variable for
> you, but we certainly don't set a default editor in Octave, and never
> did.
>
> - Jordi G. H.
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 10 Apr 2012 15:42:42 +0100
> From: Michael Goffioul <address@hidden>
> To: Jordi Guti?rrez Hermoso <address@hidden>
> Cc: address@hidden, Miikka Tulonen <address@hidden>
> Subject: Re: edit error
> Message-ID:
>        <address@hidden>
> Content-Type: text/plain; charset=windows-1252
>
> On Tue, Apr 10, 2012 at 3:30 PM, Jordi Guti?rrez Hermoso
> <address@hidden> wrote:
>> On 8 April 2012 14:54, Miikka Tulonen <address@hidden> wrote:
>>> Old 3.2.0 opened the editor without problems so I was slightly annoyed by
>>> this sort of BS with the newer versions. In my case fiddling with the
>>> Octave?s startup script helped to solve the problem. (Took a whole day to
>>> figure out this very simple fix)
>>
>> You don't need to modify edit.m to do this. Do you have an octaverc?
>> That's where you can select your editor.
>>
>> I imagine Ben Lindner's old 3.2.4 Windows build set this variable for
>> you, but we certainly don't set a default editor in Octave, and never
>> did.
>
> Actually, we sort of do. edit.m uses by default EDITOR, which defaults
> to emacs. So if you don't specify anything, octave uses emacs by
> default.
>
> The additional problem in edit.m is due to persistent variables. If
> edit.m is executed before changing EDITOR, then the default editor in
> edit.m is fixed to the EDITOR value at the time of the first call.
> Changing EDITOR afterwards doesn't have any effect. That's what
> confuses users, as the help for edit.m mentions that it uses EDITOR by
> default.
>
> Michael.
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 10 Apr 2012 10:46:39 -0400
> From: Jordi Guti?rrez Hermoso <address@hidden>
> To: Michael Goffioul <address@hidden>
> Cc: address@hidden, Miikka Tulonen <address@hidden>
> Subject: Re: edit error
> Message-ID:
>        <address@hidden>
> Content-Type: text/plain; charset=UTF-8
>
> 2012/4/10 Michael Goffioul <address@hidden>:
>> The additional problem in edit.m is due to persistent variables. If
>> edit.m is executed before changing EDITOR, then the default editor in
>> edit.m is fixed to the EDITOR value at the time of the first call.
>> Changing EDITOR afterwards doesn't have any effect. That's what
>> confuses users, as the help for edit.m mentions that it uses EDITOR by
>> default.
>
> Oh, that's problematic. Your patch or mine?
>
> - Jordi G. H.
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 10 Apr 2012 15:53:48 +0100
> From: Michael Goffioul <address@hidden>
> To: Jordi Guti?rrez Hermoso <address@hidden>
> Cc: address@hidden, Miikka Tulonen <address@hidden>
> Subject: Re: edit error
> Message-ID:
>        <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Tue, Apr 10, 2012 at 3:46 PM, Jordi Guti?rrez Hermoso
> <address@hidden> wrote:
>> 2012/4/10 Michael Goffioul <address@hidden>:
>>> The additional problem in edit.m is due to persistent variables. If
>>> edit.m is executed before changing EDITOR, then the default editor in
>>> edit.m is fixed to the EDITOR value at the time of the first call.
>>> Changing EDITOR afterwards doesn't have any effect. That's what
>>> confuses users, as the help for edit.m mentions that it uses EDITOR by
>>> default.
>>
>> Oh, that's problematic. Your patch or mine?
>
> Be my guest. I don't have time these days to work on octave.
>
> Michael.
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 10 Apr 2012 18:34:08 +0300
> From: Olli Alatalo <address@hidden>
> To: address@hidden
> Subject: Undefined mat2gray
> Message-ID:
>        <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I've got the following piece of code
>
> function A=noise(i, j)
> A=round(unifrnd(0,255,i,j));
> B=mat2gray(A);
> imshow(B);
> figure();
> imhist(B);
> figure();
> pause(4);
>
> when I run it, I receive an error:
>
> error: `mat2gray' undefined near line 3 column 3
>
>
> What? Why? How to fix?
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 10 Apr 2012 11:48:29 -0400
> From: Jordi Guti?rrez Hermoso <address@hidden>
> To: Olli Alatalo <address@hidden>
> Cc: address@hidden
> Subject: Re: Undefined mat2gray
> Message-ID:
>        <address@hidden>
> Content-Type: text/plain; charset=UTF-8
>
> On 10 April 2012 11:34, Olli Alatalo <address@hidden> wrote:
>> I've got the following piece of code
>>
>> function A=noise(i, j)
>> A=round(unifrnd(0,255,i,j));
>> B=mat2gray(A);
>> imshow(B);
>> figure();
>> imhist(B);
>> figure();
>> pause(4);
>>
>> when I run it, I receive an error:
>>
>> error: `mat2gray' undefined near line 3 column 3
>
> It's in the image package. Did you install it?
>
> HTH,
> - Jordi G. H.
>
>
> ------------------------------
>
> Message: 7
> Date: Tue, 10 Apr 2012 17:50:06 +0200
> From: JuanPi <address@hidden>
> To: address@hidden
> Subject: Stack Exchange: Octve
> Message-ID:
>        <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
> Computer science in StackExchange can be a good place to share
> solutions as well as all the other media you already use.
> http://scicomp.stackexchange.com/questions/tagged/octave
>
>
> --
> JuanPi Carbajal
> -----
> "The bad economist pursues a small present good, which will be
> followed by a great evil to come, while the true economist pursues a
> great good to come, at the risk of a small present evil." - Fr?d?ric
> Bastiat
> -----
> http://ailab.ifi.uzh.ch/carbajal/
>
>
> ------------------------------
>
> Message: 8
> Date: Tue, 10 Apr 2012 16:51:05 +0100
> From: Andy Buckle <address@hidden>
> To: Olli Alatalo <address@hidden>
> Cc: address@hidden
> Subject: Re: Undefined mat2gray
> Message-ID:
>        <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 10 April 2012 16:34, Olli Alatalo <address@hidden> wrote:
>> I've got the following piece of code
>>
>> function A=noise(i, j)
>> A=round(unifrnd(0,255,i,j));
>> B=mat2gray(A);
>> imshow(B);
>> figure();
>> imhist(B);
>> figure();
>> pause(4);
>>
>> when I run it, I receive an error:
>>
>> error: `mat2gray' undefined near line 3 column 3
>
> Looks like you are trying Matlab code in Octave. There is a mat2gray
> function in the image package, which might be compatible with
> Matlab's. Depending on what platform you are using.
>
> pkg install -forge image
>
> might solve your woes.
>
> --
> /* andy buckle */
>
>
> ------------------------------
>
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://mailman.cae.wisc.edu/listinfo/help-octave
>
>
> End of Help-octave Digest, Vol 73, Issue 32
> *******************************************