From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: auto-fill prefix overeager
Date: Sat, 22 Feb 2003 23:11:41 +0100 [thread overview]
Message-ID: <m3heawezj6.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <84fzqje043.fsf@lucy.is.informatik.uni-duisburg.de>
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> The problem happens when you have ">>" in a line and then type until
>>>you get to the next line.
> ^^
> See?
That's just >> plain really odd here are some more words to fill out
>> the whoops, indeed.
That's weird. Why does it do that, and how do we make it stop? I'm
not really familiar with the filling code...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-02-22 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 10:07 Kai Großjohann
2003-02-22 22:11 ` Lars Magne Ingebrigtsen [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=m3heawezj6.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).