APLwrap doesn't actually interpret the wire protocol beyond looking for
'error' in the first line. Additional lines, up to but not including the
terminating sentinel, are simply collected and displayed.
On Mon, 2014-10-06 at 11:32 +0800, Elias Mårtenson wrote:
> That's a display issue. ☺ I'm sure
Well, it should. :-)
It returns the error message and line number in separate fields. The Emacs
mode uses it to highlight the line that has the error.
Regards,
Elias
On 7 October 2014 01:02, David B. Lamkins wrote:
> APLwrap doesn't actually interpret the wire protocol beyond looking for
> 'er
Did I? I guess it's a matter of interpretation. Emacs uses origin-1 for
line numbers, while APL uses origin-0.
Clearly it makes sense to maintain the Emacs sense of line numbers.
It's still proper to commit the fix (with the +1) since otherwise
gnu-apl-mode will be wrong in the case where APL run
I try not to make incompatible changes. I would love to completely redesign
it at some point but for now you can consider that part stable. If I need
to redesign that part I'll probably simply implement a new command.
Regards,
Elias
On 7 Oct 2014 01:11, "David B. Lamkins" wrote:
> Did I? I guess
Changed and pushed.
Blake, don't commit any syntax errors in origin-0 until you get the
libemacs update. ;)
On Tue, 2014-10-07 at 01:18 +0800, Elias Mårtenson wrote:
> I try not to make incompatible changes. I would love to completely
> redesign it at some point but for now you can consider that
gcc -DHAVE_CONFIG_H -I. -I..
-DMANUALS_PATH=\"/usr/local/share/doc/aplwrap\" -std=c99 -Wall -Werror
-pthread -I/usr/include/gtk-3.0 -I/usr/include/atk-1.0
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/pango-1.0
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo
-I/usr/include/gdk-pixbuf-2.0 -I/usr
