Re: Starter-pack and documentation search

Unable to parse email body. Email id is 10356

Re: Starter-pack and documentation search

On Sun, 20 Jun 2010 15:47:11 +0100, Paul Tarvydas  
<tarvydas@visualframeworksinc.com> wrote:

>  It looks like LW was looking for a particular browser but didn't find  
> it. The bottom half of the error dialog gives you a bunch of options on  
> how to proceed - called "restarts".  Click on the most appropriate  
> browser choice, hit OK, and see if that helps.

I tried that and it did not help, the dialog pops up again no matter what  
option is chosen.
The thing is that it throws in errors only when a non hyperspec entry is  
searched for, otherwise it opens up the default browser nicely.

Re: Starter-pack and documentation search

"Yuri Davidovsky" <yury.davidouski2@mail.dcu.ie> writes:

> Hi there,
>
> just coming back to lisping after a couple years break and have Lispworks
> 5.0.2 Pro running with the latest starter-pack installed. All seemed good
> until today when trying to do an F5 documentation search the IDE came up
> with a debug window shown in the attachment. I remember it working
> properly back then and the funny bit is that the search seems to work fine
> when the search pertains to the CL hyperspecs docs but an error happens
> when searching within the lispworks specific documentation.
>
> For example, a search with a FORMAT string will come up with the
> appropriate page while a search for something like OUTPUT-PANE will result
> in an error described. There is a bit too much of low level stuff going on
> in the debugger to make any sense out of from where I am standing,
> maybe someone has came across this before?

This looks like a bug in LW-ADD-ONS (or LW-DOC), so you should ask Edi
Weitz. Only, MOP and LispWorks specific documentation seems to be
affected. In LispWorks 6.0.1 Pro for Linux I don't get an error, but I
do get an invalid URL in my browser. E.g. for capi:output-pane: 
file://usr/local/lib/LispWorks/lib/6-0-0-0/manual/online/web//usr/local/lib/LispWorks/lib/6-0-0-0/manual/online/web/CAPRM/html/capiref-262.htm#marker-4173290

LispWorks 6.0.1 Pro for Windows does signal an error:

Error: Bad result from ShellExecute 2
  1 (continue) Abort editor command.
  2 (abort) Return to event loop.
  3 Destroy interface "Listener 1" (of type LISPWORKS-TOOLS:LISTENER)

CL-USER 1 : 1 > :b
Call to ERROR
Call to (METHOD HQN-WEB:BROWSE-PAGE (SYMBOL T))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (SUBFUNCTION EDITOR::FUNCTION-MAYBE-INHIBITED EDITOR::FUNCALL-COMMAND-FUNCTION)
Call to EDITOR::FUNCALL-COMMAND-FUNCTION
Call to EDITOR::DO-A-COMMAND
Call to EDITOR::I-PROCESS-CHARACTER
Call to CAPI::USER-INPUT-CALL-EDITOR
Call to CAPI::IN-PROCESS-CAPI-EVENT-CALLBACK
Call to CAPI:EXECUTE-WITH-INTERFACE
Call to CAPI-INTERNALS:PROCESS-CAPI-EVENT-WITH-HANDLER
Call to CAPI-WIN32-LIB::CHAR-EVENT-HANDLER
Call to CAPI-WIN32-LIB::MAYBE-PROCESS-KEYDOWN
Call to CAPI-WIN32-LIB::HANDLE-WM-KEYDOWN
Call to WIN32::WND-PROC
Call to (SUBFUNCTION WIN32::|%FOREIGN-CALLABLE/wnd_proc_callback| (FLI:DEFINE-FOREIGN-CALLABLE "wnd_proc_callback"))
Call to FLI::FOREIGN-CALLABLE-ENTRY-POINT-AUX-NESTED
Call to WIN32:IS-DIALOG-MESSAGE
Call to WIN32::PROCESS-MESSAGES
Call to MP::WIN32-PROCESS-WAIT-FOR-EVENT
Call to MP:PROCESS-READ-EVENT
Call to CAPI-INTERNALS:LOOP-PROCESS-EVENTS
Call to CAPI::INTERFACE-EVENT-LOOP
Call to CAPI::INITIALIZE-AND-PROCESS-EVENTS
Call to (METHOD CAPI-LIBRARY:INTERFACE-PROCESS-WRAPPER (CAPI-WIN32-LIB::R-MDICLIENT T T))
Call to MP::PROCESS-SG-FUNCTION


