Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: gnus-dired-attach, optionally type?
Date: Sun, 16 Jun 2013 09:50:27 +0200	[thread overview]
Message-ID: <87ehc2bikc.fsf@mat.ucm.es> (raw)
In-Reply-To: <84txkyllkh.fsf@davestoy.homelinux.org>

[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]

>> "Dave" == Dave Goldberg <david.goldberg6@verizon.net> writes:

   >> (defun my-dired-attach (&optional arg)
   >> (interactive "P")
   >> (if arg
   >> (New code)
   >> (old code)))

   > It looks like you are writing a modified version of
   > gnus-dired-attach, along with the above wrapper.  If that's correct
   > then I think this will work.  I haven't tested with this specific
   > case, but it's worked for others:

   > (defun my-dired-attach (&optional arg)
   >   (interactive "P")
   >   (if arg
   >       (call-interactively 'modified-gnus-dired-attach)
   >     (call-interactively 'gnus-dired-attach)))

Right precisely, I tried that but without the call-interactively.

I originally thought to modify *directly* gnus-dired-attach,[1] but as I
said its interactive structure is too complex for me. Also it seems that
most users don't think such a patch is necessary.


   > I think you can do something similar with defadvice but I haven't
   > used that.

I have decided to avoid defadvice if possible, it is just almost
impossible to debug.

thanks

Uwe 

Footnotes:
[1]  one function to rule them all.


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5556 bytes --]

      reply	other threads:[~2013-06-16  7:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14 12:13 Uwe Brauer
2013-06-14 14:49 ` Eric S Fraga
2013-06-14 20:57   ` Uwe Brauer
2013-06-14 22:10   ` Uwe Brauer
2013-06-16  4:35     ` Dave Goldberg
2013-06-16  7:50       ` Uwe Brauer [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=87ehc2bikc.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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).