Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: auto-filling has been broken -- excessive indentation
Date: Fri, 17 Aug 2001 18:38:36 +0200	[thread overview]
Message-ID: <m366bmzlo3.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vxkelql17cp.fsf@cinnamon.vanillaknot.com>

Karl Kleinpaste <karl@charcoal.com> writes:

> No.  'Twas not me.  Perhaps not a bad idea, but at the moment,
>      whatever it is that's going on is just plain wrong.
>
> Offhand, I don't even understand the correlation between TAB binding
>          and auto-fill indentation.  I'm not using TAB.  I'm just
>          typing text, and letting auto-fill do its thing.

It seems to work OK for me -- it only starts auto-indenting stuff if
I've pressed TAB first...

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen


  reply	other threads:[~2001-08-17 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 13:46 Karl Kleinpaste
2001-08-09 16:37 ` Kai Großjohann
2001-08-09 17:16   ` Karl Kleinpaste
2001-08-17 16:38     ` Lars Magne Ingebrigtsen [this message]
2001-08-17 17:18       ` Kai Großjohann

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=m366bmzlo3.fsf@quimbies.gnus.org \
    --to=larsi@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).