* vc-arch.el buglets
@ 2004-03-16 4:06 Miles Bader
2004-03-16 13:55 ` Stefan Monnier
0 siblings, 1 reply; 2+ messages in thread
From: Miles Bader @ 2004-03-16 4:06 UTC (permalink / raw)
Cc: emacs-devel
Hi, vc-arch.el showed up in emacs; I'm very glad to finally be able to
do `C-x v =' on arch files (my number one wish before)!
A few little buglets I noticed:
(1) If you visit a _new_ file in an arch-controlled directory, it
asks you:
File NAME was lost; check out from version control? (yes or no)
Which of course is completely wrong.
(2) Commit uses -L with the contents of the log buffer, which seems
like the wrong thing (remember, -L uses the given text to fill in
_both_ the Summary: and the log body -- and a log-edit buffer
usually contains newlines...).
I think ideally, it would pre-fill-in the log-edit buffer with a
skeleton arch log (e.g. just an empty Summary: line and a
header-end empty line), and pass it to commit using the -l option.
(3) The _first_ time you use `C-x v =' on any given file, it generates
a *vc-diff* buffer containing _two_ copies of the diff! Subsequent
invocations yield only the proper one copy.
Thanks,
-Miles
p.s. Like many emacs & arch users probably did, I made a half-hearted
attempt at vc support when I first started using arch, but the
impedance mismatch between arch and vc.el's model of revision
control caused severe head pains... :-]
--
If you can't beat them, arrange to have them beaten. [George Carlin]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: vc-arch.el buglets
2004-03-16 4:06 vc-arch.el buglets Miles Bader
@ 2004-03-16 13:55 ` Stefan Monnier
0 siblings, 0 replies; 2+ messages in thread
From: Stefan Monnier @ 2004-03-16 13:55 UTC (permalink / raw)
Cc: emacs-devel
> (1) If you visit a _new_ file in an arch-controlled directory, it
> asks you:
> File NAME was lost; check out from version control? (yes or no)
> Which of course is completely wrong.
Yes, I've bumped into this one as well. I'm not sure how to fix it yet.
> (2) Commit uses -L with the contents of the log buffer, which seems
> like the wrong thing (remember, -L uses the given text to fill in
> _both_ the Summary: and the log body -- and a log-edit buffer
> usually contains newlines...).
> I think ideally, it would pre-fill-in the log-edit buffer with a
> skeleton arch log (e.g. just an empty Summary: line and a
> header-end empty line), and pass it to commit using the -l option.
Yes, this is a known problem as well.
> (3) The _first_ time you use `C-x v =' on any given file, it generates
> a *vc-diff* buffer containing _two_ copies of the diff! Subsequent
> invocations yield only the proper one copy.
I fixed this a while back, but..., I forgot to install this part of my
local changes.
It's a problem in vc.el and vc-hooks.el.
Stefan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-03-16 13:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-16 4:06 vc-arch.el buglets Miles Bader
2004-03-16 13:55 ` Stefan Monnier
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).