In the meantime, you can use LispWorks' own documentation look-up
facility (which works somewhat different) by pressing Ctrl-Shift-d when
the cursor is on a symbol. If you don't like the prompt, set
editor:*prompt-for-symbol-confirm* to nil:
(setq editor:*prompt-for-symbol-confirm* nil)

Regards.
Nico

Re: Starter-pack and documentation search

On Mon, 21 Jun 2010 10:42:34 +0100, Nico de Jager <ndj@bitart.cc> wrote:


> LispWorks 6.0.1 Pro for Windows does signal an error:

I am actually using the Windows (W7 64) version, forgot to say.

>
> Error: Bad result from ShellExecute 2
>   1 (continue) Abort editor command.
>   2 (abort) Return to event loop.
>   3 Destroy interface "Listener 1" (of type LISPWORKS-TOOLS:LISTENER)
>
> CL-USER 1 : 1 > :b
> Call to ERROR
> Call to (METHOD HQN-WEB:BROWSE-PAGE (SYMBOL T))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (SUBFUNCTION EDITOR::FUNCTION-MAYBE-INHIBITED  
> EDITOR::FUNCALL-COMMAND-FUNCTION)
> Call to EDITOR::FUNCALL-COMMAND-FUNCTION
> Call to EDITOR::DO-A-COMMAND
> Call to EDITOR::I-PROCESS-CHARACTER
> Call to CAPI::USER-INPUT-CALL-EDITOR
> Call to CAPI::IN-PROCESS-CAPI-EVENT-CALLBACK
> Call to CAPI:EXECUTE-WITH-INTERFACE
> Call to CAPI-INTERNALS:PROCESS-CAPI-EVENT-WITH-HANDLER
> Call to CAPI-WIN32-LIB::CHAR-EVENT-HANDLER
> Call to CAPI-WIN32-LIB::MAYBE-PROCESS-KEYDOWN
> Call to CAPI-WIN32-LIB::HANDLE-WM-KEYDOWN
> Call to WIN32::WND-PROC
> Call to (SUBFUNCTION WIN32::|%FOREIGN-CALLABLE/wnd_proc_callback|  
> (FLI:DEFINE-FOREIGN-CALLABLE "wnd_proc_callback"))
> Call to FLI::FOREIGN-CALLABLE-ENTRY-POINT-AUX-NESTED
> Call to WIN32:IS-DIALOG-MESSAGE
> Call to WIN32::PROCESS-MESSAGES
> Call to MP::WIN32-PROCESS-WAIT-FOR-EVENT
> Call to MP:PROCESS-READ-EVENT
> Call to CAPI-INTERNALS:LOOP-PROCESS-EVENTS
> Call to CAPI::INTERFACE-EVENT-LOOP
> Call to CAPI::INITIALIZE-AND-PROCESS-EVENTS
> Call to (METHOD CAPI-LIBRARY:INTERFACE-PROCESS-WRAPPER  
> (CAPI-WIN32-LIB::R-MDICLIENT T T))
> Call to MP::PROCESS-SG-FUNCTION

Yep, the traceback looks exactly the same, did not bother to find out what  
all that means.


> In the meantime, you can use LispWorks' own documentation look-up
> facility (which works somewhat different) by pressing Ctrl-Shift-d when
> the cursor is on a symbol. If you don't like the prompt, set
> editor:*prompt-for-symbol-confirm* to nil:
> (setq editor:*prompt-for-symbol-confirm* nil)

That seems to work just fine, thanks for the hint, that should do.

Re: Starter-pack and documentation search

I've uploaded a new version of LW-DOC which hopefully fixes this
problem.  Thanks for the report.

Edi.


