From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] tiny patch re: editor (vim)
Date: Wed, 16 Feb 2011 14:08:40 -0500 [thread overview]
Message-ID: <1297883154-sup-7252@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1297876563-sup-2003@daphne>
Excerpts from Christer Edwards's message of Wed Feb 16 12:34:39 -0500 2011:
Hi Christer,
> In any case, see the example below to configure your textwidth.
Your patch looks fine, but I question why we would do anything other
than call vim in the default case? Passing default settings like this
(including the existing options) should be beyond the scope of the
mail client in my opinion.
That being said, if others like the patch, by all means apply it. I
don't use vim and I specifically configure my environment so it won't
affect me. :)
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-02-16 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 17:34 Christer Edwards
2011-02-16 18:35 ` Matias Aguirre
2011-02-16 18:42 ` Ico Doornekamp
2011-02-16 19:08 ` Ben Walton [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1297883154-sup-7252@pinkfloyd.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