unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: secretary@lxny.org
To: help-gnu-emacs@gnu.org
Subject: NYC LOCAL: Tuesday 10 June 2008 Two Separate Meetings: Lisp NYC and Python NYLUG
Date: 9 Jun 2008 21:32:29 -0400	[thread overview]
Message-ID: <g2kljd$dku$1@panix5.panix.com> (raw)

There will be two separate meetings on Tuesday 10 June 2008.
Lisp NYC will meet and so will Python NYLUG.  Note that these
meetings are regular.  Lisp NYC meets the second Tuesday of the
month, and Python NYLUG meets every other Tuesday.

http://lispnyc.org
http://nylug.org

Below are the two official notices.

Jay Sulzberger <secretary@lxny.org>
Corresponding Secretary LXNY
LXNY is New York's Free Computing Organization.
http://www.lxny.org


<blockquote
  what="two official announcements, Lisp NYC and Python NYLUG">

 Subject: [Lisp] Lisp Meeting: June 10th 7:00 at Westside
 From: Heow Eide-Goodman <lists@alphageeksinc.com>
 Date: Mon, 09 Jun 2008 13:43:19 -0400

 Please join us for our next social meeting on Tuesday, June 10th from
 7:00 to 9:00 at Westside Brewery 340 Amsterdam Ave  (From the 1,2,3,9:
 between 76th-77th on Amsterdam)

 Cheers,

 - Heow

 P.S.  Sorry this is going out by hand.  Thorn-in-my-side-Mailman was
 just "upgraded" and now it can't read it's own files.  Sigh.

 -- 
 ;;--------------------------------------------------------------------------
 (let ((m '(("woeH" "@" "cnIskeeGahplA" "." "moc") 
            ("woeH" "@" "CYNpsiL" "." "gro"))))
  (apply 'concatenate 'string (mapcar #'reverse (nth (random (length m)) m))))


 < end Lisp NYC notice ; begin Python NYLUG notice />


 From: NYLUG Announcements <info@nylug.org>
 To: NYLUG Announcements <nylug-announce@nylug.org>
 Date: Mon,  9 Jun 2008 11:26:36 -0400 (EDT)
 Subject: [nylug-announce] NYLUG Python Workshop, (tomorrow) 6:00PM-8:00PM

 This is a reminder for the event detailed below.

 PYTHON WORKSHOP
 Date: Tuesday, June 10, 2008
 Time: 6:00pm
 Duration: 120 minutes

 Topics:
   General discussion about Python, and another look at David Bristow's
   pygame experiments.  Bring something to discuss! There's a blackboard,
   chalk, and Internet access.

 Description:
   We will continue meeting on a bi-weekly basis at the Hudson Library at
   66 Leroy St New York, NY 10014.

   It is helpful, but not necessary to have a notebook computer.          
   The WiFi at the library works now.                       

 Map & Directions:
   http://maps.google.com/maps?q=The+Hudson+Library+at+66+Leroy+St+New+York%2C+NY+10014&hl=en
   (http://tighturl.com/fp)

   We meet in the basement. Enter the library and head to the back. If the
   door is closed when you arrive you can ask the manager of the library for
   the keys to the room if you're comfortable opening up the basement, or
   you can wait for some of the others to arrive.
 ______________________________________________________________________
 Hire expert Linux talent by posting jobs here :: http://jobs.nylug.org
 nylug-announce mailing list nylug-announce@nylug.org
 http://nylug.org/mailman/listinfo/nylug-announce
  
</blockquote>


                 reply	other threads:[~2008-06-10  1:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='g2kljd$dku$1@panix5.panix.com' \
    --to=secretary@lxny.org \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).