From: Lee Willis <lee@gbdirect.co.uk>
Subject: Re: Bug? pgnus 0.95
Date: 28 Jul 1999 14:28:15 +0100 [thread overview]
Message-ID: <lzaesggaz4.fsf@landlord.gbdirect.co.uk> (raw)
In-Reply-To: <m1bemhsud5r.fsf@blackbird.mitre.org>
dsg@mitre.org (David S. Goldberg) writes:
> I think you need to do a C-u m when over the group line, not just m.
> That's what's documented, and it works for me.
Sorry, I didn't explain myself too well. That would Gcc to the group
that the point is over which is not what I'm after.
I tootle around and read my mail, then say for example I want to compose
a new mail. I'm in the Group buffer with point over some indeterminate
group (At this point I don't care and shouldn't have to care which!) and
hit 'm' to compose a new message. What I think should happen is that I
should get a Gcc: into my archive folder (That's what the lisp snippet I
sent does). This is what, correctly, happens if point is over a group in
a topic with the ((gcc-self . t)) not set. If however point happens to
be over a group who's parent topic has ((gcc-self . t)) in it's
parameters I get an empty Gcc line. This is IMHO wrong. My messages
should be archived according to gnus-message-archive-group regardless of
the group I'm over, after all I'm just over the group, not IN it.
Sorry for the possibly weak explanation both times, I hope you now see
what I mean ...
Lee.
--
I was doing object-oriented assembly at 1 year old ...
For some reason my mom insists on calling it "Playing with blocks"
next prev parent reply other threads:[~1999-07-28 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-28 12:13 Lee Willis
1999-07-28 13:17 ` David S. Goldberg
1999-07-28 13:28 ` Lee Willis [this message]
1999-07-28 15:39 ` Kai Großjohann
1999-07-29 8:17 ` Jaap-Henk Hoepman
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=lzaesggaz4.fsf@landlord.gbdirect.co.uk \
--to=lee@gbdirect.co.uk \
/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).