@plbogen and @m_steph_m and I have been tweeting about learning command line stuff. We would like to have a shell tutorial! I asked for links to help, and here’s what I got:

• bit.ly/8MydsF: http://linuxcommand.org
• bit.ly/k0IlR: FREEENGINEER.ORG
• bit.ly/MEKoYD: Bash Guide for Beginners
• bit.ly/yU4AKH: The Command Line Crash Course

Who can GIVE a shell tutorial?

Who wants to TAKE a shell tutorial?

N.B. If no one can (or is willing to) give a shell tutorial, I would be happy to have a working session choosing one of the docs linked above and working our way through it as a collaborative group of beginners!

Comments?

Having recently retooled my DevonThink setup yet again, I’m finding that I’m still dissatisfied. My regular everyday worktools include:

• DevonThink, really, pretty much I use it as a better finder
• Omnifocus for task management
• Mellel for wordprocessing
• Bookends for citations
• Scrivener for writing
• My blog is on WordPress
• Google Apps for collaboration

I’m happy to talk about what I love and hate about each of these, for example, I love Bookends’ integration with Mellel and hate how clunky it is. I love almost everything aout WordPress except actually composing posts. I want DevonThink and Omnifocus to TALK to each other. And more… I’d love for other folks to talk about how they do their workflows.  And to tell me why using Oxygen is such an uphill battle? In addition, I just upgraded my OSX to Lion and am curious if anyone has found awesome things that Lion can do that they want to share.

P.S. Other things I’d love to talk about include Islandora, teaching oneself to code, learning to work with the command-line after being a GUI person forever, and and and… they go on. Okay, calling this post “one more” might have been misleading…

Using GIT
I “get” GIT–I see the utility–I see the logic–I see why it’s great. But I’d love some discussion on how to start using it, what are some preferred GIT clients, and what the best-GIT-practices are. If this conversation could be combined with a western-twanged series of puns on the word “git,” that would be ideal.

Digital Scholarly Editions
This is my main DH interest at the moment. I would love to talk about:

• Issues of encoding
• What software platforms people are using (Islandora, Omeka, by-hand?)
• Excellent, and execrable, examples of digital scholarly editions
• Issues of copyright (i.e. “Do ALL digital editions have to be out of copyright???”)
• What kinds of scholarly apparatus do digital editions facilitate that were harder or impossible in paper editions?
• Multi-media digital editions

Working without institutional infrastructure
AKA, when you’re more alt than ac
For the many of us who are still on the hunt for the permanent position, how do we think about the issues of our digital work differently? For example, in a workshop I was once in, someone said: “This is what you’ll need to tell your design team…” What about when we ARE our team? What are the dangers of developing digital tools, editions, creations of any kind on resources provided by a university where you are only a temporary employee? How do we access resources? How do our grant applications differ? How do we access the support systems we need to make our work…work?