This is still an issue. It is actually a lot worse now too. For example,
if I just arrow up and down, the window thinks the file is modified.
When arrowing up and down the line numbers sometimes go in the wrong
direction and then jump to some other number.
Thanks.
Blake
On Sun, Sep 21, 2014
Fixed and pushed.
Dear David,
Thanks a lot! Looks a lot better. I did find one small issue with it
though.
It displays the total number of lines. Nice. Problem is, it is one
greater than the number of lines. I suppose there is a way of looking at
it such that it is correct, but that logic only worked when the
I know. I thought about that.
I'm not convinced that adjusting the line count is the right answer. We
actually do have N lines numbered 0 to N-1.
I suppose we could display the largest line number rather than the number
of lines. Then you'd have to remember to add 1 to get the line count...
May
Dear David,
The problem is this: you open up a function with two lines (the header and
one line) but the counter at the bottom says 3. The first thing you think
is; what does that number represent? It is confusing.
If you edit a function with 200 lines (God help us), it would be nice to
know it
OK, I see. That's not quite the full fix, though. If you go to the last
line and start typing, the line count doesn't change.
Fixed and pushed.
On Fri, Oct 3, 2014 at 1:37 PM, Blake McBride wrote:
> Dear David,
>
> The problem is this: you open up a function with two lines (the header and
> on
I pushed an APLwrap update with file Open, Save and Save As functionality.
--
"The secret to creativity is knowing how to hide your sources."
Albert Einstein
http://soundcloud.com/davidlamkins
http://reverbnation.com/lamkins
http://reverbnation.com/lcw
http://lamkins-guitar.com/
http://lamki
