Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Stanislav Ochotnicky <sochotnicky@redhat.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] vim text wrapping
Date: Thu, 17 Mar 2011 16:14:13 +0100	[thread overview]
Message-ID: <1300374660-sup-1025@sochotnicky.usersys.redhat.com> (raw)
In-Reply-To: <1300371571-sup-2777@plc.intranet.plecavalier.com>


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

Excerpts from Philippe LeCavalier's message of Thu Mar 17 15:26:51 +0100 2011:
> Hi All.
>
> This is more of a vim question than it is a sup one but I'm not a
> member of the vim list so I thought I'd ask you guys first.

Really not a sup question at all, but I have no problem trying to
answer. Others might feel different though :-)

> Since I don't write very well I always end up making changes while
> re-reading myself. When I edit a line Vim doesn't wrap anymore like it
> did when I first typed the text. So all the lines I've edited aren't
> wrapped like the others. It can make reading my mail challenging at
> times.

How about "gqq"? Also "set nopaste" and "set textwidth=72" should be
of help most of the time.

> Perhaps I'm misunderstanding how to properly edit text in vim?

Nah, vim might look like a simple editor but it has more features than
most people would believe :-)

--
Stanislav Ochotnicky <sochotnicky@redhat.com>
Software Engineer - Base Operating Systems Brno

PGP: 7B087241
Red Hat Inc.                               http://cz.redhat.com

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 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-03-17 16:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 14:26 Philippe LeCavalier
2011-03-17 15:14 ` Stanislav Ochotnicky [this message]
2011-03-17 15:33 ` Paul Grove
2011-03-17 16:10   ` James Taylor
2011-03-17 15:40 ` Tyberius Prime
2011-03-17 15:52 ` Bruno d'Arcangeli
2011-03-17 16:04 ` Erin Sheldon
2011-03-17 16:05 ` Peter Lewis
2011-03-17 16:12 ` Amadeusz Żołnowski
2011-03-17 16:47   ` Matthieu Rakotojaona
2011-03-17 16:19 ` Ico Doornekamp
2011-03-17 18:14   ` Philippe LeCavalier
2011-03-18 13:56     ` Philippe LeCavalier
2011-03-17 16:23 ` pancho horrillo
2011-03-17 17:46   ` Bruno d'Arcangeli

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=1300374660-sup-1025@sochotnicky.usersys.redhat.com \
    --to=sochotnicky@redhat.com \
    --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