all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: A Modest Proposal
Date: Sun, 01 May 2016 01:38:00 +0200	[thread overview]
Message-ID: <874mai4qhz.fsf@gnus.org> (raw)

I've been on the couch with a cold for the past few days, so I've been
doing documentation and doc string tweaks to avoid going crazy with
boredom.  (It was either that or watch Murder She Wrote.)

I've been reminded this time over that (apart from the many pieces of
Emacs that I know nothing about), there are two areas I don't really
like touching:  Customize and dired.

Customize:

When I try to chase down a rendering bug or ... anything, I'm seldom
able to.  Everything seems to happen somewhere else.  In addition, it
does a lot of stuff with overlays instead of text overlays (which I find
more convenient to interface with, especially when debugging).

And looking at the number of commit messages, perhaps I'm not the only
one.

Perhaps it's time just to throw in the towel and reimplement it from
scratch?  I'm talking about the user interface only, of course.  The
`defcustom' language etc etc etc are fine as they are.

Perhaps we could just start generating HTML write a new interface on top
of shr or something?  Or gtk+?  I dunno.  But I think it's an idea that
somebody who's looking for a nice little project should consider.

Dired:

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.

In addition, dired (in some places) tries to use the visual
representation in the buffer for something useful, which limits what can
and can't be displayed.  Specifying what files to work on as a regexp is
just kinda nauseating.  (Did I mention my cold?)

It has been mentioned that the reliance on "ls" would enable a future
more async version of dired, but we can use the async.el library for
that just as well, without all the drawbacks.

So that's another little project for somebody: Implement a dired clone
from a UI interface standpoint, but implement it in a more flexible
way.  Then we can make dired obsolete in a few years.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





             reply	other threads:[~2016-04-30 23:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-30 23:38 Lars Ingebrigtsen [this message]
2016-04-30 23:50 ` A Modest Proposal raman
2016-05-01  0:14 ` John Wiegley
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=874mai4qhz.fsf@gnus.org \
    --to=larsi@gnus.org \
    --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.