unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Eythan Weg <eythanweg@gmail.com>, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: attaching a file in dired mode
Date: Tue, 24 Feb 2009 13:23:17 -0500	[thread overview]
Message-ID: <02skm3vgmi.fsf@fencepost.gnu.org> (raw)
In-Reply-To: b4m8wnwyb41.fsf@jpl.org

Katsumi Yamaoka wrote:

> I didn't think that gnus-dired.el is used without launching Gnus.

I didn't follow the discussion, but I think rms wants gnus-dired to be
capable of (optionally) working without the rest of Gnus.

> But I may not be wrong at least in `C-c C-m C-a'
> (gnus-dired-attach). Why one wishes to use `C-c C-m C-a' is that one
> wants to use one's Gnus configuration for message sending, message
> archiving, etc. So, it is not unreasonable requirement that one has
> to run Gnus in advance, is it? How about making it stop with a
> warning like "You must run Gnus first"?

That's probably fine, if the message says something like:
"You must run Gnus, or customize `gnus-dired-mail-mode', first"

Or, how about something like changing the default value of
gnus-dired-mail-mode to something like:

(if (featurep 'gnus) 'gnus-user-agent
  'mail-user-agent)

(It's possible none of this makes sense, I'm not familiar with how
this works...)




  reply	other threads:[~2009-02-24 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87tz6p1c85.fsf@gmail.com>
2009-02-23  7:12 ` attaching a file in dired mode Katsumi Yamaoka
2009-02-23 19:17   ` Glenn Morris
2009-02-23 23:41     ` Katsumi Yamaoka
2009-02-24 18:23       ` Glenn Morris [this message]
2009-02-25  2:26         ` Katsumi Yamaoka
2009-02-25  3:59           ` Glenn Morris
2009-02-24 14:48   ` Eythan Weg

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=02skm3vgmi.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=eythanweg@gmail.com \
    --cc=yamaoka@jpl.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).