gmane.lisp.lispworks.general

Re: portableaserve threads problems gone

Lawrence Au — 2012-05-22T22:43:21

Hi Martin,
     It's been several months,  and we still not seen a single failure  
due this this bug,  so I consider your fix to be a total success!

thank you,

Lawrence Au
Sauriel LLC.
On Mar 20, 2012, at 10:36 AM, Lawrence Au wrote:

Clon 1.0b22 is out

Didier Verna — 2012-05-22T12:36:42


  FYI, this new release now supports LispWorks. Thanks to Martin for
providing a fully functional version of LW 6.1.

http://www.didierverna.com/sciblog/index.php?post/2012/05/22/Clon-1.0b22-is-out

Re: error-output and stderr

Camille Troillard — 2012-05-15T18:11:10


On 15 mai 2012, at 19:49, Martin Simmons wrote:


Thank you Martin, somehow I must have missed something because I saw this function but it didn't work for me.
A simple test case shows it obviously works properly:


;;;
;;; Use Build Application to produce an executable
;;;

(defun test ()
  (let ((*error-output* (sys:make-stderr-stream)))
    (write-string "This is on the standard output")
    (terpri)
    (write-string "This is on the error output" *error-output*)
    (terpri *error-output*)))

(compile 'test)

(deliver 'test
         "~/test.out"
         5)


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: error-output and stderr

Martin Simmons — 2012-05-15T17:49:21


The default value of *terminal-io* writes to stdout and you can make a stream
for stderr by calling system:make-stderr-stream.

capi:clone

Paul Tarvydas — 2012-05-15T14:45:06

Is capi:clone implemented for the standard pinboard objects?  I would have expected so, but it appears not to be the case (in LW61):

(capi:clone (make-instance 'capi:capi-object))

fails, same as for capi:ellipse.  Comments welcome.

pt

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug< at >lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Capi input model on Mac OS X 10.7 for key/character does not work!

Deepak Surti — 2012-05-15T09:50:38

I am trying to run the input-model.lisp example under:
examples/capi/output-panes/input-model.lisp

However, except mouse inputs; key and char inputs do not work.

I am on Mac OS X 10.7 running Lispworks 6.0 Personal edition.

Any ideas appreciated?

Thanks,
Deepak

error-output and stderr

Camille Troillard — 2012-05-14T15:31:19

Hello,

I am working on a delivered executable on Mac OS X.
How do I send *error-output* to stderr and *standard-output* to stdout?


Best Regards,
Camille

Remove me from the mail list

??? — 2012-05-11T11:37:16

Dear sir, 

 

could you please remove me  from the mail list, since I could not
find the way to do it myself.

 

Thank you in advance

Use of '--' on the command-line

Didier Verna — 2012-05-11T09:22:35


  And here's a suggestion: it would be nice if Lispworks complied with
Posix by ignoring what's after '--' on its command-line (all other
compilers currently do so).

AFAICUI, the current behavior is to ignore options unknown to Lispworks,
and leave everything in *line-arguments-list*. This is almost OK because
you can pass any user-specific option to your session, but the problem
is the risk of collision with options that Lispworks already handles.

For instance, you cannot currently say something like this:

lispworks -load mystuff.lisp -- -build myprog ; myprog non-existant

because Lispworks tries to handle -build itself.

Remove me from the mailing list

Sally Sangwon Park — 2012-05-11T07:40:27

Dear sir, 

could you please remove me  from the mail list, since I could not
find the way to do it myself.

Thank you in advance

--
Sally Sangwon Park
Kstartup Project Manager 

Cell: +82)10-9287-6632
Email: sallypark< at >me.com
Skype: < at >psw1223
Twitter: < at >psw1223
Facebook: facebook.com/sallypark1223

Remove me from the mail list

aouss gabash — 2012-05-11T06:51:12

Dear sir, 


could you please remove me  from the mail list, since I could not
find the way to do it myself.

Thank you in advance

Re: accessing a stream's file descriptors

Didier Verna — 2012-05-10T22:18:02


  FWIW, here's a new version with more robust support for non
FILE-STREAMs and with support for Lispworks SYSTEM::TERMINAL-STREAMs as
well...

Re: accessing a stream's file descriptors

Didier Verna — 2012-05-10T18:56:43


  TIOCGWINSZ. It's for Clon. The idea is to figure out whether the
stream is connected to a terminal and (when that's the case) get the
terminal size at the same time.

The most common situation is a standalone application doing 'app --help'
or 'app --help > file' on a terminal (which involves *standard-output*
in both cases).

In case you're interested, I'm attaching the file doing this in the
current version of Clon. It supports 7 implementations in various ways
(CFFI or some implementation-specific version). The current code would
probably break for esoteric streams (checking slime streams is on my
TODO List) but it works for the intended usage at least.

Re: accessing a stream's file descriptors

Martin Simmons — 2012-05-10T17:10:54


Yes, kind of (there is one for stderr as well).



It isn't printed anywhere by default.  The underlying stdout on the Mac is
connected to the Console log, but we don't want to write the LispWorks startup
banner there every time, so the output it collected in memory and written to
the emergency terminal window if the IDE crashes back to the terminal debugger
for some reason.



That could be risky on a file descriptor that you don't control (and could be
of an unknown type, e.g. pipe, tty).  Which ioctl is it?  Possibly LispWorks
should include an API for it?



That's probably a "no" then -- LispWorks doesn't link with cygwin, so it won't
be calling cygwin's ioctl.

Re: accessing a stream's file descriptors

Didier Verna — 2012-05-10T16:39:11

Martin Simmons wrote:


  Hmmm, so is this a singleton?



  Is there a way to know where it will be printed ?



  Perform an ioctl on it.



  Err, not sure :-) In fact, I think it should under cygwin, but
