This question already has answers here:
How to learn the Joy of Autotools? [closed]
(2 answers)
Closed 7 years ago.
There are automake, autoconf, autoscan, autoheader and maybe others that I don't know about. If I want to understand and use these tools, which should be the learning order? Which should be learned first? I read the man and info page, but those pages don't give me any clear clue. I can't grab the big picture from those pages.
Can anyone give me a simple explanation (maybe with example) regarding the learning order (assuming I understand C code and a little of Makefile)?
If you understand autoconf/automake and have a basic idea about libtool you don't need to know the rest.
Apart from the sites Etan mentioned there is a book (https://www.sourceware.org/autobook/ ), it is quite dated but still a useful tutorial-like introduction.
I also suggest to look at existing projects that uses autotools.
This question already has an answer here:
How can I capture terminal arrow keys in Ruby?
(1 answer)
Closed 8 years ago.
I'm trying to dynamically generate a list from file names in a directory using Ruby.
I already have all the code, but my problem is the user interface. In programs such as "testdisk" and "photorec", menu navigation is done via the arrow keys and the enter key alone, without having to type out the name of the option.
Is there a way to reproduce this behavior in a Ruby program?
Ruby Toolbox is a great resource for finding gems that you can use, the link here pointing toward the search for 'curses'.
ncurses should work with any ANSI/Posix compliant system.
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 1 year ago.
Improve this question
I am unsure what to tag this under, but I'd imagine it's a question that's relevant to most developers.
Throughout my working day, I often come across snippets of information and knowledge that will come in useful again. These may be general coding examples, or else environment specific commands etc.
Typcially, I just store these in different text files, and then refer to these text files when I am in need.
However, this is awkward and difficult to search
One alternative I've considered is creating my own local Wiki and tagging such snippets under common tags, that I can easily search.
I'd be interested to know though how other developers manage such knowledge in a "pragmatic" way.
As above, TiddlyWiki seems like the best option here
I keep my notes in a combination of Evernote and Microsoft OneNote.
Evernote takes care of most of my note-taking while reading on the web. If you set up your notebooks in an organized way, and are diligent about tagging your notes when you create them, the built-in search makes that information available anytime, anywhere. Advantages:
Can group, sort and tag in as many ways as I want
Available on all my devices
Clipping articles and snippets is a breeze on Chrome with the
add-on
Simple interface
OneNote is brilliant when I'm working on my PC; it is more feature-packed than Evernote and the ability to free-form text and to paste in any other document is awesome. Wish it had the range of availability of Evernote; I wouldn't need anything else.
There is a very good knowledge management system at that is practising typing in the right keywords in google (or bing if you prefer).
I do it many times a day and have never had the urge to save anything, or even bookmark it, as it is easy enough to find it back if required, if not through your web browser's history by typing a similar query in google.
For progamming issues you may be better of using stackoverflow.com for your searches, but stackoverflow.com results are usually on top of your search result listing anayway.
I was using TreePad for that 6 or 7 years ago and it was great. The only problem was my computer crashed and I hadn't been backing up as I should have. So now I use Google Docs. The data isn't organized in the nice way that TreePad does, but I don't have to worry about backups and it has a search capability (although I have noticed a few glitches in the search before where it didn't find something I knew was there).
This question already has answers here:
Closed 12 years ago.
Possible Duplicate:
MATLAB date selection popup calendar for gui
Does anyone know of a Calendar GUI for matlab's Guide gui system? I'd like to implement an easy user clickable date selection.
You can easily integrate several built-in date-selection (calendar) components in your Matlab GUI:
http://undocumentedmatlab.com/blog/date-selection-components/
You will need to place the relevant code in the *_OutputFcn() function within your GUIDE-generated m-file
Yair Altman
http://UndocumentedMatlab.com
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 9 years ago.
I find that one of the most frustrating aspects to software development is finding a solution to a problem, forgetting it, then being faced with the same issue in the future only to forgot how you previously solved it. Or to write a useful bit of code, then on a later project not be able to find this code.
My general question is this: How do you keep track of all the new things you learn each day while programming? Does anyone have a systematic way to capture knowledge and easily and efficiently apply it in the future?
UPDATE: Thanks the for the responses, here's what you came up with:
Social
Stackoverflow
Tumblr
Twitter
Evernote
Blogs/Wikis
Code Repositories
Github
Unfuddle
LaunchPad
Google Code
Desktop
Dropbox
Yojimbo (mac)
VoodooPad (mac)
Wikidpad (win)
Surfulater
Stackoverflow is a good place to start :-)
Keeping a blog is another thing (here's mine).
Even Twitter can be useful for this.
There are also a number of "desktop wiki" applications that I find very useful: VoodooPad on the Mac and Wikidpad for Windows.
Finally, if you need to store snippets (or more) of code (that you have the rights to, of course), then there are plenty of source code repositories available now (GitHub, LaunchPad, Google Code or Unfuddle if you want complete control).
The brain has limits. Accept it.
The solution is to have tests for your code so you can merge repeated code without breaking a sweat as soon as you notice it.
I use TiddlyWiki to keep track of a lot of things. It's a one-page, self contained wiki that you can run off your desktop, or your server.
If you want a hosted solution, you can get one for free over at TiddlySpot
I'm having this problem myself too. I've just started couple months ago by adding good SO questions/answers into my favorites, even those I answered or posted. I guess that's a good start. :)
Write a blog. Publish your findings, code samples and everything else. The best way to save the knowledge for future.
I don't care too much when I forget how I solved some problem five years ago. Chances are that in the meantime, there is a better way to do it available. GIYF.
If it is for an organisation, having internal wiki page (or something similar) could help.
If it is only for you (and anyone that's interested), write a blog, favourite snippets on internet etc.
For code, a good approach (in both cases: organisation and yourself) is to keep something I call "Utilities Library". Each piece of code I like usually fits into one of the problem scopes / namespaces of the library. This way, over time, you have a neat code base that allows you to not to invent the weel again. Of course, after couple of months or years the library needs documentation to find anything in there :)
I think Evernote is one of the best resources for storing all kinds of notes. You can even upload photos of texts (say from your iphone, or just your computer), and the text will be OCR'd, so that you can free-text search for parts of the text later.
I use Yojimbo to keep track of just about every neat algorithm, code snippet, or handy idea.
A database of notes (I use an application called Surfulater) and a directory tree of source code (also kept in a Subversion repository).
If I were to start today, I'd probably use some Wiki framework to store my notes.
I always carry around all my interesting projects with me using dropbox. Then I usually know where to find the tricks I did before.
Everytime I see something good on SO I star it, everytime I see a good article on the web I bookmark it.
Keeping a blog or a tumblr is also nice.
I am used to carry my flash disk wherever I go. So, I have different folder there for C# notes, Asp.Net notes, Design Patterns etc.
And whenever I do something that I feel I can use it in the future, basically I open the relevant Word document in it, add the details and the code snippet with a header and save.
I do not know how the others do it but it really helps me.
Do not forget to add a reference index in the beginning of your document.
P.S : I also carry all the e-books in my disk. To have them all in my pocket gives me really good feeling.
I use google reader to store all the interesting blogs and I add notes on the issues it was about.For codes strangely I always forget after having solved the issue but now I either post on asp.net forum and stackoverflow. But only strange thing happened to me couple of years ago, I had an issue and I managed to research to solve it but when I reviewed some codes I had written 3 years before I saw that I had used the same function and identical code for a similar issue. I think even if I didn't remember the code, it must have been hidden somewhere in my mind :)