From: D. Goel <deego@gnufans.org>
Subject: Re: ges.el v. 0.0
Date: 27 Oct 2002 21:29:07 -0500 [thread overview]
Message-ID: <87k7k3thxo.fsf@computer.localdomain> (raw)
In-Reply-To: uxhef8ylvs.fsf@computer.localdomain
While I was downloading various author's files and testing them, I
didn't test my own!
Now, ironically, I realize that whereas I was ranting about
guidelines-for-authors on g.e.s, almost the only posts that do not
currently play well with ges.el's automation are my own... I will
change the format of my future posts to be ges-compliant. :)
And also improve ges.el somewhat..
DG http://deego.gnufans.org/~deego/
--
All my comments/code posted are FDL/GPLed and hence may be
freely incorporated into FDLed wikis or GPLed libraries.
prev parent reply other threads:[~2002-10-28 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uxhef8ylvs.fsf@computer.localdomain>
2002-10-27 22:53 ` ges.el v. 0.0 Cyprian Laskowski
2002-10-28 3:01 ` D. Goel
2002-10-28 2:29 ` D. Goel [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=87k7k3thxo.fsf@computer.localdomain \
--to=deego@gnufans.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).