Cool. Thanks for the report.
I rarely invoke aplwrap from a shell window (I usually use GNOME's
Alt-F2 launcher), so I tend to miss chatter sent to the terminal.
On Fri, 2014-09-12 at 15:18 -0500, Blake McBride wrote:
> Works for me now without errors. Thanks to all!!
>
> On Fri, Sep 12, 2014
I suspect it might have something to do with timing.
The window's "destroy" signal invokes aplwrap_quit(), which then
terminates the APL process.
The termination of the APL process invokes (due to the
g_child_watch_add() call) apl_exit(), which then tries to terminate the
APL process.
I suspect
Works for me now without errors. Thanks to all!!
On Fri, Sep 12, 2014 at 2:30 PM, Chris Moller wrote:
> I just applied and pushed David's patch, the question remaining why it
> showed up only in some environments and not others.
>
>
> On 09/12/14 15:04, David B. Lamkins wrote:
>
> I believe I'
I just applied and pushed David's patch, the question remaining why it
showed up only in some environments and not others.
On 09/12/14 15:04, David B. Lamkins wrote:
I believe I've found the cause of this problem.
There's something special (I don't know what) about the exit behavior of
GTK+ in
Thanks a lot, David!!
Blake
On Fri, Sep 12, 2014 at 2:04 PM, David B. Lamkins
wrote:
> I believe I've found the cause of this problem.
>
> There's something special (I don't know what) about the exit behavior of
> GTK+ in the case that there's something on the application's clipboard.
> With no
I believe I've found the cause of this problem.
There's something special (I don't know what) about the exit behavior of
GTK+ in the case that there's something on the application's clipboard.
With nothing on the clipboard, application exit was fine. With something
on the clipboard, aplwrap's apl
Good idea. I'll give that a try tonight.
On Fri, 2014-09-12 at 12:55 -0400, Chris Moller wrote:
> Can you run it under valgrind? That should find memory problems.
>
>
> On 09/12/14 12:51, David B. Lamkins wrote:
>
> > FWIW: commenting out the gtk_text_view_scroll_to_mark() call in
> > scroll_t
Can you run it under valgrind? That should find memory problems.
On 09/12/14 12:51, David B. Lamkins wrote:
FWIW: commenting out the gtk_text_view_scroll_to_mark() call in
scroll_to_cursor() does not affect the crash that I'm seeing (which is
different in its details from the crash that Blake
FWIW: commenting out the gtk_text_view_scroll_to_mark() call in
scroll_to_cursor() does not affect the crash that I'm seeing (which is
different in its details from the crash that Blake reported). I still
get a memory corruption report, though...
On Fri, 2014-09-12 at 09:46 -0700, David B. Lamkins
I reached similar conclusions. It seems that copy/paste tickles this
bug.
Copy, then paste, then evaluate, then click the close box: this is
enough to give me GTK+ errors and even stack dumps.
These are probably the important clues:
GLib-GObject-WARNING **: invalid unclassed pointer in cast to
'
The backspaces I use don't work, but attempting it causes the problem. I
am at git commit 5352f834aba8f8620dcbb4ab1aab3bb64aede4a4
Do you get the error there?
Thanks.
Blake
On Fri, Sep 12, 2014 at 11:24 AM, Chris Moller
wrote:
> No, I don't get get a failure, but as you pointed out in an e
No, I don't get get a failure, but as you pointed out in an earlier
post, the copied 'abc' is uneditable--and I just saw that David has
fixed that. I'll have that patch up in a couple of minutes.
Chris
On 09/12/14 11:47, Blake McBride wrote:
Here are the steps that reproduce the problem:
1.
Interestingly, the error shows on the console, and the aplwrap window
disappears BUT the aplwrap process is still running.
On Fri, Sep 12, 2014 at 10:47 AM, Blake McBride wrote:
> Here are the steps that reproduce the problem:
>
> 1. Execute aplwrap
>
> 2. Type the following:
>
>
Here are the steps that reproduce the problem:
1. Execute aplwrap
2. Type the following:
∇test
[1] abc
[2]
3. Highlight and COPY (^C) the 'abc'
4. Click on the end of the [2] line
5. PASTE (^V) the 'abc' (has no quotes)
6. Hit the backspace key 3 times
7. Hit the X in t
I am using vanilla LinuxMint 16. GTK comes with it. Upgrading to test is
sort of a big job that messes up auto-update. Let me see if I can get an
exact sequence to duplicate the problem instead. Is that okay?
On Fri, Sep 12, 2014 at 8:49 AM, Chris Moller wrote:
> Can you try putting in a ne
Can you try putting in a newer version? 3.8.7 is from November of last
year. They've done a lot of bug-fixing since then and it would be good
to know if the bug is on my end or in GTK.
On 09/12/14 09:40, Blake McBride wrote:
Looks like I am running 3.8.7
On Fri, Sep 12, 2014 at 8:25 AM,
Looks like I am running 3.8.7
On Fri, Sep 12, 2014 at 8:25 AM, Chris Moller wrote:
> What version of GTK are you using? I'm running 3.10.9 though in
> configure.ac I'm only checking for versions >= 3.0.12. There may be some
> incompatibility.
>
>
>
> On 09/12/14 08:39, Blake McBride wrote:
>
What version of GTK are you using? I'm running 3.10.9 though in
configure.ac I'm only checking for versions >= 3.0.12. There may be
some incompatibility.
On 09/12/14 08:39, Blake McBride wrote:
Greetings,
I was in the middle of editing a function using the regular
del-editor, I copied and
Greetings,
I was in the middle of editing a function using the regular del-editor, I
copied and pasted a line, I then exited aplwrap by clicking on the x in the
upper left hand corner of the screen without closing the function I was
editing. Aplwrap gave me:
(aplwrap:29325): Gtk-CRITICAL **: gtk
19 matches
Mail list logo
