help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help-octave Digest, Vol 154, Issue 45


From: vempati Sarma
Subject: Re: Help-octave Digest, Vol 154, Issue 45
Date: Sat, 26 Jan 2019 18:54:30 +0530



On Sat, Jan 26, 2019 at 6:39 PM <address@hidden> wrote:
Send Help-octave mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.gnu.org/mailman/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: 'syms' command (Nicholas Jankowski)
   2. help on functions (vempati Sarma)
   3. Re: help on functions (Andrew Janke)
   4. Calling Octave built in functions from C, not C++
      (Allan Branscomb)
   5. Re: Calling Octave built in functions from C, not C++
      (Carlo De Falco)
   6. Re: Calling Octave built in functions from C, not C++
      (Andreas Weber)
   7. Re: help on functions (Nicholas Jankowski)


----------------------------------------------------------------------

Message: 1
Date: Fri, 25 Jan 2019 18:49:37 -0500
From: Nicholas Jankowski <address@hidden>
To: Colin Macdonald <address@hidden>
Cc: Help GNU Octave <address@hidden>
Subject: Re: 'syms' command
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 25, 2019 at 5:44 PM Colin Macdonald <address@hidden> wrote:
>
> On 2019-01-25 12:08 p.m., Nicholas Jankowski wrote:
> >
> > straight from the CLI works.
>
> Ok we're slowly converging on step-by-step instructions...
>
> I assume this means "cmd.exe" (not Octave command line).  But what is
> this called for non-technical Windows users?
>
> 1.  Click on the start menu,
> 2.  Open <???>  ("command line", "command prompt", "cmd.exe"?)
> 3.  Type "pip install sympy".
>
> Colin
>

I updated the wiki with detailed instructions covering those. Let me
know if the current steps aren't sufficiently detailed.



------------------------------

Message: 2
Date: Sat, 26 Jan 2019 10:02:12 +0530
From: vempati Sarma <address@hidden>
To: address@hidden
Subject: help on functions
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset="utf-8"

Hi,
I am using Octave 4.4.0(GUI) on Windows 10 OS. I am trying to get help on
command line about some functions, only last portion
of help text is displayed, if it has size more than window . Vertical
navigation key is not helping in getting top portion of help text. Since,
some of the functions do not have documentation I am unable to read the
help text.
Is there any work around to navigate to see earlier portion of command
window?


--
Best Regards,
vsrk sarma
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/help-octave/attachments/20190126/8747db96/attachment.html>

------------------------------

Message: 3
Date: Sat, 26 Jan 2019 01:37:48 -0500
From: Andrew Janke <address@hidden>
To: address@hidden
Cc: address@hidden
Subject: Re: help on functions
Message-ID: <address@hidden>
Content-Type: text/plain; charset=utf-8; format=flowed



On 1/25/19 11:32 PM, vempati Sarma wrote:
> Hi,
> I am using Octave 4.4.0(GUI) on Windows 10 OS. I am trying to get help
> on command line about some functions, only last portion
> of help text is displayed, if it has size more than window . Vertical
> navigation key is not helping in getting top portion of help text.

Does the scroll bar work?

> Since, some of the functions do not have documentation I am unable to
> read the help text.
> Is there any work around to navigate to see earlier portion of command
> window?

You can use "doc <function>" instead of "help <function>" to view
function documentation in a separate documentation browser

> --
> Best Regards,
> vsrk sarma

Cheers,
Andrew



------------------------------

Message: 4
Date: Fri, 25 Jan 2019 18:29:52 -0800
From: Allan Branscomb <address@hidden>
To: address@hidden, Allan <address@hidden>
Subject: Calling Octave built in functions from C, not C++
Message-ID: <address@hidden>
Content-Type: text/plain; charset=utf-8; format=flowed

Hello;

Searching the Octave user manual, the email archives, and the Web, I can
find examples in which Octave built-in functions are called from C++ but
none from C.

There is mention that it can be done but I haven't been able to find any
examples in which C is the calling language.

The task is to call the polyfit and polyval functions from a C
function.  I've implemented this from C to Matlab but don't see how it
is done with Octave.

I want to call these functions directly, without use of the Octave
interpreter.  I found a discussion on the Web in which it is stated that
built-in functions can be called without use of the interpreter and for
performance reasons would prefer this approach if possible.

Thanks for your help;
Allan






------------------------------

Message: 5
Date: Sat, 26 Jan 2019 11:02:56 +0000
From: Carlo De Falco <address@hidden>
To: "address@hidden" <address@hidden>
Cc: "address@hidden" <address@hidden>
Subject: Re: Calling Octave built in functions from C, not C++
Message-ID: <address@hidden>
Content-Type: text/plain; charset="us-ascii"



> On 26 Jan 2019, at 03:29, Allan Branscomb <address@hidden> wrote:
>
> There is mention that it can be done but I haven't been able to find any examples in which C is the calling language.

Where did you find mention of that? builtin functions are declared as :

extern OCTINTERP_API octave_value_list
Fnorm (const octave_value_list& = octave_value_list (), int = 0);

and "octave_value_list" is definitely not a C compatible type ...

c.


------------------------------

Message: 6
Date: Sat, 26 Jan 2019 12:10:27 +0100
From: Andreas Weber <address@hidden>
To: address@hidden, address@hidden
Subject: Re: Calling Octave built in functions from C, not C++
Message-ID: <address@hidden>
Content-Type: text/plain; charset=utf-8; format=flowed

Am 26.01.19 um 03:29 schrieb Allan Branscomb:
> The task is to call the polyfit and polyval functions from a C
> function ... I want to call these functions directly, without use of the Octave
> interpreter.

Have you had a look how these functions are implemented in GNU Octave?
You won't be able to run these without interpreter.

I think the best option for you is to pick one of the many C libraries
which can do that, for example GSL - GNU Scientific Library

-- Andy



------------------------------

Message: 7
Date: Sat, 26 Jan 2019 08:08:53 -0500
From: Nicholas Jankowski <address@hidden>
To: vempati Sarma <address@hidden>
Cc: Help GNU Octave <address@hidden>
Subject: Re: help on functions
Message-ID:
        <CABNpfR-Bf=address@hidden>
Content-Type: text/plain; charset="utf-8"

On Fri, Jan 25, 2019, 23:32 vempati Sarma <address@hidden wrote:

> ...
> Is there any work around to navigate to see earlier portion of command
> window?
>

in addition to the scroll bar and doc browser,  you can turn on the "pager"
function which will paginate long text output like help text.  You can turn
this feature on and off using

more on

And

more off

You should see navigation prompts at the bottom for "(f)orward (b)ack
(q)uit"
Thank you, Nicholas. This hint is useful and I am able to see help text part by part. 

also, be warned that I believe there were issues in older versions of
Octave on windows with noticeable delays in output using the pager,
although I don't think that has been reported in some time.

>


>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/help-octave/attachments/20190126/f301b93e/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
Help-octave mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/help-octave


------------------------------

End of Help-octave Digest, Vol 154, Issue 45
********************************************


--
Best Regards,
vsrk sarma

reply via email to

[Prev in Thread] Current Thread [Next in Thread]