From: "Eric S. Raymond" <esr@thyrsus.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: My plans for VC mode
Date: Sat, 22 Nov 2014 13:08:45 -0500 [thread overview]
Message-ID: <20141122180845.GA27863@thyrsus.com> (raw)
In-Reply-To: <5470CBEC.3000500@yandex.ru>
Dmitry Gutov <dgutov@yandex.ru>:
> On 11/22/2014 06:37 PM, Eric S. Raymond wrote:
>
> >vc-state is likely to surivive with unaltered semantics. So is diff.
>
> Ok. I'm also using `vc-diff-internal', `vc-buffer-sync' and
> `vc-exec-after', but these seem to be less relevant to the current
> subject.
Agreed.
> The above list includes `state', which you're saying won't be
> changed much. Other than that, do you mean `dir-status' and
> `dir-status-files' will be merged?
That seems extremely likely. Unless I run out of time to work on this
before I get to it.
> If that means that the new function will behave just like
> `dir-status' when passed a nil (or a directory) instead of a list of
> files, then how that's much better than keeping the functions
> separate? The downside is obvious, meanwhile (API breakage).
It's better than keeping the functions separate because the
separation contributes in a significant way to making the
interface a hairball that is difficult to understand and maintain.
I should have been able to write SRC support in 90 minutes. The fact
that it took the inventor of both SRC and VC mode *two days* told
me the API has gone very badly wrong.
It is obvious why; we have been succumbing to the temptation to just
glue on another knob for far too long. Ideally, I would like to
*halve* the number of entry points. And ensure that each one has
simple, regular semantics that can be described in one or two
sentences. Backward compatibility can go straight to the hell where
it belongs.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2014-11-22 18:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 13:33 My plans for VC mode Unknown
2014-11-22 14:17 ` Jan D.
2014-11-22 16:29 ` Eric S. Raymond
2014-11-22 16:44 ` Jan D.
2014-11-22 14:33 ` Dmitry Gutov
2014-11-22 16:37 ` Eric S. Raymond
2014-11-22 17:46 ` Dmitry Gutov
2014-11-22 18:08 ` Eric S. Raymond [this message]
2014-11-23 1:27 ` Dmitry Gutov
2014-11-22 22:32 ` Stefan Monnier
2014-11-23 1:01 ` Dmitry Gutov
2014-11-23 6:25 ` Eric S. Raymond
2014-11-22 23:17 ` Steinar Bang
2014-11-23 20:02 ` Eric S. Raymond
2014-11-23 20:11 ` Eli Zaretskii
2014-11-22 16:11 ` Stefan Monnier
2014-11-22 16:41 ` Eric S. Raymond
2014-11-22 16:59 ` Dieter Deyke
2014-11-22 22:34 ` Stefan Monnier
2014-11-23 19:58 ` Eric S. Raymond
2014-11-24 6:40 ` Dieter Deyke
2014-11-24 7:50 ` Eric S. Raymond
2014-11-24 7:55 ` Kan-Ru Chen (陳侃如)
2014-11-24 8:07 ` Eric S. Raymond
2014-11-24 14:33 ` Stefan Monnier
2014-11-24 17:57 ` Eric S. Raymond
2014-11-23 19:27 ` Ivan Shmakov
2014-11-23 20:10 ` Eric S. Raymond
2014-11-22 19:02 ` Michael Albinus
2014-11-23 6:26 ` Eric S. Raymond
2014-11-23 8:23 ` Michael Albinus
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=20141122180845.GA27863@thyrsus.com \
--to=esr@thyrsus.com \
--cc=dgutov@yandex.ru \
--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.