From: David Kastrup <dak@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: esr@thyrsus.com, "Eric S. Raymond" <esr@snark.thyrsus.com>,
"Stephen J. Turnbull" <stephen@xemacs.org>,
Paul R <paul.r.ml@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Ready to start serious work on VC mode again
Date: Fri, 02 May 2008 16:32:51 +0200 [thread overview]
Message-ID: <85tzhghj3g.fsf@lola.goethe.zz> (raw)
In-Reply-To: <jwvd4o4ye92.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 02 May 2008 10:27:27 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> > Multiple back ends is kind of a wacky edge case;
>>>
>>> I don't agree. Multiple back end workspaces are going to be quite
>>> common *among the population of people who are likely to turn into
>>> vc.el hackers*. DAK obviously uses them, I do, Barry Warsaw (Mailman
>>> maintainer and Python release engineer) uses them on at least three
>>> projects, and that's just a few folks I know.
>>>
>>> You want this feature to shine, I think.
>
>> Does anybody have a clear idea about how VC should behave in such a
>> situation ?
>
> Currently, there are 2 ways to control it:
> - vc-handled-backends whose order influences which backend is used
> by default.
> - C-x v b which allows you to switch to another backend.
Oh, by the way: I find that C-x v b does switch to a different backend,
but the mode line is not adapted accordingly. Also, it somehow
considers RCS and CVS to be the same, which is pretty confusing.
> The fact that backends are currently associated to filenames is the
> source of the problems we need.
We need them?
> They should be associated to buffers instead.
Or buffers should be able to override the association with a
buffer-local binding.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2008-05-02 14:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 18:19 Ready to start serious work on VC mode again Eric S. Raymond
2008-04-28 19:32 ` Jason Earl
2008-04-28 19:56 ` Eric S. Raymond
2008-04-28 21:05 ` Jason Earl
2008-04-28 23:33 ` Andreas Schwab
2008-04-28 23:40 ` Stephen J. Turnbull
2008-04-29 2:19 ` Eric S. Raymond
2008-04-30 12:24 ` David Kastrup
2008-05-01 8:09 ` Eric S. Raymond
2008-05-01 9:27 ` Nick Roberts
2008-05-01 16:01 ` Eric S. Raymond
2008-05-01 16:42 ` Stephen J. Turnbull
2008-05-01 18:11 ` Paul R
2008-05-01 19:44 ` Sean O'Rourke
2008-05-01 19:54 ` David Kastrup
2008-05-02 14:27 ` Stefan Monnier
2008-05-02 14:32 ` David Kastrup [this message]
2008-05-02 19:24 ` Eric S. Raymond
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=85tzhghj3g.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.com \
--cc=monnier@iro.umontreal.ca \
--cc=paul.r.ml@gmail.com \
--cc=stephen@xemacs.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.