From: John Wiegley <jwiegley@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: A Modest Proposal
Date: Sat, 30 Apr 2016 17:14:14 -0700 [thread overview]
Message-ID: <m2vb2yeisp.fsf@newartisans.com> (raw)
In-Reply-To: <874mai4qhz.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 01 May 2016 01:38:00 +0200")
>>>>> Lars Ingebrigtsen <larsi@gnus.org> writes:
> I think the basic design is misguided. There is so much talk about matching
> up "ls" parameters to internal stuff that it makes my head swim. (Even if
> I'm not feverish.) C'mon. We're not barbarians. We can read directories
> ourselves.
Maybe the default behavior for dired should be to just use opendir. That
sounds like a good idea to me.
However, dired does a heck of a lot more than just call "ls": It lets you act
on anything with the same basic format, such as output from "find" or "ack".
So, the regexps are handy in that they're allowing a common, "group of files"
browsing metaphor on lots of stuff that just looks like, well, a group of
files.
Another random idea that just occurred to me: Given any compilation buffer,
create a dired buffer from it containing only the files that had errors.
Sometimes useful when I want to search/replace across every non-compiling
file.
Resuming: I wonder how would your proposal normalize that information? Would
it use a Dired API to populate the buffer, rather than filling it with text
and applying a bunch of regexps after the fact?
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-05-01 0:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 23:38 A Modest Proposal Lars Ingebrigtsen
2016-04-30 23:50 ` raman
2016-05-01 0:14 ` John Wiegley [this message]
2016-05-01 2:39 ` Eli Zaretskii
2016-05-01 13:30 ` John Wiegley
2016-05-01 14:44 ` Drew Adams
2016-05-01 15:01 ` Lars Ingebrigtsen
2016-05-01 15:16 ` Eli Zaretskii
2016-05-01 15:28 ` Dmitry Gutov
2016-05-01 15:45 ` Eli Zaretskii
2016-05-01 18:24 ` Alan Third
2016-05-01 18:38 ` Eli Zaretskii
2016-05-04 3:56 ` Stefan Monnier
2016-05-04 4:29 ` Drew Adams
2016-05-04 15:02 ` Eli Zaretskii
2016-05-04 10:39 ` Dmitry Gutov
2016-05-04 14:54 ` Eli Zaretskii
2016-05-01 19:21 ` Michael Albinus
2016-05-04 3:55 ` Stefan Monnier
2016-05-04 8:51 ` Andy Moreton
2016-05-04 15:09 ` Eli Zaretskii
2016-05-04 22:13 ` Andy Moreton
2016-05-05 7:58 ` Michael Albinus
2016-05-01 15:15 ` Eli Zaretskii
[not found] ` <<834mahollh.fsf@gnu.org>
2016-05-01 16:46 ` Drew Adams
2016-05-01 15:03 ` Lars Ingebrigtsen
2016-05-01 15:21 ` joakim
2016-05-01 23:02 ` Richard Stallman
2016-05-01 23:54 ` raman
2016-07-06 14:03 ` Ted Zlatanov
[not found] <<874mai4qhz.fsf@gnus.org>
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=m2vb2yeisp.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.