Gnus development mailing list
 help / color / mirror / Atom feed
From: Toni Drabik <tdrabik@public.srce.hr>
Subject: Re: forwarding as text rather than MIME?
Date: 22 Feb 1999 13:54:44 +0100	[thread overview]
Message-ID: <cc3emniha3v.fsf@jagor.srce.hr> (raw)
In-Reply-To: Hrvoje Niksic's message of "21 Feb 1999 20:40:10 +0100"

Hrvoje Niksic <hniksic@srce.hr> writes:

> > 'Twould be nice if this were customizable. I like to edit out
> > headers, etc., in messages I send.
> 
> You will be able to do that in the next release -- Lars gave in that
> much.  What you won't be able to do is forward messages the old,
> pre-MIME, way.  Which is kinda sad, but I guess we'll get used to it.

I don't think so.  Forwarding messages the new, MIME way is OK when we 
talk about mail messages.  But, what's with post forwards?  Currently, 
`gnus-summary-post-forward' forwards selected post as a MIME
attachment.  And, because attachments of any kind are considered rude
in non-binary newsgroups, that's *very* bad thing.

I'd like to be able to forward posts the old way.  Of course, I always 
can press `F' and change the `Newsgroups: ' header, but that's not a
solution...  Not a good one, at least.


-- 
Warning: This article may be fatal if swallowed.
Toni Drabik <tdrabik@public.srce.hr> * <URL:http//public.srce.hr/~tdrabik/>


  reply	other threads:[~1999-02-22 12:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-15 18:20 Bill White
1999-02-15 20:36 ` Hans de Graaff
1999-02-19 14:23   ` Lars Magne Ingebrigtsen
1999-02-20  9:44     ` Hans de Graaff
1999-02-21  7:21       ` Chris Tessone
1999-02-21 10:38         ` Lars Magne Ingebrigtsen
1999-02-21 19:37           ` Chris Tessone
1999-02-21 19:40             ` Hrvoje Niksic
1999-02-22 12:54               ` Toni Drabik [this message]
1999-02-22 17:43                 ` Hrvoje Niksic
1999-02-22 17:58                   ` Robert Bihlmeyer
1999-02-22 18:26                     ` Hrvoje Niksic
1999-02-23 18:32                       ` Per Abrahamsen
1999-02-24 15:52                         ` Robert Bihlmeyer
1999-02-24 16:17                           ` Hrvoje Niksic
1999-02-24 16:30                             ` Chris Tessone
1999-02-24 16:43                               ` Alexandre Oliva
1999-02-24 16:52                                 ` Chris Tessone
1999-02-24 17:01                                 ` Kai.Grossjohann
1999-02-24 17:10                               ` Robert Bihlmeyer
     [not found]                           ` <m3678rtieo.fsf@serpent.laymusic.>
1999-02-25 17:17                             ` Kai.Grossjohann
1999-02-25 10:39                         ` Russ Allbery
1999-02-26  7:14                   ` Lars Magne Ingebrigtsen
1999-02-26 11:48                     ` Hrvoje Niksic
1999-02-26 12:30                       ` Per Abrahamsen
1999-02-26 14:45                       ` Lars Magne Ingebrigtsen
1999-02-27 12:38                         ` Russ Allbery
1999-02-27 13:15                           ` Lars Magne Ingebrigtsen
1999-02-27 14:13                           ` Hrvoje Niksic
1999-02-28 19:21                           ` Per Abrahamsen
1999-02-22 22:13               ` Aaron M. Ucko
1999-04-03  7:28       ` Hans de Graaff

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=cc3emniha3v.fsf@jagor.srce.hr \
    --to=tdrabik@public.srce.hr \
    /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).