freenode/#clim - IRC Chatlog
Search
9:35:51
beach
loke: There is a special variable *active-history-type* that lets you filter the types that you get from the history with M-p.
9:36:18
beach
Perhaps if you restrict that type to exclude commands, it will do something closer to what you want.
9:45:56
loke
OK, as best as I can tell, *active-history-type* gets set to whatever the :HISTORY argument is set to
9:46:36
loke
The problem is that if I set it to 'MAXIMA-NATIVE-EXPR (or, in the test case, 'FOO-ARGUMENT) I don't get any history at all. Presumably because it's looking at the wrong history object?
9:48:03
loke
beach: Right, but where should I bind it? It's already bound in the ACCEPT method, so that would override the previous binding.
9:49:58
loke
Yes. Even if I bind that variable prior to calling ACCEPT, inside ACCEPT said varaible gets re-bound to whatever I passed as :HISTORY
9:52:44
beach
So, it seems natural that if you accept a particular type with ACCEPT, then that same time is what the history is scanned for.
9:52:53
loke
Did you try changing my test code? Speicfically, the :HISTORY argument in the READ-FRAME-COMMAND function. If you chaneg that from FOO-ARGUMENT-OR-COMMAND into FOO-ARGUMENT, then I get no history whatsoever.
9:53:30
beach
... therefore, the only solution appears to be to avoid that commands are entered onto the history in the first place.
9:54:12
loke
Unless there is actually a bug in the behaviour, but I'd be damned if I had any idea where that bug would be.
9:56:35
beach
Did you check whether not giving NIL as the default avoids getting the default for M-p?
9:57:35
beach
OK, I am off for a while. Got to tell the cleaning lady goodbye, then put everything back that she moved, then lunch, then rest. Back in a few hours at most.
9:59:12
loke
the NIL seems to be inserted at the point where I was in the history list when I typed th enew command.
15:03:43
beach
loke: I am tracing PRESENTATION-HISTORY-INSERT in both the listener and in your stripped-down application.
15:05:09
beach
Your stripped-down application does not increase the fill pointer when it inserts FOO, but only when it inserts NIL.
15:22:10
loke
beach: Did you also notice that both the NIL and the actial value gets inserted on each command?
15:23:19
beach
The return value of presentation-history-insert is the index of the inserted element.
15:26:13
beach
It appears that in the listener, the empty thing is not overwritten, but in your application, the NIL is overwritten.
15:26:35
loke
Remember how I said that I found it irritating that the index stayed where I was when I used M-p to find a previous command?
15:26:48
loke
Well, turns out that CLIM-Listener doesn't do that. The index is restored to the last element
15:29:32
beach
Another clue: in the listener, when I type M-p, I get the previous input, but not as a presentation. I think that must have something to do with the type that you assign to what you push on the history.
16:30:43
beach
I am thinking I can be more effective that way. Many people can write the same code I can write, but fewer people seem to write specifications, and fewer people have the knowledge that I have to help people out.
16:31:32
beach
I.e., I spend a lot of time writing specifications that will then never become implemented.
16:32:31
beach
jackdaniel: Plus, there are people working on some projects that I started, and who could use my help to make faster progress.
16:35:09
loke
ACTION just realised that my use of standard output records for rendering maths have a limitation.
16:35:44
loke
I typically render a subexpression to an output record, and then take its dimensions to detmine how to place it within the greater expression.
16:36:09
loke
The problem is that the output record dimensions are often larger than the actual graphical content
16:37:34
loke
I just noticed it when trying to render the ABS function (horizontal lines on each side of a subexpression). The spacing between expression and line is not consistent :-(
16:39:50
loke
I'm surprised that no one tried this before. I mean Maxima did run on Maclisp, which is the lisp that powered Genera, wasn't it?
16:42:47
beach
I don't remember. It's predecessor was named Macsyma. And the Mac part I think is from project Mac.
16:45:32
loke
It seems like an obvious project if you have a graphical interface couples with macsyma
16:48:03
beach
Yes, I was going to mention improvements in font technology. I think you are right that that's a big improvement.