From: "Dieter Wilhelm, H." <dieter@duenenhof-wilhelm.de>
To: Glenn Morris <rgm@gnu.org>
Cc: 14931@debbugs.gnu.org
Subject: bug#14931: 24.3; marking extensions with dired-x
Date: Wed, 24 Jul 2013 17:55:30 +0200 [thread overview]
Message-ID: <CAPM452rxoLADA6o0+BOnGHFFAHYUnsOPV0kXBEaZsRar=JQJAQ@mail.gmail.com> (raw)
In-Reply-To: <20975.63203.802379.76278@gnu.org>
2013/7/24 Glenn Morris <rgm@gnu.org>:
>
> Please keep the debbugs address cc'd.
> Resending your comments so they are more visible.
I see and I'll take care. I noticed also a minor typo of mine below...
> Date: Wed, 24 Jul 2013 11:03:16 +0200
> From: "Dieter Wilhelm, H." <dieter@duenenhof-wilhelm.de>
>
> 2013/7/24 Glenn Morris <rgm@gnu.org>:
>
> Hi Glenn, thank you for your reply.
>
>>> dired-x does not mark lists of extension as advertised, please have a
>>> look at the following diff output.
>
>> It seems to work for me, and at first sight your patch does not look
>> right. I tried:
>> emacs-24.3 -Q -l dired-x
>> C-x d /path/to/lisp
>> M-: (dired-mark-extension '(".el" ".elc"))
>
> Sorry, I did only consider the interactive approach with 'C-* .'!
I meant '* .' not 'C-* .' of course...
--
Dieter
> Since I think this is more relevant/frequent to the dired usage as the
> purely programatical one. Idealy one would combine both! :-)
>
> With my diff a simple sequence in the mini-buffer like 'png jpg' is
> working, though not with the original code...
>
> Thanks for your attention
>
> Dieter
next prev parent reply other threads:[~2013-07-24 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 10:33 bug#14931: 24.3; marking extensions with dired-x Dieter Wilhelm, H.
2013-07-24 7:29 ` Glenn Morris
[not found] ` <CAPM452qvtorhEYFAfKDc00eTQ=HuF0g0V5R=bRioGvd8RhVLhA@mail.gmail.com>
2013-07-24 15:46 ` Glenn Morris
2013-07-24 15:55 ` Dieter Wilhelm, H. [this message]
2013-07-24 16:10 ` Glenn Morris
2013-07-24 17:07 ` Dieter Wilhelm, H.
2020-09-18 14:24 ` Lars Ingebrigtsen
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='CAPM452rxoLADA6o0+BOnGHFFAHYUnsOPV0kXBEaZsRar=JQJAQ@mail.gmail.com' \
--to=dieter@duenenhof-wilhelm.de \
--cc=14931@debbugs.gnu.org \
--cc=rgm@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).