From: Carl Worth <cworth@cworth.org>
To: Keith Amidon <camalot@picnicpark.org>
In-Reply-To: <873a3hou2k.fsf@friend.picnicpark.org>
References: <1260053640-10034-1-git-send-email-keith@nicira.com>
	<1260053640-10034-2-git-send-email-keith@nicira.com>
	<1260053640-10034-3-git-send-email-keith@nicira.com>
	<878wda49b6.fsf@yoom.home.cworth.org>
	<873a3hou2k.fsf@friend.picnicpark.org>
Date: Sun, 13 Dec 2009 15:07:09 -0800
Message-ID: <87my1m323m.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Cc: Keith Amidon <keith@nicira.com>, notmuch@notmuchmail.org
Subject: Re: [notmuch] [PATCH 2/2] Save all attachments to a directory
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Fri, 11 Dec 2009 17:32:51 -0800, Keith Amidon <camalot@picnicpark.org> w=
rote:
> {-- Thu, 10 Dec 2009 16:57:01 -0800: Carl <cworth@cworth.org> wrote: --}
> What do you see as the "write one" behavior for a message with multiple
> attachments?

I was imagining a direct-manipulation approach by clicking on (or
pressing a key while point is on) a button representing the attachment.

And then it would probably be reasonable to make that same keypress save
the next attachment if point is positioned between attachment buttons.

> Yes, you're right the current approach should have had a proper prompt.
> I've been thinking about this though and I wonder if we should skip
> separately prompting for the directory and instead do the following:
>=20
> 1) Have customizable "default save directory" both types of attachment
>    saving default to.  Use this as the path part of the prompt for the
>    filename to which the attachment will be written.
> 2) After the user has adjusted the path as required, verify that the
>    full directory path exists and if not create it.
> 3) Use the same directory path as the default for any subsequent
>    attachments that are being saved.

Yes, the above sounds good to me. If the directory doesn't exist it
should probably give a y-or-n prompt before creating it, (and drop back
to prompting for the full filename path again if the users says no to
creating the directory).

> This seems like it would lesson the number of keystrokes required for
> at least some common cases.

Spoken as a man after my own heart.

> I'm not sure it is the most usable solution, but I believe selecting the
> text to save in the rendered message in the thread view and using "M-x
> write-region" should handle this use case.

Funny---I don't think I've ever used that command before. But it should
be handy---thanks!

=2DCarl

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLJXOe6JDdNq8qSWgRAupSAJ9FGo/m+JBoDvLa0SlVcX27dsxgxQCcDFmd
JrLinXtA70ddCHBjpTvcWTI=
=bJN3
-----END PGP SIGNATURE-----
--=-=-=--