As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
As a programming novice, I often run into trouble when trying to install packages, use virtualenv, and basically do anything even mildly complex using the command line.
What are some good references out there to help me UNDERSTAND things like my path, environment, shell scripts, etc?
Basically, I'm tired of copying and pasting. I want to really understand what's going on.
Thanks!
I used Linux in a Nutshell by O'Reilly. It helps you get past the initial beginners stage. Obviously there are a ton more links and tutorials, lists of keystrokes online, easily found with a Google search, but this will help you get going, and nice to read when you are on the bus or at lunch or whatever, to give you some ideas you might not just happen on in normal everyday life.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Having a program that has several distinct parts is usual.By part I mean a graphical part that has its own windows and functionalities.(About non graphical part, I think creating a library is the preferable solution)
How do you prefer to separate them ?
Is it better to make each of them a static library and use them in the main program?
Or the better solution is to create an executable file of each one and load them in the main program?
Or even better solution?
I suggest that you read Code Complete or something simlar. This book and others go into the best practices or even how to know which of the best practices you should look into when you create a product.
The problem is one of scope. You need to know your specifications and the parts that join together, as well as which design practices you are going to use before you can answer this question.
I am also inclined to think that there is no right or wrong answer (depending on HOW wrong you are) and that no-one else can answer that question for you, especially since you are likely to be one of the main players in maintaining the code.
Hope that gives you some food for thought :-)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
This is a genuine question, not intended to start a flame war.
I've used Vim for over 10 years; watching people use Emacs/Slime ... has made me decide to learn Emacs/Slime.
I want to get up to speed as fast as quickly:
there are a bunch of "finger macros" I instinctively do -- I want to figure out the equivalent in Emacs/Slime & retrain myself
Since I'm familiar with Clojure, writing elisp config won't be a problem (minus the dynamic vars sometimes)
What should I be reading / memorizing?
EDIT: note, I have tried VimClojure, and decided I like Slime/Swank more.
When I learn a new editor (or tool of any kind), the moment I don't know how to do something (e.g. Save a File), I google up the answer, then do it, 3x over.
In Emacs, save a file is C-x C-s. Every time you cannot remember what it is, do it three times. It'll become second nature VERY quickly.
Never "cheat" because you're in a rush, or feeling lazy. Research each command as you need it, and repeat it until it becomes a "finger macro".
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I've tried to use opengrok, lxr, cxref. no one didn't work properly or unobvious in installation and configuration. Does anyone know some easy to use tool for C/C++? And it's better if the tools knows a lot of languages.
Have you tried basic ctags?
CTags sourceforge page
OpenGrok uses ctags and requires it to be installed properly as a precondition, so it is certainly easier to install. It supports 41 different programming languages and is extremely easy to use. It's a very popular and widely used tool as it's interface is simple commandline. It integrates with vi, emacs, and similar tools.
Otherwise, you may have better luck finding answers if you post specific questions on issues you encounter while installing or using specific packages.
Another option is cscope.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
This is a bit of a silly question, but please bear with me. ;)
I just got the Code::Blocks IDE and I'm enjoying it thoroughly. However, since the : character isn't allowed in Windows folder names, I'm unsure of what to call the folder I keep all my projects in. (I name each folder after its IDE.)
Should it be written as "Code Blocks," "CodeBlocks," or something else...?
Let's see what the people who are affiliated with the project calls it.
The official name is spelled "Code::Blocks".
In the filenames in the Download section it's spelled "codeblocks".
In the page title of the Wiki it's spelled "CodeBlocks"
If you remove the "illegal" characters from the official names you get "CodeBlocks".
However, the :: indicates that they think something should separate "Code" and "Blocks".
According to this, and considering proper grammar, I think you should call it "Code Blocks". Alternatively "Code Blocks IDE".
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
I had to see what all the fuss was about Vim so tried it out for a little while; built a whole site in it. In the end I decided I was less productive.
So my question is: is Vim really that good or is it just one of those ultra-nerdy things people want to use so they can say: "I use Vim". Vim seems a little cumbersome to me. I know it's supposed to be lean but I think the years development and the mass of contributes has left it untidy. Am I wrong? Should I stick it out with Vim? What are the advantages of Vim?
How I learn to stop worrying and love VIM
Hope this helps.