From: Tassilo Horn <tassilo@member.fsf.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Deniz Dogan <deniz.a.m.dogan@gmail.com>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Making it easier to enable dired-x
Date: Fri, 18 Mar 2011 10:03:12 +0100 [thread overview]
Message-ID: <87aags6bsf.fsf@member.fsf.org> (raw)
In-Reply-To: <jwvy64di2tz.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 17 Mar 2011 22:24:15 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
Hi!
>> Eg dired-filename-at-point is not massively different to ffap and
>> thing-at-pt,
`dired-filename-at-point' returns the expanded file name in a dired
buffer. (thing-at-point 'filename) returns only the last part. So the
former is clearly useful when writing code operating it dired buffers.
>> stuff like "hands-off-my-x-keys" seems clunky, dired-x's local
>> variables are now replaced by dir-locals, there's 50 lines and 3
>> commands dedicated just to deleting TeX and patch temp files, etc.
Yes, for those, I agree.
>> Plus it has its own manual, which is ~ 80% of the length of
>> dired.texi, which would have to be merged in somehow.
>
> I tend to agree. I would welcome adding the remaining useful
> functionality of dired-x into dired and then making dired-x obsolete.
From dired-aux, I think the subdir stuff is really useful.
From dired-x, I frequently use `dired-jump' and `dired-omit-mode'.
Bye,
Tassilo
next prev parent reply other threads:[~2011-03-18 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 10:15 Making it easier to enable dired-x Deniz Dogan
2011-03-16 14:00 ` Drew Adams
2011-03-16 14:31 ` Ted Zlatanov
2011-03-16 18:17 ` Glenn Morris
2011-03-17 15:19 ` Deniz Dogan
2011-03-17 20:31 ` Glenn Morris
2011-03-18 2:24 ` Stefan Monnier
2011-03-18 9:00 ` Leo
2011-03-18 9:03 ` Tassilo Horn [this message]
2011-03-18 17:43 ` Stefan Monnier
2011-03-18 21:58 ` Richard Stallman
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=87aags6bsf.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=deniz.a.m.dogan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.