probably not otherwise.

remove from the mail list

zhao yh — 2012-05-10T16:11:36

Dear sir,  please remove me  from the mail list, since I could not
find the way to do it myself. Thank you

Re: accessing a stream's file descriptors

Martin Simmons — 2012-05-10T16:09:06


TERMINAL-STREAM on Unix-like OSes always uses fd 1 (but note that output to
*TERMINAL-IO* will not be written there by default in a GUI application).

What will be the foreign code do with the fd?  Is this code supposed to work
on Windows?

__Martin

linux ide question

Ala'a Mohammad — 2012-05-10T16:04:18

Hi,

I'm using the following in my .lispworks

;; initially from http://article.gmane.org/gmane.lisp.lispworks.general/3122
;; the small annoying window toolbar is called lispworks-echo-podium
;; note that lispwoks has lispworks-podium, but is not exported
(defparameter *the-echo-podium* nil)

(define-action "CAPI Create Interface"
              "catch the echo podium"
              #'(lambda (interface)
                  (when (typep interface 'lw-tools:lispworks-echo-podium)
                    (capi:hide-interface interface nil)
                    (setf *the-echo-podium* interface))))

;; I tried to kill the podium in the previous stage, but it seems that
it is being checked for at startup, so I needed to catch it,
;; and then kill it later on
(define-action "Initialize LispWorks Tools"
              "Kill this echo podium"
               #'(lambda (obj)
                   (declare (ignore obj))
                   (capi:quit-i

Re: accessing a stream's file descriptors

Didier Verna — 2012-05-10T15:52:43

Tim Bradshaw <tfb< at >cley.com> wrote:


  Yeah, that's true. It seems to me that TERMINAL-STREAMs should,
though. As per Paul's suggestion, I introspected a bit and the only
thing I could see so far is a slot named OUTPUT-HANDLE which sounds
kinda nice, but its value for *terminal-io* is T, not an fd... :-/



  Probably (hence Nick's suggestion). However, even in a standalone
console application (delivered from Lispworks), a TERMINAL-STREAM such
as *terminal-io* has no relation with an OS stream, and that currently
escapes me...

Re: accessing a stream's file descriptors

Nick Levine — 2012-05-10T15:23:14


Not a clue then. Sorry.

- nick

Re: accessing a stream's file descriptors

Paul Tarvydas — 2012-05-10T15:12:53

That's not necessarily an FD, e.g. in IDE mode *standard-output* is an editor stream, not a file descriptor.

It would be an FD if you delivered the app.  So, inspect (interactively) *terminal-stream* to figure out what the fields are, then deliver a test app that displays the values of these fields.  With luck, you might see where the FD (handle) is.

pt

gmane.lisp.lispworks.general

Re: portableaserve threads problems gone

Clon 1.0b22 is out

Re: *error-output* and stderr

Re: *error-output* and stderr

capi:clone

Capi input model on Mac OS X 10.7 for key/character does not work!

*error-output* and stderr

Remove me from the mail list

Use of '--' on the command-line

Remove me from the mailing list

Remove me from the mail list

Re: accessing a stream's file descriptors

Re: accessing a stream's file descriptors

Re: accessing a stream's file descriptors

Re: accessing a stream's file descriptors

remove from the mail list

Re: accessing a stream's file descriptors

linux ide question

Re: accessing a stream's file descriptors

Re: accessing a stream's file descriptors

Re: accessing a stream's file descriptors

Re: error-output and stderr

Re: error-output and stderr

error-output and stderr