(
Jump to the original submission)
Sun 02 Dec 2012 12:43:04 AM UTC, comment #6:
I pushed the changeset
http://hg.savannah.gnu.org/hgweb/octave/rev/cd3d7f126190
|
Mon 19 Nov 2012 03:17:07 PM UTC, comment #5:
Attached is a patch for this bug.
(file #26933)
|
Mon 19 Nov 2012 12:26:11 PM UTC, comment #4:
It should have been a zero in the first instance and a one in the second. It probably got garbled by the markup system.
Sorry.
|
Mon 19 Nov 2012 12:22:26 PM UTC, comment #3:
On the forwarded mail I read 0 in the first case, 1 in the second. On the bug report web page I read 1. and 1 repsectively. Which one should I trust?
Anyway I will make changes in copyobj to reflect those expected behaviors, and submit a patch here.
|
Mon 19 Nov 2012 08:35:13 AM UTC, comment #2:
ML gives
- in the first case
1 in the second.
|
Mon 19 Nov 2012 08:24:28 AM UTC, comment #1:
Thank you for testing.
It looks like in ML the current axes is reset to its previous value when the copy is made in the same figure. I will change that.
What if the copy is made inside a new figure? Can someone test this in ML :
And what about copying figures :
|
Thu 15 Nov 2012 01:08:40 PM UTC, original submission:
Here one would expect T = 'foo' (as in ML). What one gets, however, is the empty string.
|
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach File(s):
Comment:
Depends on the following items: None found
Items that depend on this one: None found
Follow 5 latest changes.