Marcel: I am as we speak getting material together for a talk on emacs including stuff that vi can't do for the programmer.
I am going to cover 3 areas: - Basic tutorial - A Basic .emacsrc - A little demonstration of how Emacs can help in a programming task. ----- Original Message ----- From: Marcel Lecker <[EMAIL PROTECTED]> Date: Tuesday, June 17, 2003 11:20 am Subject: (clug-talk) July Meeting : speakers? > Hi Folks, > > Seeing as I'll be running the show for the July meeting (seeing as our > President and the secretary are heading out for a much deserved > holiday).I'm just doing a sound-off and am looking for a back-up > speaker for the July > Meeting. Rob is still on for emacs,.. I hope. Rob please confirm? > > Craig, you were going to a server security talk last month > (personally I > think that's a great topic), are you interested in being a back-up > for this > month? > > I was originally hoping to do "SSH Madness" as a back-up talk this > month (in > case Rob couldn't do his talk) but Caroline (my significant other) > will be > generally immobile and recovering from surgery that week so I'm > trying to > thin my responsibilities before and after as much as I can. > > That said, Anyone! Have a peek at the CLUG website: > http://calgary.linux.ca/index.php?CLUG%20Technology%20Presentations > for presentation ideas. If you're interested in presenting > something, it > doesn't need to be an advanced topic but needs to be related to > Linux/OpenSource software in some way and preferably has something > of interest to all > knowledge levels. > > Think about it. > > Marcel > -- > Marcel Lecker <[EMAIL PROTECTED]> > CLUG Vice President > > -------------------------------------------------------------------- > -------- > This communication is intended for the use of the recipient to > which it is > addressed, and may contain confidential, personal, and or privileged > information. Please contact us immediately if you are not the intended > recipient of this communication, and do not copy, distribute, or > take action > relying on it. Any communication received in error, or subsequent > reply,should be deleted or destroyed. > >
