On 1/27/06, Robert Abad <Robert_Abad(a)trimble.com> wrote:
> > > On 1/19/06, Robert Abad <Robert_Abad(a)trimble.com> wrote:
> > > > I recently installed XEmacs v21.4.18 on Windows XP machine
> > > using the
> > > > Inno-Setup exe program. I believe there are several issues
> > > with this
> > > > version and its installation:
> > > >
> > > > - Whenever I try to use a Tag Table, it always defaults to
> > > C:\TAGS (I
> > > > have C:\ set as my startup directory). It doesn't
> default to the
> > > > directory in which I used a shell to create a tags file or the
> > > > directory in which I have the currently opened file. This
> > > behavior is
> > > > very different from v21.4.13 (the previously released windows
> > > > version).
> > >
> > > I wouldn't expect this to be any different between the versions,
> > > actually. Where a particular TAGS table is found depends on the
> > > setting of the variable tag-table-alist. The info node on
> > > 'Selecting a Tags Table' tries to explain this.
> >
> > Let me elaborate a little more....
> >
> > In v21.4.13, I would open a file, say, C:\projects\src\junk.c. I
> > would then want to search for a tag (M-x tags-search).
> XEmacs would
> > then ask me (in the command line):
> >
> > Build tag completion table for c:\projects\src\TAGS? (y or n)
> >
> > I would hit 'y' for yes and the search would begin. I
> wouldn't have
> > to do anything with the variable tag-table-alist (unless it was
> > automatically done for me).
> >
> > v21.4.18 does not do this. I'll open the file just like before. I
> > invoke a tags search and the command line says (I don't
> remember the
> > exact words):
> >
> > C:\TAGS does not exist
> >
> > The search is then aborted. It won't let me specify a tags table
> > either via the menu Tools->Tags->Select Tags Table File...
> (which I
> > believe is the same as M-x visit-tag-table). My
> expectation was that
> > this would've behaved the same way that 21.4.13 behaved.
> >
>
> I don't see the behavior you described. Here's what I did:
>
> mkdir test
> cd test
> cp ~/cvsroot/xemacs-21.4/src/win* .
> etags *.c *.h
> xemacs-21.4 -vanilla
> C-x C-f window.c
> C-s XSETWINDOW
> M-. -> Find tag: (default XSETWINDOW) RET This loads the TAGS
> file and jumps to the definition of XSETWINDOW in window.h.
> The TAGS file is small enough not to prompt for a completion table.
>
> This is running the latest windows native XEmacs from the
> 21.4.19-pre5 setup kit (available from
>
ftp://ftp.xemacs.org/pub/xemacs/windows/testing).
>
> Do you see the problematic behavior in a xemacs started with
> the -vanilla option?
What is the -vanilla option???
I will try the 21.4.19 beta version and see what happens.
>
> If so, please file a bug report with the new XEmacs (the
> installation report you filed came from the 21.4.13 version).
>
> What does your etags file look like? Did you generate a
> fresh one using the etags that came with XEmacs?
>
Here are the keystrokes I used to find out about '-vanilla' in the XEmacs info:
C-h i m x e m a c s RET s - v a n i l l a RET s RET
decoded:
C-h i ; invoke info
mxemacs RET ; select the 'xemacs' node
s -vanilla RET ; search for the string '-vanilla'
s RET ; search again
And here's what info told me:
`-vanilla'
This is equivalent to `-q -no-site-file -no-early-packages'.
So, starting XEmacs with the -vanilla option is a way to take all user
and system customizations out of the equation.
Thanks for your testing.
HTH,
Vin
--
Whoever you are, no matter how lonely,
the world offers itself to your imagination,
calls to you like the wild geese, harsh and exciting--
over and over announcing your place
in the family of things. Mary Oliver