Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: prad <prad@towardsfreedom.com>
To: info-gnus-english@gnu.org
Subject: Re: author of post and signature problems
Date: Tue, 28 Dec 2010 12:10:37 -0800	[thread overview]
Message-ID: <8762udk69u.fsf@towardsfreedom.com> (raw)
In-Reply-To: <ifdcot$g68$1@quimby.gnus.org>

Richard Riley <rileyrg@googlemail.com> writes:

> Possibly try doing a delayed post or "unplugged". That might show you if
> its Gnus or the server.

hi richard!
nice to hear from you especially since it was primarily your post on
emacs.help that prompted me to go with gnus!

this isn't a big deal as far as posting since i already know how to
by-pass the problem. i'm just trying to find out what the significance
of gnus-signature-limit variable is. i also have only tried this on
gmane.emacs.gnus.user
gmane.test

i've see some people set it to 500 or do stuff like:
(setq gnus-signature-limit '(200.0 "^------Forward"))
which apparently means that if there are more than 200 lines or there
is that forward line it shouldn't be considered a sig. none of this
worked for me - it's like the line limit of 4.0 is hardwired into gnus. :D

possibly the sig-limit variable is used to handle other people's posted sigs?

the forward matter can particularly be an issue i guess since i like to
introduce forwarded text with a short blurb followed by my sig.

in any case, i'll move on with something else since this is a really fun
software to explore! however, if you or anyone can provide further
insight into the sig-limit variable, it will always be appreciated.

--
In friendship,
prad

                                      ... with you on your journey
Towards Freedom
http://www.towardsfreedom.com (website)
Information, Inspiration, Imagination - truly a site for soaring I's

  reply	other threads:[~2010-12-28 20:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.31.1293525612.2341.info-gnus-english@gnu.org>
2010-12-28 10:21 ` Massimo Gengarelli
2010-12-28 14:36 ` Adam Sjøgren
2010-12-28 18:12   ` prad
     [not found]   ` <mailman.7.1293559906.18542.info-gnus-english@gnu.org>
2010-12-28 19:06     ` Adam Sjøgren
2010-12-28 20:19       ` prad
     [not found]       ` <mailman.3.1293567513.3661.info-gnus-english@gnu.org>
2010-12-28 21:25         ` Adam Sjøgren
2010-12-29 14:48           ` Philipp Haselwarter
2010-12-30 19:13             ` prad
2010-12-28 19:11     ` Richard Riley
2010-12-28 20:10       ` prad [this message]
     [not found]       ` <mailman.2.1293566991.3661.info-gnus-english@gnu.org>
2010-12-28 20:31         ` Richard Riley
2010-12-28 21:40         ` despen
2010-12-28 23:39           ` prad
     [not found]           ` <mailman.0.1293579503.26585.info-gnus-english@gnu.org>
2010-12-29  1:49             ` despen
2010-12-29  7:12               ` prad
2010-12-28 20:18     ` David Brown
2010-12-28 20:32       ` Richard Riley
2010-12-31  0:59   ` Brett Viren
2010-12-28  8:33 prad

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=8762udk69u.fsf@towardsfreedom.com \
    --to=prad@towardsfreedom.com \
    --cc=info-gnus-english@gnu.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).