[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57208] comment lines typed at command line ar
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #57208] comment lines typed at command line are no longer ended with a newline |
Date: |
Mon, 11 Nov 2019 16:11:22 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko |
URL:
<https://savannah.gnu.org/bugs/?57208>
Summary: comment lines typed at command line are no longer
ended with a newline
Project: GNU Octave
Submitted by: rik5
Submitted on: Mon 11 Nov 2019 01:11:20 PM PST
Category: Interpreter
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Regression
Status: Confirmed
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Any
_______________________________________________________
Details:
Comment lines typed at the command line are no longer terminated with a
newline. Instead, they shift the parser in to multi-line mode.
Sample session:
octave:5> ## A comment line
> sin (5)
octave:5> sin (5)
ans = -0.9589
octave:6> diary off
You can see that after the newline following the comment line the parser
shifts to multi-line mode because the prompt changes. When the second line is
ended with a newline, nothing is executed which is shown by the fact that
there is no output 'ans' and the command number is not incremented from 5. On
the other hand, just typing "sin (5)" does exactly what you expect in that it
produces an answer and increments the command number.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57208>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #57208] comment lines typed at command line are no longer ended with a newline,
Rik <=