Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Content-Type: nil
Date: 18 Dec 1998 12:39:59 +0100	[thread overview]
Message-ID: <kig90g5d6gg.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "18 Dec 1998 12:29:41 +0100"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Vladimir Volovich <vvv@vvv.vsu.ru> writes:
> 
> > when attaching a file, gnus suggests the "best" content-type according
> > to some heuristics. but if one simply presses RET, then gnus puts
> > Content-Type: nil into the attached part.
> 
> Is this with `C-c C-a'?  In that case, I'm unable to reproduce the
> bug.

I reproduced it and fixed it.  See the patches I mailed you.

It is easy to reproduce by `C-c C-a ~/.emacs RET' and then just press
RET when queried about content-type.


      reply	other threads:[~1998-12-18 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-17 21:34 Vladimir Volovich
1998-12-18 11:29 ` Lars Magne Ingebrigtsen
1998-12-18 11:39   ` Hrvoje Niksic [this message]

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=kig90g5d6gg.fsf@jagor.srce.hr \
    --to=hniksic@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).