unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org
Subject: vc-arch.el buglets
Date: 16 Mar 2004 13:06:39 +0900	[thread overview]
Message-ID: <buofzc9xwog.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)

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]

             reply	other threads:[~2004-03-16  4:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16  4:06 Miles Bader [this message]
2004-03-16 13:55 ` vc-arch.el buglets Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=buofzc9xwog.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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 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).