Gnus development mailing list
 help / color / mirror / Atom feed
From: Deepak Tripathi <deepak@gnumonk.com>
To: ding@gnus.org
Subject: Re: gnus long line break while reply.
Date: Sun, 05 Jun 2011 16:54:40 +0530	[thread overview]
Message-ID: <87r5784j2f.fsf@gnumonk.com> (raw)
In-Reply-To: <m3mxhy7ehk.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 04 Jun 2011 00:10:47 +0200")

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]


lars, 
that's not working properly, see before and after using 'W w'.
before
,----
| > I discovered by accident that nnimap article editing works.  At
| least
| > kinda works... the article was edited, but the summary buffer and
| the
| > tick marks were confused afterwards.
`----
after
,----
| > I discovered by accident that nnimap article editing works.  At
| least kinda works... the article was edited, but the summary buffer
| > and
| the tick marks were confused afterwards.
`----
 

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Deepak Tripathi <deepak@gnumonk.com> writes:
>
>> How gnus treat long line break, so if somebody replayed to me i get
>> something like this
>
> I use `W w' on the article before following up, which usually breaks
> stuff sensibly.

-- 
,----
| Life's Too Short, Write Fast Code, Use emacs :) 
| Deepak Tripathi(gnumonk)
| irc: irc.debian.org | nick: deepak, gnumonk
| irc: irc.freenode.com | nick: gnumonk
| web: http://www.gnumonk.com 
`----

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2011-06-05 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 17:24 Deepak Tripathi
2011-06-03 22:10 ` Lars Magne Ingebrigtsen
2011-06-05 11:24   ` Deepak Tripathi [this message]
2011-06-26 10:10     ` Lars Magne Ingebrigtsen

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=87r5784j2f.fsf@gnumonk.com \
    --to=deepak@gnumonk.com \
    --cc=ding@gnus.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 NNTP newsgroup(s).