From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Missing the save index option (patch attached)
Date: Sun, 17 Jan 2010 11:12:24 -0500 [thread overview]
Message-ID: <1263744728-sup-405@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1263741896-sup-8418@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 440 bytes --]
Excerpts from William Morgan's message of Sun Jan 17 10:25:59 -0500 2010:
> (Also has the nice side-effect of making '$' not go to the bottom of the
> screen, which was driving me batty.)
Yes, that has been hard for me to unlearn too.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-01-17 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 12:36 Israel Herraiz
2010-01-17 15:25 ` William Morgan
2010-01-17 16:12 ` Ben Walton [this message]
2010-01-17 23:22 ` William Morgan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1263744728-sup-405@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=sup-talk@rubyforge.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