Thanks! Just realized it says that when the prompt starts—I hadn’t noticed
it.
On Mon, Dec 10, 2012 at 1:47 PM, Devin Walters wrote:
> cljs/quit
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegrou
Have you tried :cljs/quit ?
Cheers,
--
'(Devin Walters)
On Monday, December 10, 2012 at 3:23 PM, Asim Jalis wrote:
> Is there a way to exit the ClojureScript REPL? None of these worked: Ctrl-D,
> exit. (exit 1), quit, (quit 1). So eventually I killed the window.
>
> -
Is there a way to exit the ClojureScript REPL? None of these worked:
Ctrl-D, exit. (exit 1), quit, (quit 1). So eventually I killed the window.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email
> > Also is there any way to contribute patches to the clojure website
> > itself? (maybe put it up on github too?)
>
> Instructions on the patch process are
> athttp://dev.clojure.org/display/design/JIRA+workflow. Issues waiting for
> patches are
> athttp://dev.clojure.org/jira/secure/IssueNa
On Feb 25, 9:43 am, Stuart Halloway wrote:
> > Hello all. A bit new to clojure here. Anyway I found it a bit
> > difficult to exit from a REPL.
> > Would a patch to make it give instructions (like Python's
>
> > C:\>c:\installs\Python26\python.exe
> &
Yeah, you're right. I was thinking of what happens when you fall off the
end of main.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - plea
On Fri, Feb 25, 2011 at 10:04 PM, .Bill Smith wrote:
> If you are running any non-daemon threads, even System.exit won't cause the
> JVM to shut down.
I'm pretty sure it will. Falling off the end of main won't and closing
all GUI windows won't, but System/exit is suppos
On Fri, Feb 25, 2011 at 9:39 PM, Alan wrote:
> On Feb 25, 6:21 pm, Ken Wesson wrote:
>> On Fri, Feb 25, 2011 at 11:21 AM, Michael Wood wrote:
>> > Would this help?
>>
>> > user=> (def exit "Use Ctrl-C to exit")
>> > #'user/exit
>
If you are running any non-daemon threads, even System.exit won't cause the
JVM to shut down. Whereas as Michael Wood pointed out, there are various
control sequences that do the trick reliably.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To po
On Feb 25, 6:21 pm, Ken Wesson wrote:
> On Fri, Feb 25, 2011 at 11:21 AM, Michael Wood wrote:
> > Would this help?
>
> > user=> (def exit "Use Ctrl-C to exit")
> > #'user/exit
> > user=> exit
> > "Use Ctrl-C to exit"
> > us
On Fri, Feb 25, 2011 at 11:21 AM, Michael Wood wrote:
> Would this help?
>
> user=> (def exit "Use Ctrl-C to exit")
> #'user/exit
> user=> exit
> "Use Ctrl-C to exit"
> user=>
Why stop there?
(defn exit [] (System/exit 0))
--
You receive
> Hello all. A bit new to clojure here. Anyway I found it a bit
> difficult to exit from a REPL.
> Would a patch to make it give instructions (like Python's
>
> C:\>c:\installs\Python26\python.exe
>>>> exit
> Use exit() or Ctrl-Z plus Return to exit
>&g
On 25 February 2011 17:35, Armando Blancas wrote:
> Using jline you can exit with ctrl-d. This is from the clojure web
> site in Getting Started:
>
> The REPL has very rudimentary editing. For a better experience, try
> running it via the JLine ConsoleRunner:
> ja
Using jline you can exit with ctrl-d. This is from the clojure web
site in Getting Started:
The REPL has very rudimentary editing. For a better experience, try
running it via the JLine ConsoleRunner:
java -cp jline-0_9_5.jar:clojure.jar jline.ConsoleRunner clojure.main
On Feb 24, 4:38 pm
Hello all. A bit new to clojure here. Anyway I found it a bit
difficult to exit from a REPL.
Would a patch to make it give instructions (like Python's
C:\>c:\installs\Python26\python.exe
>>> exit
Use exit() or Ctrl-Z plus Return to exit
>>>
)
like that have a chanc
The snippet:
---
(def reschedule nil) ; Forward declaration
(defn broadcast [msg]
(reschedule)
(doall
(map
(fn [client]
(send-msg client msg))
@clients)))
---
(def
Ngo,
I checked out your github , it is great. I have not used netty, it looks
clean. However, what is the meaning of this, (def reshedule nil)?
Regards,
Emeka
On Thu, Oct 15, 2009 at 3:02 AM, ngocdaothanh wrote:
>
> I created this (Netty is used instead of server-socket):
> http://github.com/
I created this (Netty is used instead of server-socket):
http://github.com/ngocdaothanh/telchat-clojure
I am going to create a Scala version of the same program to have a
feeling of Clojure vs Scala, it will be telchat-scala.
On Oct 14, 10:12 pm, Emeka wrote:
> Ngo,
>
> Honestly speaking I do
Ngo,
Honestly speaking I don't know. How far have you gone?
Regards,
Emeka
On Sat, Oct 3, 2009 at 3:21 PM, ngocdaothanh wrote:
>
> Emeka, good catch. It's just my mistake.
>
> Another thing is I think there may be exception raised when on-msg
> sends message to a closed socket. How would you
Emeka, good catch. It's just my mistake.
Another thing is I think there may be exception raised when on-msg
sends message to a closed socket. How would you solve this?
On Oct 3, 7:35 pm, Emeka wrote:
> ngo,
> I was about doing this kind of client/server thing some days ago, however
> now you
ngo,
I was about doing this kind of client/server thing some days ago, however
now you are into it I would like to learn then. I am not quite clear why you
have this:
(.start (new Thread (fn [] (create-server 8080 chat-loop
My concern is on Thread, create-server function has a Thread inside
> I'm not sure TCP/IP has a native facility for that.
I'm afraid John's statement is correct:
http://www.velocityreviews.com/forums/t125620-client-socket-disconnection-event-not-received-on-server-socket-java-nio.html
and trying to read and write until something wrong happens as
demonstrated in R
On Thu, Oct 1, 2009 at 4:02 PM, Roger Gilliar wrote:
> Am 01.10.2009 um 21:28 schrieb ngocdaothanh:
> > Roger, your code is not event based.
> What do you mean by not event based ?
He means he wants automatic notification if a connection is dropped.
I'm not sure TCP/IP has a native facility fo
Am 01.10.2009 um 21:28 schrieb ngocdaothanh:
> Roger, your code is not event based.
What do you mean by not event based ?
Regards
Roger
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post t
Roger, your code is not event based.
I'm new to Clojure and as a small exercise I just want to create a
simple chat server for telnet clients, any usable socket library is
OK:
* Chat messages are broadcast to all clients
* When a client disconnect, all others will receive "A client has
disconnect
>
> I want to write a simple socket server in Clojure. I want to perform
> some action when a client disconnects.
---
The following code works for me. read-input returns nil if the socket
is closed (the client disconnects)
Regards
Roger
(defn read-inp
I want to write a simple socket server in Clojure. I want to perform
some action when a client disconnects.
I tried server-socket:
http://richhickey.github.com/clojure-contrib/server-socket-api.html
but it does not support on exit event.
Is there a solution? Should I look at something like
ks for your reply. You are quite right - adding (shutdown-agents)
does allow the script using lazy-xml to exit promptly. From a cursory
scan of the lazy-xml/parse-seq code, it does use agents.
-mark
--~--~-~--~~~---~--~~
You received this message because you are s
2009/7/29 mwillson :
>
> Hi,
>
> I was experimenting with Clojure and XML and stumbled upon a lengthy
> hang when exiting java which was tracked down to the use of
> clojure.contrib.lazy-xml. Here's a toy example which exhibits the
> issue:
I haven't looked at clojure.contrib.lazy-xml, but this
j
(ns strange
(:use clojure.contrib.lazy-xml)
(import (java.io ByteArrayInputStream)))
(time (clojure.contrib.lazy-xml/parse-trim
(ByteArrayInputStream. (.getBytes (slurp "msgs.xml")
#_(System/exit 0)
[~/dev/clojure]$ time java -cp clojure-1.0.0.jar\;clojure-contrib.jar
cloj
On 27/05/2009, Baishampayan Ghose wrote:
..
> In the SLIME REPL, press , (comma) and then type 'quit' and press Enter.
>
> That'd close your REPL gracefully after which you can exit Emacs by
> pressing C-x C-c.
>
> Regards,
> BG
>
> --
Exactly what
> I have just started learning Clojure, and I found Clojure Box (http://
> clojure.bighugh.com/) to be an easy installation for that.
> Unfortunately, I am not sure about the right way to exit from the
> prompt.
> After starting Clojure Box and using the prompt (possibly includin
Hi everyone,
I have just started learning Clojure, and I found Clojure Box (http://
clojure.bighugh.com/) to be an easy installation for that.
Unfortunately, I am not sure about the right way to exit from the
prompt.
After starting Clojure Box and using the prompt (possibly including
loading and
I've updated this patch, eliminating the performance hit I introduced
for concatenation of stdout & stderr when they're byte arrays (turns
out it was significant). Let me know if there's anything else I can
do.
Perry
http://code.google.com/p/clojure-contrib/issues/detail?id=23
--~--~-~-
Patch submitted to the issue tracker:
http://code.google.com/p/clojure-contrib/issues/detail?id=23
Thanks,
Perry
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send email t
> Sounds good. Is ':verbose' the best name for this option? What about
> ':return-map'? I'm okay with ':verbose' if we can't reach consensus
> on something else.
I agree that :verbose isn't right -- :return-map's not bad at all.
Perry
--~--~-~--~~~---~--~~
You
On Wed, Jan 28, 2009 at 4:43 PM, Chouser wrote:
>
> Sounds good. Is ':verbose' the base name for this option?
Sorry for the typo. "best name"
--Chouser
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Clojure" g
On Wed, Jan 28, 2009 at 4:37 PM, Perry Trolard wrote:
>
> I'd sometimes like to have the exit status from system commands, so I
> patched clojure.contrib.shell-out to accept a :verbose option which,
> when turned on, returns a map with :exit, :out, & :err (where :exit'
Hi Users of Shell-out,
I'd sometimes like to have the exit status from system commands, so I
patched clojure.contrib.shell-out to accept a :verbose option which,
when turned on, returns a map with :exit, :out, & :err (where :exit's
value is the exit code int, & :out &
SWEET! That did it. I knew that I had to be doing something stupid.
That won't be the first time I am sure. Thank you for the help.
On Jan 4, 12:13 pm, "Stephen C. Gilardi" wrote:
> On Jan 3, 2009, at 7:57 PM, chris wrote:
>
> > I was wondering if anyone else had a problem with this. I am trying
On Jan 3, 2009, at 7:57 PM, chris wrote:
I was wondering if anyone else had a problem with this. I am trying to
run clojure on Vista. I think that the problem might be with my
environmental variables but I am not sure which ones to changes or
where to point them too.
Thank you for your help.
Chris,
I run my Clojure on Vista and I have not experienced what you mentioned. I
would like to know what you have done. Your installation details. And did
you download your Clojure.jar or did you use ant to build yours?
Emeka
On Sun, Jan 4, 2009 at 12:57 AM, chris wrote:
>
> I was wondering i
I was wondering if anyone else had a problem with this. I am trying to
run clojure on Vista. I think that the problem might be with my
environmental variables but I am not sure which ones to changes or
where to point them too.
Thank you for your help.
--~--~-~--~~~---
Answering my own question ...
It seems that there is provision for a "user startup file", user.clj.
Maybe that's where I should have put my mods?
Oh and I've seen other (previous) answers to this (exit) -- that must
be a FAQ, except that I couldn't find the FAQ :-( --
OK. That one with trivial to add :-)
(defn exit
"Returns to the OS by forcibly exiting the platform"
([] (. System exit 0))
([n] (. System exit n)))
Added inside boot.clj, right before
(import '(java.io Writer))
(defn- print-sequential [#^String b
45 matches
Mail list logo