Re: [Factor-talk] Git
I don't want to publish my changes anytime soon, only distinguish them from released clean-branch code, so that I can track both. If you get tired of so much standing in your way of going forward, consider doing manual things with these files, old-school (rename/move them, checkout so you have latest, copy back over). I get the sense there are a lot of formalities standing in the way of your having more fun with the actual code at hand. Factor is wonderful, I love it with a passion. I hope you find time to discover that amid all the font changing and source code system learning. I've read a lot of Git material tonight, and, frankly, most of it is not well written. I found two significantly different descriptions of git pull. One of these implies only a repo manipulation; the other, I think the correct one, implies that the working directory is updated, as well. This seems to be what happens in our factor.cmd pull, but I cannot explain it yet with definitions I've read. Shaping -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Git: Repository -Verfiy Database warnings on freshly cloned and pulled repo
I imagine that someone has seen the problem before and already knows the issue. Has anyone tried to verify a fresh clone and seen this problem? I suppose it doesn't matter much, if the problem still exists for all of us, and hasn't caused any problems. Then, again, I may be the only one doing the verify; it's convenient from the GUI. I think most of us are using the Git Bash. Shaping From: John Benediktsson [mailto:mrj...@gmail.com] Sent: 2010-November-15, 05:10 To: factor-talk@lists.sourceforge.net Subject: Re: [Factor-talk] Git: Repository -Verfiy Database warnings on freshly cloned and pulled repo Can someone explain this? How serious a problem is this? Does it indicate corruption in my local repo? Would it be possible to keep out-of-topic questions out of this list (this one should be posted on a git users mailing-list since it has nothing to do with Factor)? They seem to arrive faster than I am able to mark them as ignored. I have to agree. Generally I'm in favor of helping out where possible, but the discussion here is overwhelming and not about Factor. If you want some iterative help like this, perhaps IRC or other sources would be better? Don't misunderstand - your Factor ideas are very welcome and encouraged. Thanks, John. -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] load-all
On Mon, Nov 15, 2010 at 4:07 PM, Shaping shap...@charter.net wrote: I just completed a fresh cloning of the Factor origin repo and a build of factor.exe. I opened the Listener, and evaluated load-all. When the load-all completed, I saw only this: I don't know enough about site-watcher to say what the exact problem is, but in general, missing symbol errors during load-all are minor problems, unless you intend to actually use the affected vocabularies. -Joe -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Integrating Browser functionality into Listener: John Benediktsson's Syntax Highlighting
On Mon, Nov 15, 2010 at 8:45 AM, Shaping shap...@charter.net wrote: I'm also thinking that the stack-effect data could be more binding than it currently is. I noticed while compiling some new words that the compiler will infer a stack-effect, and tell you when you've written it incorrectly. This looks almost binding. So my suggestion/question is: Can we use the stack effects to check at least the superficial (type- and count-based) correctness of a forth expression, as it is assembled on a Listener command line? The stack effects are already binding. When you enter a word definition, and the compiler determines that the code's stack effect does not match the declared effect, you'll get an immediate compiler error. The one exception to this is inline higher-order words (words such as map that take a quotation as input)—for these words, stack checking will be deferred to call sites that use the inline higher-order word, because the stack checking can't be done thoroughly without a quotation to fill in the parameter. If the word declares a static stack effect for its quotations, the effect will be enforced on the caller: -- ( scratchpad ) : foo ( x quot: ( x -- ) -- ) call ; inline ( scratchpad ) : bar ( x y -- ) [ + . ] foo ; ! bar should cause an Input quotation to foo doesn't match its expected effect error -- If the word declares a polymorphic effect (using ..a style stack variables to represent a variable number of values), the arities of the stack variables will be unified, and an error raised if unification fails: -- ( scratchpad ) \ if see : if ( ..a ? true: ( ..a -- ..b ) false: ( ..a -- ..b ) -- ..b ) ? call ; ( scratchpad ) : bas ( x y z? -- ) [ + ] [ neg ] if ; ! bas should cause an Input quotations to “if” don't match their expected effects error -- If a higher-order word declares no stack effect for its quotation arguments, the overall stack effect of the caller will still be checked when the body of the higher-order word and its arguments have been inlined. -Joe -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] What should I call to issue [ 8080 httpd ] in-thread again, after closing factor reopening?
See pitfall #3 in this link
http://www.ibm.com/developerworks/linux/library/l-sockpit/
I cannot help with applying this knowledge to the Factor API.
--Jeff
From: Jim mack [mailto:j...@less2do.com]
Sent: Sunday, November 14, 2010 11:56 AM
To: factor-talk@lists.sourceforge.net
Subject: [Factor-talk] What should I call to issue [ 8080 httpd ]
in-thread again, after closing factor reopening?
reopening factor, then calling to [ 8080 httpd ] in-thread is now
throwing this kind of an error
[2010-11-14T19:53:33Z] NOTICE start-accept-loop: T{ inet6 f :: 8080 }
[2010-11-14T19:53:33Z] NOTICE start-accept-loop: T{ inet4 f 0.0.0.0
8080 }
[2010-11-14T19:53:33Z] ERROR start-accept-loop: Unix system call
E2809CbindE2809D failed:
[] ERROR start-accept-loop: Address already in use
(98)
[] ERROR start-accept-loop: It was called with the
following arguments:
[] ERROR start-accept-loop: 18
[] ERROR start-accept-loop: S{ sockaddr-in6 f 10
36895 0 ~uchar-array~ 0 }
[] ERROR start-accept-loop: 28
[2010-11-14T19:53:33Z] ERROR start-accept-loop: Unix system call
E2809CbindE2809D failed:
[] ERROR start-accept-loop: Address already in use
(98)
[] ERROR start-accept-loop: It was called with the
following arguments:
[] ERROR start-accept-loop: 18
[] ERROR start-accept-loop: S{ sockaddr-in f 2 36895
0 0 }
[] ERROR start-accept-loop: 16
I am on latest stable release binaries, ubuntu 10.4 lts, linode. I am
leaving the listener open in a screen. I thought I went through months
of this kind of deployment successfully, where I would just git pull in
the work folder, close restart factor + my vocab, and it would serve
the updated page.
--
Jim
I'm for extending the working Medicare program for our seniors all the
way back to contraception, so Americans can concentrate on living their
lives without fear of changing a job, going bankrupt from deductibles or
fighting HMO bureaucracy.
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Integrating Browser functionality into Listener: John Benediktsson's Syntax Highlighting
Shaping -- If you do embark on the effort you propose below, I would be happy to work on it with you (although I would think you would want to find at least one old hand to participate as well). What you describe is very close to what I intend for my own factor-like environment that I described to you previously and so I'm going to be doing a lot of the same design work anyway. Sounds like a good project to sink one's teeth into for really going up the factor learning curve. Regards, Mike From: shap...@charter.net To: factor-talk@lists.sourceforge.net Date: Sun, 14 Nov 2010 21:15:10 -0600 Subject: [Factor-talk] Integrating Browser functionality into Listener: John Benediktsson's Syntax Highlighting Hi John/all. I still have some Git exercises and maintenance to do tonight, but I tripped over this http://planet.factorcode.org/ and want to see where it might lead. The syntax highlighting is interesting to me. I'm wondering whether we can change the Listener GUI into a color vocab browser that focuses more on code and less on the navigation links and doc and examples, as in the current Browser. There is a place for those too, obviously, but I'm trying to change the emphasis a little to make development faster and to reduce the amount of typing of words into the Listener. One possibility: Split the Listener vertically, placing the usual Listener command line progression on, say, the right side, and another pane on the left. The idea is that, when you need to know what a word means, because you are trying to use it, or are wondering whether you even have the right word or concept in mind, you can type it into the Listener, and instead of doing \ some-word see you could instead dynamically search for the word's definition by either clicking on the word or just hovering over it. I'm thinking that if you access and display the word's definition on hover-over, instead of on click-on, you could rapidly scan colored formatted word definitions in the left pane. You could have, say, a line of words entered into the Listener, scan over them left to right (or whichever way) with your mouse, looking at their color definitions flash through the pane on the left. When you hit a word that is especially interesting/confusing, you click on it to lock that definition into the left pain. You can now wander up to the definition in the left pane with your mouse and continue the process of scanning over its words, drilling down toward primitives, until you are convinced you understand enough to complete the expression at hand. Every time you want to drill, stop scanning with your mouse and click on the interesting word to popup yet another pane below the one you were in when you clicked on the interesting word. Or, you could stack your definition windows on top of each other, as you drill, and provide a context menu back command, or just use some forward/backward arrows in the GUI to go back and then go forward again, just as you would in the HTML help Browser. So why do this? If you are in a coding app and not a browsing app, you could not only scan and study as you drill, you can also scan and edit the command line you are building. Maybe Ctrl-click on a word to append it to the end of the Listener's command line. (Maybe the other way: Ctrl-click for doc and click for appending.) I want to get around faster, and to assemble correct Factor expressions, the first time. I don't want to see an example for a word before I see the code for the word. The reason for this is subtle but important: I want to understand the words increasingly quickly when I read them and their definitions, and not by remembering necessarily several favorite examples, which memories I will acquire anyway if I can use the word successfully in my own word definitions a few times. Having a bad time reading words creates a drive to improve the words, especially because you are now reading definitions more often than examples (which I think I would want to put in a nearby pane or in an examples tab in the same pane). I don't want to use English explanations and examples as crutches for reading Factor fluently. I want to write better words and patterns of them. Being required to read definitions first may be a healthy source of pressure in that direction. I'm also thinking that the stack-effect data could be more binding than it currently is. I noticed while compiling some new words that the compiler will infer a stack-effect, and tell you when you've written it incorrectly. This looks almost binding. So my suggestion/question is: Can we use the stack effects to check at least the superficial (type- and count-based) correctness of a forth expression, as it is assembled on a Listener command line? Also, concerning literals and stack objects, when you mouse-scan those, you could get an inspector, also on the left in its own pane, under your last
Re: [Factor-talk] What should I call to issue [ 8080 httpd ] in-thread again, after closing factor reopening?
Thank you! I was looking at this more as a potential regression in factor,
but I think it more productive to look at it as my noobieness on *nx.
On Mon, Nov 15, 2010 at 10:32 AM, Jeff C. Britton j...@iteris.com wrote:
See pitfall #3 in this link
http://www.ibm.com/developerworks/linux/library/l-sockpit/
I cannot help with applying this knowledge to the Factor API.
--Jeff
--
*From:* Jim mack [mailto:j...@less2do.com]
*Sent:* Sunday, November 14, 2010 11:56 AM
*To:* factor-talk@lists.sourceforge.net
*Subject:* [Factor-talk] What should I call to issue [ 8080 httpd ]
in-thread again, after closing factor reopening?
reopening factor, then calling to [ 8080 httpd ] in-thread is now throwing
this kind of an error
[2010-11-14T19:53:33Z] NOTICE start-accept-loop: T{ inet6 f :: 8080 }
[2010-11-14T19:53:33Z] NOTICE start-accept-loop: T{ inet4 f 0.0.0.0 8080
}
[2010-11-14T19:53:33Z] ERROR start-accept-loop: Unix system call
E2809CbindE2809D failed:
[] ERROR start-accept-loop: Address already in use (98)
[] ERROR start-accept-loop: It was called with the
following arguments:
[] ERROR start-accept-loop: 18
[] ERROR start-accept-loop: S{ sockaddr-in6 f 10 36895
0 ~uchar-array~ 0 }
[] ERROR start-accept-loop: 28
[2010-11-14T19:53:33Z] ERROR start-accept-loop: Unix system call
E2809CbindE2809D failed:
[] ERROR start-accept-loop: Address already in use (98)
[] ERROR start-accept-loop: It was called with the
following arguments:
[] ERROR start-accept-loop: 18
[] ERROR start-accept-loop: S{ sockaddr-in f 2 36895 0
0 }
[] ERROR start-accept-loop: 16
I am on latest stable release binaries, ubuntu 10.4 lts, linode. I am
leaving the listener open in a screen. I thought I went through months of
this kind of deployment successfully, where I would just git pull in the
work folder, close restart factor + my vocab, and it would serve the
updated page.
--
Jim
I'm for extending the working Medicare program for our seniors all the way
back to contraception, so Americans can concentrate on living their lives
without fear of changing a job, going bankrupt from deductibles or fighting
HMO bureaucracy.
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
--
Jim
I'm for extending the working Medicare program for our seniors all the way
back to contraception, so Americans can concentrate on living their lives
without fear of changing a job, going bankrupt from deductibles or fighting
HMO bureaucracy.
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Git
Someone please check the following statements for accuracy: A == remote repo B == local repo C == local working directory including by definition the local repo (.git directory) 1) *clone* copies compressed files from a remote repo to a local repo,creates remote-tracking branches for each branch in the remote repository, and creates and *checks out* an initial branch forked from the cloned repository’s currently active branch. A - B - C. 2) *checkout* updates files in the working directory to match the version in the specified branch of the repo. By default, the current branch is set to the specified branch. B - C. 3) *fetch* only copies compressed files from a remote repo to a local repo. A - B. 3) *pull* *fetches* and then *merges* the fetched code into the current branch. A - B. No check-out is done; so how does the repo code get into the working directory (C)? In practice, I think our factor.cmd does a pull that puts code in the working directory, which is where the compiler goes for its source during the build. So this is not clear to me. Perhaps I don't understand what *merge* means. Pull performs A B, B C. When I work with my own hosted git repos, github, I either do pushes or pulls exclusively, and no other commands. 5) *merge* replays changes from a specified branch into the current branch. The changes are those resulting from commits in the specified branch since it diverged from the current branch. This looks like a local, repo-only operation: B - B. I think it's B' - B, then B - C 4) *push* copies compressed files from a local repo to a remote one, to update it. B - A -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] What should I call to issue [ 8080 httpd ] in-thread again, after closing factor reopening?
Except, Factor already sets the REUSE flag with setsockopt. So maybe you have
a Factor running in the background? Can you make a test case?
Doug
On Nov 15, 2010, at 2:01 PM, Jim mack wrote:
Thank you! I was looking at this more as a potential regression in factor,
but I think it more productive to look at it as my noobieness on *nx.
On Mon, Nov 15, 2010 at 10:32 AM, Jeff C. Britton j...@iteris.com wrote:
See pitfall #3 in this link
http://www.ibm.com/developerworks/linux/library/l-sockpit/
I cannot help with applying this knowledge to the Factor API.
--Jeff
From: Jim mack [mailto:j...@less2do.com]
Sent: Sunday, November 14, 2010 11:56 AM
To: factor-talk@lists.sourceforge.net
Subject: [Factor-talk] What should I call to issue [ 8080 httpd ] in-thread
again, after closing factor reopening?
reopening factor, then calling to [ 8080 httpd ] in-thread is now throwing
this kind of an error
[2010-11-14T19:53:33Z] NOTICE start-accept-loop: T{ inet6 f :: 8080 }
[2010-11-14T19:53:33Z] NOTICE start-accept-loop: T{ inet4 f 0.0.0.0 8080 }
[2010-11-14T19:53:33Z] ERROR start-accept-loop: Unix system call
E2809CbindE2809D failed:
[] ERROR start-accept-loop: Address already in use (98)
[] ERROR start-accept-loop: It was called with the
following arguments:
[] ERROR start-accept-loop: 18
[] ERROR start-accept-loop: S{ sockaddr-in6 f 10 36895 0
~uchar-array~ 0 }
[] ERROR start-accept-loop: 28
[2010-11-14T19:53:33Z] ERROR start-accept-loop: Unix system call
E2809CbindE2809D failed:
[] ERROR start-accept-loop: Address already in use (98)
[] ERROR start-accept-loop: It was called with the
following arguments:
[] ERROR start-accept-loop: 18
[] ERROR start-accept-loop: S{ sockaddr-in f 2 36895 0 0 }
[] ERROR start-accept-loop: 16
I am on latest stable release binaries, ubuntu 10.4 lts, linode. I am
leaving the listener open in a screen. I thought I went through months of
this kind of deployment successfully, where I would just git pull in the work
folder, close restart factor + my vocab, and it would serve the updated
page.
--
Jim
I'm for extending the working Medicare program for our seniors all the way
back to contraception, so Americans can concentrate on living their lives
without fear of changing a job, going bankrupt from deductibles or fighting
HMO bureaucracy.
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
--
Jim
I'm for extending the working Medicare program for our seniors all the way
back to contraception, so Americans can concentrate on living their lives
without fear of changing a job, going bankrupt from deductibles or fighting
HMO bureaucracy.
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] What should I call to issue [ 8080 httpd ] in-thread again, after closing factor reopening?
Will do. To get going, I had been running as root (which I know is bad, but
I could get it working) I am now trying to start using port forwarding, so
I'll try to make sure that isn't what's causing this.
Newbie question: I have been using screen to start factor listener. Is
there any way a factor listener could keep going, and yet not show as a
detached screen? I had assumed not, so had been relying on the presence of
a screen running factor as my test of factor already running. Now maybe
I'll learn how to use ps better. :)
On Mon, Nov 15, 2010 at 2:21 PM, Doug Coleman doug.cole...@gmail.comwrote:
Except, Factor already sets the REUSE flag with setsockopt. So maybe you
have a Factor running in the background? Can you make a test case?
Doug
On Nov 15, 2010, at 2:01 PM, Jim mack wrote:
Thank you! I was looking at this more as a potential regression in factor,
but I think it more productive to look at it as my noobieness on *nx.
On Mon, Nov 15, 2010 at 10:32 AM, Jeff C. Britton j...@iteris.com wrote:
See pitfall #3 in this link
http://www.ibm.com/developerworks/linux/library/l-sockpit/
I cannot help with applying this knowledge to the Factor API.
--Jeff
--
*From:* Jim mack [mailto:j...@less2do.com]
*Sent:* Sunday, November 14, 2010 11:56 AM
*To:* factor-talk@lists.sourceforge.net
*Subject:* [Factor-talk] What should I call to issue [ 8080 httpd ]
in-thread again, after closing factor reopening?
reopening factor, then calling to [ 8080 httpd ] in-thread is now
throwing this kind of an error
[2010-11-14T19:53:33Z] NOTICE start-accept-loop: T{ inet6 f :: 8080 }
[2010-11-14T19:53:33Z] NOTICE start-accept-loop: T{ inet4 f 0.0.0.0 8080
}
[2010-11-14T19:53:33Z] ERROR start-accept-loop: Unix system call
E2809CbindE2809D failed:
[] ERROR start-accept-loop: Address already in use
(98)
[] ERROR start-accept-loop: It was called with the
following arguments:
[] ERROR start-accept-loop: 18
[] ERROR start-accept-loop: S{ sockaddr-in6 f 10 36895
0 ~uchar-array~ 0 }
[] ERROR start-accept-loop: 28
[2010-11-14T19:53:33Z] ERROR start-accept-loop: Unix system call
E2809CbindE2809D failed:
[] ERROR start-accept-loop: Address already in use
(98)
[] ERROR start-accept-loop: It was called with the
following arguments:
[] ERROR start-accept-loop: 18
[] ERROR start-accept-loop: S{ sockaddr-in f 2 36895 0
0 }
[] ERROR start-accept-loop: 16
I am on latest stable release binaries, ubuntu 10.4 lts, linode. I am
leaving the listener open in a screen. I thought I went through months of
this kind of deployment successfully, where I would just git pull in the
work folder, close restart factor + my vocab, and it would serve the
updated page.
--
Jim
I'm for extending the working Medicare program for our seniors all the
way back to contraception, so Americans can concentrate on living their
lives without fear of changing a job, going bankrupt from deductibles or
fighting HMO bureaucracy.
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
--
Jim
I'm for extending the working Medicare program for our seniors all the way
back to contraception, so Americans can concentrate on living their lives
without fear of changing a job, going bankrupt from deductibles or fighting
HMO bureaucracy.
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Re: [Factor-talk] What should I call to issue [ 8080 httpd ] in-thread again, after closing factor reopening?
On Mon, Nov 15, 2010 at 2:26 PM, Jim mack j...@less2do.com wrote: Newbie question: I have been using screen to start factor listener. Is there any way a factor listener could keep going, and yet not show as a detached screen? I had assumed not, so had been relying on the presence of a screen running factor as my test of factor already running. Now maybe I'll learn how to use ps better. :) Are you saying that ps u | grep factor isn't showing your actual factor process? It should be there, even if it was run under screen and subsequently detached. On my Linux machine, I alias factor to dtach -n /tmp/factor.sock factor. It's a similar solution to just using screen, but dtach has a slightly different use case [1]. The main advantage dtach has over just backgrounding the process with factor is that it won't be tied to your terminal session. [1] http://dtach.sourceforge.net/ -- Aaron Bull Schaefer http://elasticdog.com/ -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Help Browser slow
Last week, it happened almost right away just browsing the docs. It happened to me twice. Today, I did a fresh install again, and I can't seem to reproduce the crash. This time I was only using Help. Before I had been interacting with the Listener, and probably ran the tetris deploy-tool test. --Jeff -Original Message- From: Slava Pestov [mailto:sl...@factorcode.org] Sent: Friday, November 12, 2010 7:36 PM To: factor-talk@lists.sourceforge.net Subject: Re: [Factor-talk] Help Browser slow Hi Jeff, We've seen this same exact crash on the build farm before, while running benchmarks. It is interesting that the help browser triggers it too. I'll try and play around with the help browser to see if I can trigger it. Do you think you can narrow down a more specific series of steps? Slava On Fri, Nov 12, 2010 at 10:40 AM, Jeff C. Britton j...@iteris.com wrote: I get the following after using the Help browser for a while. You have triggered a bug in Factor. Please report. error: 16 arg 1: 44 arg 2: f Starting low level debugger... Basic commands: q -- continue executing Factor - NOT SAFE im -- save image to fep.image x -- exit Factor Advanced commands: d addr count -- dump memory u addr -- dump object at tagged addr . addr -- print object at tagged addr t -- toggle output trimming s r -- dump data, retain stacks .s .r .c -- print data, retain, call stacks e -- dump environment g -- dump generations data -- data heap dump words -- words dump tuples -- tuples dump refs addr -- find data heap references to object push addr -- push object on data stack - NOT SAFE code -- code heap dump READY -Original Message- From: Jeff C. Britton [mailto:j...@iteris.com] Sent: Thursday, November 11, 2010 5:18 PM To: factor-talk@lists.sourceforge.net Subject: [Factor-talk] Help Browser slow On Windows XP the Browser that is opened upon clicking Help in the listener is painfully slow. For example, I clicked on Vocabulary tags, and a couple of minutes went by before the tags appeared. I then clicked on collections and another couple of minutes went by before the collections appeared. Is this normal? -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
