Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Switch to your preferred Unix-like OS (BSD or Solaris is probably better than Linux for this--most people have heard of Linux) but get rid KDE, GNOME or any other friendly desktop environment. Instead, run your preferred window manager (something that looks nothing like Windows or MacOS is better) and use xterms for all your actual interactions. Use lynx as your web browser and mutt as your mail client. (Or if you must use Firefox/Thunderbird, find the most outlandish and confusing theme and set of extensions you can find.)
Then, when somebody asks to use your laptop, just say "Sure, go ahead. This runs $FREE_OS, though, which may not be what you're used to." If they ask for help, tell them which man page they need to read to get the answer.
After three or four iterations of this, nobody will bother you anymore.
(Also, it's a good idea to set up a guest account and some way to to it, just in case you meet somebody who knows Unix. See other posts in this thread for more suggestions.)
I just downloaded it and played with it for a few minutes. Some comments:
- I don't think your license actually meets the criteria for open-source. It isn't clear to me that I legally could create a fork of Sandbox and distribute it under the same terms. I'd be much happier if you used a well-known open-source license (e.g. the GPL) instead.
- I also don't how your license claims the copyright of any submitted changes. A more suspicious mind might think you're trying to build a base of contributor games that you can then commercialize. If that isn't your plan, I suggest you change the terms to make that clear. Once again, using a well-known OSS license would solve the problem.
- Aside from that, I think this is a really neat idea for teaching kids to think like programmers.
The really nice thing about query-replace and query-replace-regexp is that you can replace almost all items. It's great for cases where, say, you want to replace all uses of variable "count" while leaving the word alone when it's used in a comment.
If you just want to replace everything, you use the non-query versions, replace-string and replace-regexp. That way, you don't need to hold down the 'y' key.
When I googled to see what the vi "." did, I found this, so the answer is no, but you can download an extension to do it.
But what I was going to say was that there are two options that I can think of:
- If you typed in the command at the M-x or M-: (lisp eval) prompts, you can always just use the command history and rerun the command that way.
- Alternately, you can repeat the next command by typing C-u and the number of repetitions followed by the command. So "C-u 75 -" will draw a row of 75 dashes. You can do more complex things by first recording a keyboard macro ("C-x (", keystrokes, "C-x )" and then prefexing the macro eval command ("C-x e") with a repeat count. If you're afraid of going past a certain point and don't want to carefully figure out exactly how many times to repeat, you can use narrow-to-region first.
Those two things, along with query-replace, automates most of my tasks for me.