Gnus development mailing list
 help / color / mirror / Atom feed
From: Adrian Lanz <lanz@wsl.ch>
To: ding@gnus.org
Subject: Re: mm-default-directory not honoured
Date: Sat, 09 Oct 2010 13:31:35 +0200	[thread overview]
Message-ID: <yovazkunbo14.fsf@sampling.wsl.ch> (raw)
In-Reply-To: <m31v81ajby.fsf@quimbies.gnus.org>

>>>>> On Thu, 07 Oct 2010 21:33:53 +0200
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

    LMI> Adrian Lanz <lanz@wsl.ch> writes:
    >> Afterwards in line
    >> 
    >> (setq mm-default-directory (file-name-directory file))
    >> 
    >> (file-name-directory file) returns nil and mm-default-directory
    >> is set to nil. Does it really work for you as expected?

    LMI> Ah, right.  So it works the first time, but not the second.
    LMI> I've now fixed this.
    

Works, I confirme. Many thanks.

    >> BTW, now that I have a look into this code: as a user I never
    >> liked the effect of this line (setq mm-default-directory
    >> (file-name-directory file)).

    LMI> Yeah, it does seem a bit annoying.  But, on the other hand, if
    LMI> you're saving five attachments and want them all to go to the
    LMI> same directory, it's quite convenient.  So I don't know...
    

Yes. I see the point. It depends how (most) people are handling mail
attachements.

I keep all attachments in a single directory: for me, it is a quick and
dirty export of the files while going throug my new mail. BTW a new
feature for the wishlist: I would even like, I think, Gnus providing an
(optional) mechanism, which would automatically extract mail attachments
(by type?) from all new mail messages (incoming mails or, better, while
reading an unread message?).


Afterwards I filter (copy/move) documents (attachments) by hand into
thematic directories (projects). Of course, one could imagine a
splitting of mail attachments into directories the Gnus (magic) way,
like it's done with mail messages (based on mail headers). But this
might be a little bit exagerated? Any need for that? (I vote for it,
without high priority.)

Best, Adrian.




  reply	other threads:[~2010-10-09 11:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05  8:58 Adrian Lanz
2010-10-05 17:04 ` Lars Magne Ingebrigtsen
2010-10-05 23:39   ` Adrian Lanz
2010-10-07 19:33     ` Lars Magne Ingebrigtsen
2010-10-09 11:31       ` Adrian Lanz [this message]
2010-10-09 14:02         ` Lars Magne Ingebrigtsen
2010-10-26 11:57       ` Adrian Lanz
2010-10-29 23:01         ` Lars Magne Ingebrigtsen
2010-11-01  8:46           ` Adrian Lanz
2010-11-01 11:54             ` Lars Magne Ingebrigtsen
2010-11-02 10:47               ` Adrian Lanz
2010-11-04 19:56                 ` Lars Magne Ingebrigtsen

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=yovazkunbo14.fsf@sampling.wsl.ch \
    --to=lanz@wsl.ch \
    --cc=ding@gnus.org \
    /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).