(As an aside, one thing I’ve been working on has been learning how to make modes and all the things that would go into that, and because of that I was able to “fix” a bug in php-mode, which apparently somebody has found useful and thanked me for. First time ever being thanked for fixing code, let me tell you it was really nice and inspired an extra few hours of learning. What I’m saying is that if you like the work somebody’s doing saying thanks not only makes thme feel good, it also will improve the chances of thme doing further things that will benefit you.)

One direct result of this is that I have written a short count-words-document function. All the hard work was taken care of by `karl’, he wrote the main count-words function as part of the text. But I have started to do a lot of editing of LaTeX text in emacs, so that I don’t have to deal with OOo’s obsessive desire to print my document every time I hit C-p. I can’t figure it out ;)

The wordcount function’s he wrote can count all the words in a region or a buffer, but neither of those are optimal of a LaTeXer, what with all the boilerplate my templates are accumulating. Sure, I could search for the beginning of the document, mark it, and then go to the end and pass the region to the function, but doesn’t that sound like to much work? Well, I realized that since all my templates begin with a “begin{document}” environment, and usually actually a “begin/end{singlespace}” env., that I could write a defun to just automatically deal with that, so voila:

(defun count-words-document (&optional arg begin end)
  "Without ARG, count all the words in the {document} environment
if ARG exists, count words in region."
  (interactive "P\nr")
  (if arg
      (count-words-region (prefix-numeric-value begin)
			  (prefix-numeric-value end))
    (save-excursion
      (goto-char (point-min))
      (if (search-forward "end\{singlespace\}" nil t)
	  (count-words-region (point) (progn
					(search-forward "end\{document\}")
					(goto-char (match-beginning 0))))
	(progn
	  (goto-char (point-min))
	  (if (search-forward "begin\{document\}" nil t)
	      (count-words-region (point) (progn
					    (search-forward "end\{document\}")
					    (goto-char (match-beginning 0))))
	    (count-words-region (point-min) (point-max) t)))))))

That function depends on the `count-words-region’ defun which was written by “karl” and can be downloaded, for convenience with my additional function from here. The count-words-document function if called without an argument (e.g. `M-x count-words-document’) will automatically create a region that begins, in descending order, with `end{singlespace}’, then `begin{document}’, then just the beginning of the buffer. The first two conditions will end the region at an `end{document}’ string, and the beginning of the buffer ends at the end of the buffer. So it has a nice descending order of most logical TeX regions. You can also, if you want pass it any argument (e.g. `C-u M-x count-words-document’) and it will count the words in the current region instead.

This would be nicer if it searched for variables instead of hard-coded regexes, but for now that’s for a v0.2 or something, since I don’t know how to define custom variables yet. Also, I just realized that the documentation is horribly incomplete. Anyway:

To install it, stick it in your load-path (if you haven’t got one set up, adding (setq load-path (cons ".emacs.d" load-path)) to your .emacs file will add `.emacs.d’ to your load path, just make the actual directory [that is to say, `mkdir .emacs.d'] and put the file inside it.) and add (load "wordcount") to your .emacs file somewhere below the load-path edit, and voila.

You could also set it to a shortcut key, for example I have it set to `C-c d’

(global-set-key "\C-cd" 'count-words-document)

`d’ for Document.

Technorati Tags: emacs, lisp, wordcount

And, of course, freedom-loving individual that I am, I would love collaborators (programmers, designers, eventually educators, and of course other kinds of people I haven’t thought of) on any project you can see there.

Technorati Tags: svn

#!/bin/bash
 
while [ true ]
do
    touch /media/BigEx/.keephdactive
    sleep 4m
done

Wow, right?

Yeah, it’s been kind of bothering me for months, nothing on the internet anywhere had an easy way to do this. And then, after 5-ten minutes of googling in vain all of a sudden I thought to myself: “Hey man, you’re supposed to be a computer scientist, (tbd) can’t you do something about this?” And so, in less time than several failed google searches, I had this.

If you’re on linux and you want to get this running, copy & paste the following into your terminal. It will open up your text editor, inside of which you should change the “BigEx” to the name of your external hard drive. (What it shows up as in the menus and such.) These commands will just put it in your home folder, at the end there’s a command to move it out of there, if you don’t know how.

If you’re in GNOME (eg Ubuntu):
wget http://svn.quodlibetor.com/pubsh/bash/hdactive.sh && gedit hdactive.sh && chmod +rx hdactive.sh

If you’re in KDE (eg Kubuntu, Fedora 9):
wget http://svn.quodlibetor.com/pubsh/bash/hdactive.sh && kate hdactive.sh && chmod +rx hdactive.sh

The only difference between them is a different text editor. (The “&&”s are just ways to join multiple commands together in one line, I did it so that you won’t have to copy/paste 3 times just to get a little hack working :)

Last thing to do then is run it:

./hdactive.sh &

should do it. (The “&” just means “run this process in the background.”)

If you’re in GNOME and you want this file to run every time you start your system, first it’s probably a good idea to put it in your /usr/bin directory:

sudo mv hdactive.sh /usr/bin/

And then you’ll want to add it to your startup session, which is something I don’t know a command for, or how to do it in KDE, so menus time: “System -> Preferences -> Sessions” select “+ add” from the right side, for the name put “HDactive” (or whatever) for the command put “hdactive.sh” (no quotes) and for comment put “oh man quodlibetor’s friggin’ sweet.”

That last part is essential for the proper working of the code :)

OK, it’s now officially been an hour and fifteen minutes since I thought “damn I wish my hard drive would stay on.” On the one hand, that’s way too long, on the other hand, my hard drive has stayed on :)

p.s. I know that there are at least a couple things to do to make this work better (eg accept parameters instead of making people change the code by hand) this works for me, and it’s also damn near my first working bash script ever, so I’ll change it as I have time. I promise that the link will always work though, and if I change it enough that these instructions don’t apply any more I’ll put comments inside it so anybody trying to edit a newer version will see that something’s weird and what to do about it. You can consider it currently licensed under the WTFPL, so do wtf you want to with it :)

[edited a whole bunch of times to get some basic code formatting and syntax highlighting working, since this is my first post with actual code]

Technorati Tags: bash, hardware, howto, linux, script