From: Harry Putnam <reader@newsguy.com>
Subject: Re: Latest cvs attachements have no button, appear inline
Date: Thu, 01 Jan 2004 20:35:29 -0600 [thread overview]
Message-ID: <m3brpnjcwe.fsf@newsguy.com> (raw)
In-Reply-To: <m3oetnjdrq.fsf@newsguy.com>
Harry Putnam <reader@newsguy.com> writes:
> I'm not sure what the recipient got but I wanted them to get an
> attachment, not an inline document.
With a little more testing I see there are two choice at the
`disposition' prompt one gets when using C-c C-a (`mml-attach-file')
Apparently the default is `inline' but I think that may have happened
somewhat recently.
Since we already have C-x i to insert files inline, wouldn't it make
sense to default to `attachment'. That's almost always what I would
want when attaching something. Or maybe its configurable. But still
`attachemnt' seems to be a sensible default.
next prev parent reply other threads:[~2004-01-02 2:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 2:16 Harry Putnam
2004-01-02 2:35 ` Harry Putnam [this message]
2004-01-02 11:01 ` Reiner Steib
2004-01-02 19:51 ` Harry Putnam
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=m3brpnjcwe.fsf@newsguy.com \
--to=reader@newsguy.com \
/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).