all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juang Dse <juangdse@gmail.com>
Cc: 46794@debbugs.gnu.org
Subject: bug#46794: 28.0.50; octave-mode: parse error in debug mode
Date: Sun, 19 Jun 2022 16:01:57 +0200	[thread overview]
Message-ID: <87a6a8vjje.fsf@gnus.org> (raw)
In-Reply-To: <CAGEcx2SN6CCLQScJ-xyR0yGd5k-v9eckynMSWHSsAKHPSVpW0A@mail.gmail.com> (Juang Dse's message of "Fri, 26 Feb 2021 14:26:47 +0100")

Juang Dse <juangdse@gmail.com> writes:

> Suppose the file
> -------------------
> # hoo.m
> function hoo ()
>    for j = 1 : 10
>       y(j) = j ;
>    endfor
> endfunction
> -------------------
> is in the search path (e.g. same directory). Then execute
> dbstop hoo
> hoo() ;
>
> from within emacs (octave-send-line twice), and in the file hoo.m mark
> the region of the for-loop, followed by octave-send-region. The
> following error is thrown:
>
> debug> debug> debug>    for j = 1 : 10
>       y(j) = j ;
>    endfor
>
>> > debug> error: parse error:
>
>   syntax error
>
>>>>    endfor
>             ^

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

I'm not very familiar with Octave mode, but if I understand correctly,
the complaint here is that if you've entered debugging mode in the
inferior Octave buffer, then you can't use octave-send-region
successfully until you've exited debugging mode again?

I'm not sure whether that's as it should be or not -- anybody else
familiar with Octave?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-06-19 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 13:26 bug#46794: 28.0.50; octave-mode: parse error in debug mode Juang Dse
2022-06-19 14:01 ` Lars Ingebrigtsen [this message]
2023-05-31  9:35 ` Juang Dse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6a8vjje.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=46794@debbugs.gnu.org \
    --cc=juangdse@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.