unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>,
	martin rudalics <rudalics@gmx.at>
Cc: 16424@debbugs.gnu.org
Subject: bug#16424: 24.3.50; y-or-n-p prompt no more visible in minibuffer
Date: Sun, 12 Jan 2014 10:22:26 -0800 (PST)	[thread overview]
Message-ID: <0f117281-9f53-4a40-aeb5-247f46cd5109@default> (raw)
In-Reply-To: <87r48dqel4.fsf@gmail.com>

OT for this bug, but you might (anyway) consider using a different
function for this question about acting on a list of files.

Dired offers some code for this kind of thing.  See, for instance,
`dired-map-over-marks-check'.  Some of what it does might be
pertinent here.

In Dired+ I have a function `diredp-y-or-n-files-p', which does
just the following, and so is probably more pertinent here (but
it does not log errors as `dired-map-over-marks-check' does):

,----
| diredp-y-or-n-files-p is a compiled Lisp function in `dired+'.
| (diredp-y-or-n-files-p PROMPT FILES &optional PREDICATE)
| 
| PROMPT user with a "y or n" question about a list of FILES.
| Return t if answer is "y".  Otherwise, return nil.
| 
| Like `y-or-n-p', but the user can also hit `l' to display the list of
| files that the confirmation is for, in buffer `*Files'.  When
| finished, buffer `*Files*' is killed if it was never shown, or is
| hidden and buried otherwise.  Thus, if it was shown then it is still
| available to revisit afterward (even if the user quit using `C-g').
| 
| PREDICATE is passed to `diredp-list-files', to list only file names
| for which it returns non-nil.
`----

`diredp-list-files' does this:

,----
| diredp-list-files is a compiled Lisp function in `dired+'.
| (diredp-list-files FILES &optional DIR BUFNAME PREDICATE)
| 
| Display FILES, a list of file names.  Wildcard patterns are expanded.
| The files are shown in a new buffer, `*Files*' by default.
| Optional arg DIR serves as the default directory for expanding file
|  names that are not absolute.  It defaults to `default-directory'.
| Optional arg BUFNAME is the name of the buffer for the display.
|  It defaults to `*Files*' (or `*Files*<N>' if `*Files*' exists).
`----

These functions are not really Dired-specific, as you can tell from
the descriptions.

HTH.  Again, I realize it is OT for the bug.





  reply	other threads:[~2014-01-12 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 16:49 bug#16424: 24.3.50; y-or-n-p prompt no more visible in minibuffer Thierry Volpiatto
2014-01-12 17:27 ` martin rudalics
2014-01-12 17:45   ` Thierry Volpiatto
2014-01-12 18:22     ` Drew Adams [this message]
2014-01-12 19:49       ` Thierry Volpiatto
2014-01-12 18:41     ` martin rudalics
2014-01-13 17:52 ` martin rudalics
2014-01-14 13:22   ` Thierry Volpiatto

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=0f117281-9f53-4a40-aeb5-247f46cd5109@default \
    --to=drew.adams@oracle.com \
    --cc=16424@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    --cc=thierry.volpiatto@gmail.com \
    /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).