Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
there is bunch of repl in clojure ?
lein repl
cursive clojure repl plugin inteljidea
gorilla repl newly launched
cider for emacs
is anybody having idea which one is good?
Practically all Clojure REPLs mentioned are based upon nREPL, and as such have the same backend functionality. The choice of REPL client frontend is usually driven by usecase:
Minimal REPL only needing JVM and Clojure jar, no nREPL client-server structure or leiningen project.clj integration:
Clojure REPL launched by java -cp clojure.jar clojure.main
Quick commandline checks or lightweight install for connection from commandline only systems:
lein REPL, which uses REPL-y as frontend
Working from the IDE of your preference:
Cider (based on Emacs)
Cursive (based on Intellij)
Counterclockwise (based on Eclipse)
Need for iPython notebook like interactive UI and persistence, graphical plots
Gorilla REPL
Session
Client maturity and functionality within these categories differ little, and are user preference based. However, choosing the right type of REPL by usecase makes all the difference, which is why most Clojure users switch between them when needed.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 5 years ago.
Improve this question
I have created Django python web app .How to add it to github am new to both of these and have searched web for somedays without any luck.
Recommend you to look into tutorials, following code is a pointer.
git init
git add .
git commit -m 'First commit'
git remote add origin <github repo link>
git push origin master
I don't want to confuse you since your new to both Git and Django. So this is what I would say.
You should understand and learn git first (before continuing with Django or any other language). It's not very difficult and I would recommend doing a free 2 hours course on Codecademy. Simply know that Git is an essential now days and is used for everything.
Django doesn't require Git but a good practice, you could continue without it but at somepoint in the future you probably will have to learn Git. So learn Git first and it's not difficult to learn.
Just understand the concept of Git and why we use it.
Learn how to use Git and things will start to make sense to you. Practice and you will understand the concept and the purpose behind it.
Hope that helps.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 7 years ago.
Improve this question
Version: 8.0
It was working and all of sudden it started throwing this error.
Update Note: After installing fresh install of site core instance , it worked fine and I have created outside project to built site specific templates and used publish option visual studio to deploy outside project files to the site core website folder. It started failing.
Well it's really hard to answer without details, but I would suggest you to replace the bin of your website from a fresh Sitecore 8.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I need to create setup.exe for my abc project (written in c++).
Before running the setup.exe i need to create and set the environment variable to some value.
Is it possible to add custom action of "creating and set the value of environment variable"
in the installer and if yes then how.
I'm using VS 2012 and Installshield.
Thanks
You don't describe your root problem but I can give you advice on environment variable race conditions I've had in the past. Typically I'll have my installer use standard techniques (Windows Installer Environment table which updates the registry and broadcasts a settings change) and then if still have a race condition for custom code running in the installer I'll have the custom action set the environment for the process to work around the issue. This way the permanent change is done correctly and a temporary change is injected to make the custom action happy.
The two most commonly seen race conditions are:
1) Variations of a child process hosted by a windows service doesn't get the settings change message due to service control manager behavior
2) A pending reboot causes MSI to not send the settings change message. In this scenario it is also possible to write a custom action that does nothing but send the message after the standard action has done it's work.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I’m using a Ubuntu VPS to host a couple of Ring web apps. I have a separate GNU Screen window for each one, and I start and stop them using lein run and ^C, respectively. This works, but it feels amateurish and if anything goes wrong these services won’t be restarted automatically.
I’d like to set something up so that I can start and stop my apps using Ubuntu’s service command (which I already use to start and stop nginx). Is there some kind of shortcut I can use to get these apps working with the service command? For example, is there some Leiningen- or Ring-friendly template into which I can just insert my application’s path? Failing that, what would be the best practices for writing my own service script to integrate with Jetty?
It depends on whether you want your service to run straight from your project directory, or whether you want to go through the intermediate step of creating and installing a build artifact.
Certainly during development it's more convenient to use lein run from your project directory. For the sake of repeatability, I'd recommend using the second approach for production systems.
The general approach would be to use the lein uberjar task to create a stand-alone JAR file. From there, it's pretty straightforward (though somewhat tedious) to create a script you can stick in /etc/init.d to run the JAR file, either directly via java or using jsvc.
It looks like there's a Leiningen plugin (lein-init-script) to automate the process of generating the service script, though I don't have any experience with it. You'll probably want to check that out.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 6 years ago.
Improve this question
I do not know anything in Siebel. But we have a requirement that I need to comment one line of code in one of the applet scripts and build a new SRF. What is the procedure? I am using Siebel 6 and I have access to Siebel tools.
Also let me know any useful sites for help on Siebel 6.
You should have your local repository connected to a server repository so you can check out and check in your changes to the server repository. If you are not worried about check outs and check ins then you can do the following. Otherwise you have environment setup steps to perform before commenting out the code.
If you know the applet where the script is located, then search and right click that applet in Siebel Tools. Select Edit Server Scripts (if not there then choose the option Edit Browser Scripts). Find the line of code and prefix with //. Ctrl S to save the changes. That line of code should turn green.
Now the changes are in your local repository. You should put a SRF file from your server environment on your local machine. Right click your applet and select Compile Selected Objects and choose the file that you copied to your local machine.
Now your change has been compiled into the SRF that originated from the server and is ready to be deployed to your server for testing. You will have to shutdown, move the srf, and restart siebel services before being able to test your changes.