From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Where to get the .gnus for this screenshot?
Date: Mon, 23 Jan 2006 12:32:40 +0100 [thread overview]
Message-ID: <v98xt741t3.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87mzhnbai4.fsf@nowhere.org>
On Mon, Jan 23 2006, Glyn Millington wrote:
> Not sure about the dashed seperator - is that, maybe, just how GNU
> Emacs does it?
,----[ M-x apropos-variable RET gnus.*boundary RET ]
| gnus-body-boundary-delimiter
| Variable: String used to delimit header and body.
| gnus-treat-body-boundary
| Variable: Draw a boundary at the end of the headers.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-01-23 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 2:27 leon
2006-01-23 8:42 ` Glyn Millington
2006-01-23 11:32 ` Reiner Steib [this message]
2006-01-23 13:14 ` Steve Youngs
2006-01-23 14:04 ` Reiner Steib
2006-01-25 17:33 ` leon
2006-01-27 14:57 ` Reiner Steib
2006-01-25 17:37 ` leon
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=v98xt741t3.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).