On Mon, Jun 21, 2010 at 11:42 AM, Nico de Jager <ndj@bitart.cc> wrote:
>
> "Yuri Davidovsky" <yury.davidouski2@mail.dcu.ie> writes:
>
>> Hi there,
>>
>> just coming back to lisping after a couple years break and have Lispworks
>> 5.0.2 Pro running with the latest starter-pack installed. All seemed good
>> until today when trying to do an F5 documentation search the IDE came up
>> with a debug window shown in the attachment. I remember it working
>> properly back then and the funny bit is that the search seems to work fine
>> when the search pertains to the CL hyperspecs docs but an error happens
>> when searching within the lispworks specific documentation.
>>
>> For example, a search with a FORMAT string will come up with the
>> appropriate page while a search for something like OUTPUT-PANE will result
>> in an error described. There is a bit too much of low level stuff going on
>> in the debugger to make any sense out of from where I am standing,
>> maybe someone has came across this before?
>
> This looks like a bug in LW-ADD-ONS (or LW-DOC), so you should ask Edi
> Weitz. Only, MOP and LispWorks specific documentation seems to be
> affected. In LispWorks 6.0.1 Pro for Linux I don't get an error, but I
> do get an invalid URL in my browser. E.g. for capi:output-pane:
> file://usr/local/lib/LispWorks/lib/6-0-0-0/manual/online/web//usr/local/lib/LispWorks/lib/6-0-0-0/manual/online/web/CAPRM/html/capiref-262.htm#marker-4173290
>
> LispWorks 6.0.1 Pro for Windows does signal an error:
>
> Error: Bad result from ShellExecute 2
>  1 (continue) Abort editor command.
>  2 (abort) Return to event loop.
>  3 Destroy interface "Listener 1" (of type LISPWORKS-TOOLS:LISTENER)
>
> CL-USER 1 : 1 > :b
> Call to ERROR
> Call to (METHOD HQN-WEB:BROWSE-PAGE (SYMBOL T))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (SUBFUNCTION EDITOR::FUNCTION-MAYBE-INHIBITED EDITOR::FUNCALL-COMMAND-FUNCTION)
> Call to EDITOR::FUNCALL-COMMAND-FUNCTION
> Call to EDITOR::DO-A-COMMAND
> Call to EDITOR::I-PROCESS-CHARACTER
> Call to CAPI::USER-INPUT-CALL-EDITOR
> Call to CAPI::IN-PROCESS-CAPI-EVENT-CALLBACK
> Call to CAPI:EXECUTE-WITH-INTERFACE
> Call to CAPI-INTERNALS:PROCESS-CAPI-EVENT-WITH-HANDLER
> Call to CAPI-WIN32-LIB::CHAR-EVENT-HANDLER
> Call to CAPI-WIN32-LIB::MAYBE-PROCESS-KEYDOWN
> Call to CAPI-WIN32-LIB::HANDLE-WM-KEYDOWN
> Call to WIN32::WND-PROC
> Call to (SUBFUNCTION WIN32::|%FOREIGN-CALLABLE/wnd_proc_callback| (FLI:DEFINE-FOREIGN-CALLABLE "wnd_proc_callback"))
> Call to FLI::FOREIGN-CALLABLE-ENTRY-POINT-AUX-NESTED
> Call to WIN32:IS-DIALOG-MESSAGE
> Call to WIN32::PROCESS-MESSAGES
> Call to MP::WIN32-PROCESS-WAIT-FOR-EVENT
> Call to MP:PROCESS-READ-EVENT
> Call to CAPI-INTERNALS:LOOP-PROCESS-EVENTS
> Call to CAPI::INTERFACE-EVENT-LOOP
> Call to CAPI::INITIALIZE-AND-PROCESS-EVENTS
> Call to (METHOD CAPI-LIBRARY:INTERFACE-PROCESS-WRAPPER (CAPI-WIN32-LIB::R-MDICLIENT T T))
> Call to MP::PROCESS-SG-FUNCTION
>
>
> In the meantime, you can use LispWorks' own documentation look-up
> facility (which works somewhat different) by pressing Ctrl-Shift-d when
> the cursor is on a symbol. If you don't like the prompt, set
> editor:*prompt-for-symbol-confirm* to nil:
> (setq editor:*prompt-for-symbol-confirm* nil)
>
> Regards.
> Nico
>
>