Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Christer Edwards <cedwards@zelut.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] tiny patch re: editor (vim)
Date: Wed, 16 Feb 2011 10:34:39 -0700	[thread overview]
Message-ID: <1297876563-sup-2003@daphne> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1175 bytes --]

I've always been told that email text length should be limited to 72
characters. I did some more research this morning in preparation for
sharing this and I find that according to RFC 2822 it should be 78
characters. I then continue to find more and more discussion about how
it "doesn't matter" or "use whatever you want".

In any case, below is a tiny patch to configure vim to wrap text at 72
characters. This patch is specific to the initial file that is used at
sup-config, but the same line could be edited in your local
.sup/config.yaml.

In any case, see the example below to configure your textwidth.


--- lib/sup.rb  2011-02-16 09:08:19.373333347 -0700
+++ lib/sup.rb.new  2011-02-16 09:20:07.816666681 -0700
@@ -289,7 +289,7 @@
             :gpgkey => ""
           }
         },
-        :editor => ENV["EDITOR"] || "/usr/bin/vim -f -c 'setlocal spell spelllang=en_us' -c 'set filetype=mail'",
+        :editor => ENV["EDITOR"] || "/usr/bin/vim -f -c 'setlocal spell spelllang=en_us' -c 'set filetype=mail' -c 'set textwidth=72'",
         :thread_by_subject => false,
         :edit_signature => false,
         :ask_for_from => false,

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

             reply	other threads:[~2011-02-16 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 17:34 Christer Edwards [this message]
2011-02-16 18:35 ` Matias Aguirre
2011-02-16 18:42 ` Ico Doornekamp
2011-02-16 19:08 ` Ben Walton

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=1297876563-sup-2003@daphne \
    --to=cedwards@zelut.org \
    --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