From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: Ugly line of dashs
Date: Sat, 12 Jan 2002 08:40:01 -0500 [thread overview]
Message-ID: <vxku1trit72.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <iluvge7lsqt.fsf@extundo.com> (Simon Josefsson's message of "Sat, 12 Jan 2002 12:21:30 +0100")
Karl Kleinpaste <karl@charcoal.com> writes:
>> I find (setq gnus-body-boundary-delimiter "_") to be better, visually.
Simon Josefsson <jas@extundo.com> writes:
> This is the default, actually.
Curious...It didn't default to that a week or so ago, when I first
noticed it (and didn't like it that way).
next prev parent reply other threads:[~2002-01-12 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 2:29 Harry Putnam
2002-01-12 2:58 ` Henrik Enberg
2002-01-12 3:42 ` Karl Kleinpaste
2002-01-12 3:50 ` Steve Youngs
2002-01-12 6:06 ` Harry Putnam
2002-01-12 10:22 ` Pavel Janík
2002-01-12 11:21 ` Simon Josefsson
2002-01-12 13:40 ` Karl Kleinpaste [this message]
2002-01-12 13:42 ` Lars Magne Ingebrigtsen
2002-01-12 15:39 ` Harry Putnam
2002-01-12 15:50 ` Lars Magne Ingebrigtsen
2002-01-14 18:30 ` Wes Hardaker
2002-01-14 18:34 ` Lars Magne Ingebrigtsen
2002-01-14 21:20 ` Wes Hardaker
2002-01-14 23:17 ` Raja R Harinath
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=vxku1trit72.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.com \
/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).