[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51321] end keyword used as index disrupts cod
From: |
Marshall |
Subject: |
[Octave-bug-tracker] [bug #51321] end keyword used as index disrupts code folding |
Date: |
Mon, 26 Jun 2017 19:09:26 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0 |
URL:
<http://savannah.gnu.org/bugs/?51321>
Summary: end keyword used as index disrupts code folding
Project: GNU Octave
Submitted by: marsian
Submitted on: Mon 26 Jun 2017 11:09:25 PM UTC
Category: GUI
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Assigned to: None
Originator Name: Marsian
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.2.1
Operating System: Microsoft Windows
_______________________________________________________
Details:
The 'end' keyword breaks proper code folding when used as an index to an
array:
a = 1:5;
if true
a(1:2)+=3;
a(3:end)-=3; %code fold matched with if
b = a;
for i=1:3
b+=1;
if false
b=3;
b = a(end); %code fold matched with if
q = b;
endif
a = 1;
endfor
c+3;
endif
a = 1:5;
if true
a(1:2)+=3;
endif
Each 'end' used as an index will be matched improperly with the prior control
statement, and won't be collapsed completely. Surrounding and following lines
are shown to match to the wrong end statements, or for the last 'if' doesn't
show any match lines, but still folds.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51321>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #51321] end keyword used as index disrupts code folding,
Marshall <=