I’m just another hacker, working mostly in C++, and now Java. I’m learning elisp so I can hack emacs. bug.el is my first module, but it’s a life saver. It’s safer than simply building an emacs macro to execute ant, since on a project with multiple branches, you can’t always guarantee which project version you will accidentally compile when a macro fires off! And it’s easier than returning to your project root folder to find the build.xml manually, since, if you are like me, you eventually end up with tens of buffers, and navigating between them can be very painful…
I suppose die hards can still use the console… but just try jump to the first error message. I dare ya!
For the bug-is-root function, I think you could simply use file-name-absolute-p, rather than grovelling the file name yourself.
I don’t think that’s quite what I want. file-name-absolute-p will tell me if my pathway is absolute, but not whether I am at the root. For example, both (file-name-absolute-p “/usr/local/bin”) and (file-name-absolute-p “/”) return true. Unfortunately, (pwd) returns “Directory /” and not simply “/”. That’s why I had to split and tokenize the output. I admit, it is a bit of a hack. --Jason
Added slurp.el. A handly tool to slurp up files from a hierarchy.
Added fetch.el. A tool to search for and open Java classfiles from within a package hierarchy. It’s similar to the hyperlink feature found in Eclipse.
Thanks! I’m already aware of that, but it seems a bit too… heavy, for my tastes. Besides, since I’m new to Lisp (end ELisp) I need useful projects to play with.
hi, just noticed your fetch.el. There is already another file called fetch.el (authored by me). – deego
I did not see your fetch in the list. Where is it? --Jason
Cool! Two fetches that do completely different things. If you decide to post your sources here, then we can make fetch.el an index page that links to both our libraries. Share the Internet, I say. .
I must be dense… Are you asking me to rename my program? When I posted originally there was no module called fetch in the elisp listing so I figured the name was fair game. If you want to post your fetch in lieue of mine, then feel free. I won’t stop you.
I have taken the liberty to delete fetch2 and added it’s content to fetch.el again. The other library by this name does not to appear to be available at them moment anyways. However I have added a not about the other fetch.el to the header anyway. And while I was at it, I also improved the header to follow the conventions. I have also added a not that I adapted the file, but feel free (I would welcome it!) that note.
The main reason that I did this is however that I am currently trying to remove all foo.el files from the wiki that do not actually contain any emacs lisp code.
Hope that doesn’t cause any bad feelings JonasBernoulli