From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Simple Emacs Spreadsheet
Date: Sun, 27 Jan 2008 16:56:14 +1100 [thread overview]
Message-ID: <87sl0jn75t.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: 87ve5hqnfl.fsf@system390.hermit.cave
Pete Axon <paxon@bigblue.net.au> writes:
> Does anyone know where I can get the Simple Emacs Spreadsheet? The
> home page is (according to http://emacswiki.org) here
> http://home.comcast.net/~jyavner/ses but that has been giving a 404
> for some time.
>
> Any ideas?
>
Its already part of emacs 22. Maybe upgrade to emacs 22?
Tim
--
tcross (at) rapttech dot com dot au
prev parent reply other threads:[~2008-01-27 5:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 3:24 Simple Emacs Spreadsheet Pete Axon
2008-01-26 5:16 ` Ross A. Laird
2008-01-26 5:21 ` Ross A. Laird
2008-01-26 6:58 ` Amy Templeton
2008-01-26 19:48 ` Stefan Monnier
2008-01-27 4:17 ` Pete Axon
2008-01-27 5:56 ` Tim X [this message]
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=87sl0jn75t.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
--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).