From: Vagn Johansen <gonz808@hotmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Working with different projects in Emacs
Date: Sun, 12 Apr 2009 18:26:14 +0200 [thread overview]
Message-ID: <m2vdp9x2hl.fsf@hotmail.com> (raw)
In-Reply-To: eaf68acc-bd3d-4332-b69f-0aa720eba533@k19g2000prh.googlegroups.com
rustom <rustompmody@gmail.com> writes:
> My conclusion is that the tags making part of vps is having
> ~/.emacs_vps hardcoded though the rest (Project.txt) is picked up from
> vps-project-dir
Almost. vps-project-dir is hardcoded to the *expanded* version of
~/.emacs_vps. From vps.el:
(defvar vps-project-dir (expand-file-name "~/.emacs_vps"))
Note the call to expand-file-name which means that vps-project-dir end
up containing something like /Users/john/.emacs_vps.
When you set vps-project-dir to ~/.. then the etags program fails to
find the file (and thus fails to generate a tags file). The directory
needs to be expanded for etags to work.
I have updated vps.el to automatically expand the directory wherever
it is used.
Thanks for digging into the problem.
--
Vagn Johansen
next prev parent reply other threads:[~2009-04-12 16:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4901.1239203083.31690.help-gnu-emacs@gnu.org>
2009-04-08 18:56 ` Working with different projects in Emacs Vagn Johansen
2009-04-09 13:44 ` rustom
2009-04-09 19:45 ` Vagn Johansen
2009-04-11 15:30 ` rustom
2009-04-11 15:51 ` rustom
2009-04-11 18:30 ` Vagn Johansen
2009-04-12 8:56 ` rustom
2009-04-12 16:26 ` Vagn Johansen [this message]
2009-04-14 15:00 ` rustom
2009-04-14 17:23 ` Vagn Johansen
2009-04-15 10:29 ` Stefan Kamphausen
2009-04-08 18:10 grischka
-- strict thread matches above, loose matches on Subject: below --
2009-04-08 12:50 Damian
2009-04-08 15:59 ` Drew Adams
2009-04-08 18:21 ` Damian
2009-04-08 18:44 ` Drew Adams
2009-04-08 19:13 ` Damian
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=m2vdp9x2hl.fsf@hotmail.com \
--to=gonz808@hotmail.com \
--cc=help-gnu-emacs@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.