unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: master 739593d 3/5: Make gnus-copy-file act like copy-file etc.
Date: Thu, 14 Sep 2017 00:17:06 -0400	[thread overview]
Message-ID: <jwvo9qddiig.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 83fa9922-8d83-9d2f-82af-f34e90521d88@cs.ucla.edu

>> But it might have to be documented in also the Gnus manual, as
>> `gnus-summary-save-article' that uses the function doesn't
>> specify a destination and a user has to enter the directory name.

> The special behavior with gnus-summary-save-article and directories (or
> directory names) was not documented. Although I'm not a Gnus expert
> I took a stab at documenting the current behavior by installing the attached
> patch. If we revert the Gnus change (or make further changes) then this part
> of the manual will need to be revisited.

Maybe the interactive behavior could look as follows:

- when copying/renaming to "/foo/dir", first do it as we do now.
- if it signals an error because "/foo/dir" already exists, check if
  it's a directory.
- if it's a directory, ask the user to confirm that he meant "/foo/dir/"

That would let the user learn that he should have written "/foo/dir/" in
the first place, and so should slowly get him to avoid the prompt.


        Stefan




  reply	other threads:[~2017-09-14  4:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170911053128.28763.28434@vcs0.savannah.gnu.org>
     [not found] ` <20170911053130.C5F002068F@vcs0.savannah.gnu.org>
2017-09-11 23:14   ` master 739593d 3/5: Make gnus-copy-file act like copy-file etc Katsumi Yamaoka
2017-09-12  2:12     ` Ken Brown
2017-09-12  2:33       ` Katsumi Yamaoka
2017-09-12 19:22         ` Paul Eggert
2017-09-14  4:17           ` Stefan Monnier [this message]
2017-09-14 16:54             ` Eli Zaretskii
2017-09-14 17:59               ` Paul Eggert
2017-09-14 18:38                 ` Eli Zaretskii
2017-09-15  4:04                   ` Paul Eggert
2017-09-15  9:16                     ` Eli Zaretskii
2017-09-12  2:42       ` Eli Zaretskii
2017-09-13 19:33     ` Lars Ingebrigtsen
2017-09-13 20:07       ` Paul Eggert
2017-09-13 20:11         ` Lars Ingebrigtsen
2017-09-13 20:41           ` Paul Eggert
2017-09-13 21:10             ` Lars Ingebrigtsen
2017-09-13 23:32               ` Paul Eggert
2017-09-14 11:25                 ` Lars Ingebrigtsen
2017-09-14  2:35         ` Eli Zaretskii

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=jwvo9qddiig.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.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).