Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Gnus <ding@gnus.org>
Subject: Re: gnus bug reports go to wrong address
Date: Fri, 1 Jul 2011 12:29:23 -0500	[thread overview]
Message-ID: <87fwmpgb9o.fsf@lifelogs.com> (raw)
In-Reply-To: <19982.592.46793.378382@fencepost.gnu.org> (Glenn Morris's message of "Fri, 1 Jul 2011 13:22:24 -0400")

On Fri, 1 Jul 2011 13:22:24 -0400 Glenn Morris <rgm@gnu.org> wrote: 

GM> Ted Zlatanov wrote (on Fri, 1 Jul 2011 at 12:15 -0500):

>> What's wrong with this message?  This is what's getting sent right now.

GM> Nothing is obviously wrong with that (if the blank line is your header
GM> separator). 

OK, good.

GM> But the examples I quoted do not look like that. Eg

GM> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8972

GM> I guess you somehow need to make it clear people should start typing
GM> _after_ the boilerplate, not before. Maybe you could make it look like:

GM> -- headers end --
GM> Package: gnus
GM> Version: blah

GM> Describe your problem: <cursor positioned here>

GM> No Gnus v0.18
GM> GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.4)
GM>  of 2011-07-01 on tzlatanov-ubuntu-desktop

Oh, I see.  Would it be better to make that text uneditable and
unmovable in addition to moving the cursor?

Alternatively, can we set a header instead of the pseudo-header?

Ted



  reply	other threads:[~2011-07-01 17:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 16:22 Glenn Morris
2011-07-01 17:15 ` Ted Zlatanov
2011-07-01 17:22   ` Glenn Morris
2011-07-01 17:29     ` Ted Zlatanov [this message]
2011-07-01 17:32       ` Lars Magne Ingebrigtsen
2011-07-01 17:45       ` Glenn Morris
2011-07-01 19:02         ` Ted Zlatanov
2011-07-01 19:33           ` Glenn Morris
2011-07-01 19:37             ` Ted Zlatanov
2011-07-01 20:10               ` Glenn Morris
2011-07-02  1:10                 ` Ted Zlatanov
2011-07-02  1:20                   ` Glenn Morris
2011-07-02  1:38                     ` Ted Zlatanov
2011-07-05  0:56                       ` Dave Abrahams

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=87fwmpgb9o.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=rgm@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).