Gnus development mailing list
 help / color / mirror / Atom feed
From: Benjamin Rutt <rutt+news@cis.ohio-state.edu>
Subject: Re: request feedback on new function gnus-dired-attach
Date: Sat, 15 Dec 2001 01:39:27 -0500	[thread overview]
Message-ID: <wc33d2dyokg.fsf@eta.cis.ohio-state.edu> (raw)
In-Reply-To: <2ny9k52erz.fsf@zsh.cs.rochester.edu> (ShengHuo ZHU's message of "Sat, 15 Dec 2001 01:12:00 -0500")

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

>> (define-key dired-mode-map [(control c) (control a)] 'gnus-dired-attach)
>>
>>    is somewhat ugly, since we are defining a dired keymap in another
>>    area of code.  Paul Jarc, on the above g.e.g thread, suggested that
>>    we define a gnus-dired minor mode which can contain the keymap.
>>    But I'm not sure if that's better, since ultimately we're still
>>    stealing a possible future dired keybinding (C-c C-a currently
>>    isn't defined in dired-mode).  Maybe that last line should simply
>>    go in users ~/.gnus so the users control the keybinding override?
>
> Why not do both?  We can steal a special (or customizable) prefix for
> gnus-dired minor mode.  Users still can set C-c C-a in dired-mode-map
> to the function.  This would be less intrusive.

OK, I'll work on defining a gnus-dired minor mode.

>> 3) whether you think this should exist as a separate file that isn't
>>    included in gnus.
>
> It is better to add a separate file, say gnus-dired.el, for gnus-dired
> minor mode. If you'd like to add your code to Gnus package, you'd
> better send an assignment form to FSF (unless you've signed the form).
> I can send you the request form.

Yes, I'd like it to be included with gnus.  I will be happy to sign
the assignment request form for the FSF, just let me know what I need
to do to get that accomplished.

> In addition, I have a piece of code to open file (in dired-mode)
> according to mailcap.  I'd like to include it too.

Sure, please send your code to me and I will integrate it into the new
file gnus-dired.el.  The file can then be used for any purpose where
gnus and dired meet.

> How about use files-to-attach as an argument? So the function can be
> called from other codes too. 
>
> (defun gnus-dired-attach (files-to-attach)
>    "Attach dired's marked files to a gnus message composition."
>    (interactive
>       (list
>  	 (delq nil
>  	      (mapcar
>  		 (lambda (f) (if (file-directory-p f) nil f))
>  		 (nreverse (dired-map-over-marks (dired-get-filename) nil))))))
>     ...)

That looks very nice, I will make that change.  Thanks,
-- 
Benjamin



  reply	other threads:[~2001-12-15  6:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-15  0:19 Benjamin Rutt
2001-12-15  5:25 ` Benjamin Rutt
2001-12-15  6:12 ` ShengHuo ZHU
2001-12-15  6:39   ` Benjamin Rutt [this message]
2001-12-15  8:17   ` Benjamin Rutt
2001-12-15 23:34   ` Benjamin Rutt
2001-12-29  0:40     ` Lars Magne Ingebrigtsen
2001-12-31  7:06       ` Benjamin Rutt
2001-12-31  7:47         ` Paul Jarc
2002-01-19 19:12         ` Lars Magne Ingebrigtsen
2002-01-20  0:39           ` Benjamin Rutt
2002-01-20  0:52             ` Lars Magne Ingebrigtsen
2002-02-02  1:25       ` Benjamin Rutt
2002-02-02  6:38         ` ShengHuo ZHU

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=wc33d2dyokg.fsf@eta.cis.ohio-state.edu \
    --to=rutt+news@cis.ohio-state.edu \
    /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).