From: Glenn Morris <rgm@gnu.org>
To: neo lee <neo.lee@gmail.com>
Cc: 1158@emacsbugs.donarmstrong.com
Subject: bug#1158: 23.0.60; vc mode not working under newest Emacs.app
Date: Thu, 16 Oct 2008 01:58:57 -0400 [thread overview]
Message-ID: <18678.55329.756473.949668@fencepost.gnu.org> (raw)
In-Reply-To: <53556b270810141904u642fd38ew15dded35ba2d86cf@mail.gmail.com>
neo lee wrote (on Wed, 15 Oct 2008 at 10:04 +0800):
> But the mode actually not working. If I try to use any of the vc-* commands
> after that, the message in mini-buffer will be:
>
> No fileset is available here.
>
> Other vc-mode functions are also missing, e.g. the revision displayed on the
> bar.
It is surprising that a change in configure options could affect such
a thing.
What happens if you start with `emacs -Q', and open the README file
from the directory where you checked out the CVS trunk?
If you repeat the experiment, but do M-x toggle-debug-on-error before
opening README, do you get any backtrace?
What does
M-: (executable-find "cvs")
return?
What does
M-: (vc-cvs-registered "/path/to/emacs/cvs/README")
return?
What does
M-x list-load-path-shadows
say?
next prev parent reply other threads:[~2008-10-16 5:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18679.33051.38492.185322@fencepost.gnu.org>
2008-10-13 11:01 ` bug#1158: 23.0.60; vc mode not working under newest Emacs.app Neo Lee
2008-10-14 7:48 ` Nick Roberts
[not found] ` <53556b270810140137i5315b6dch787199f00c0d54a5@mail.gmail.com>
2008-10-14 10:35 ` Nick Roberts
2008-10-15 1:06 ` Glenn Morris
[not found] ` <mailman.1067.1224034207.25473.bug-gnu-emacs@gnu.org>
2008-10-15 1:37 ` Neo
2008-10-15 1:45 ` Glenn Morris
2008-10-15 2:04 ` Neo Lee
2008-10-16 5:58 ` Glenn Morris [this message]
2008-10-16 8:05 ` Neo Lee
2008-10-17 15:24 ` Stefan Monnier
2008-10-16 8:11 ` Neo Lee
2008-10-16 18:10 ` bug#1158: marked as done (23.0.60; vc mode not working under newest Emacs.app) Emacs bug Tracking System
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=18678.55329.756473.949668@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=1158@emacsbugs.donarmstrong.com \
--cc=neo.lee@gmail.com \
/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).