Re: [Matlab-emacs-discuss] org mode: execute matlab code and insert it, the matlab shell, matlab live editor, jupiter notebook

[Uwe B. <ou...@ma...>]

>>> "Eric" == Eric Ludlam <Eri...@ma...> writes:

Hi Eric
   > Hi Uwe,

Thanks for your answer.
   > I did see this on the list the first time, and I spent a little
   > time on it. I was surprised to see the result from using
   > matlab-shell-collect-command-output cropping as you suggested.
   > There are a few filters for things like errors, anchors, and other
   > misc text to hide that I played with, but I found nothing that
   > matched \end at that time so I didn't end up replying as I hadn't
   > found anything. There may be something else with the special MATLAB
   > end keyword I missed. Process filters are a challenge to debug,
   > particularly when there is both the matlab filter plus the gud
   > filter interacting which I'm just not that familiar with anymore.

   > If you start in gud-matlab-marker-filter, you can see some of the
   > stuff it filters, such as escape codes, error, opentoline, etc.
   > Anyway, I didn't see anything there.

   > matlab-shell-collect-command-output perhaps could cheat, and
   > disable the process filter near the loop that accepts process
   > output. For example:

   > (condition-case nil
   >      (set-process-filter (get-buffer-process (current-buffer))
   > 			      nil)
   >      ;; loop is here
   >   (error nil))
   > (set-process-filter (get-buffer-process (current-buffer))
   > 			      'gud-filter)

Do you suggest, that I should give this modification a try?


Meanwhile I got  the python jupyther client, matlab kernel 
and emacs ob-ipython to work.


This is much faster than John's solution but slower than the emacs lisp
shell!!


   > but that's a pretty big hammer. I guess it would tell us if the
   > filter is the problem. If it is in this loop, there may be an issue
   > in prompt detection. The bit that cuts out the string to return is
   > pretty simple. Perhaps it is being confused by newlines or
   > something.

Maybe in my vacation I will play around a bit. There seems not much
interest in the matlab list nor in the org mailing list about this issue
though.

Regards

Uwe