* Re: ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers]
[not found] <786EBDA1AC46254B813E200779E7AD36028CB12E@srv1163ex1.flightsafety.com>
@ 2012-12-12 9:40 ` Corinna Vinschen
2012-12-12 14:29 ` Warren Young
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: Corinna Vinschen @ 2012-12-12 9:40 UTC (permalink / raw)
To: cygwin-apps; +Cc: Dr. Volker Zell, Warren Young
[Redirected to cygwin-apps]
On Dec 11 14:05, Thrall, Bryan wrote:
> Alan Thompson wrote on 2012-12-11:
> > Looking at the link on StackOverflow (from 2010) it may be that the
> > xemacs version of ctags is overwriting the default version in /bin.
> > Could this be the culprit?
>
> Yes, it looks like xemacs-tags and ctags packages both install
> /usr/bin/ctags.exe:
>
> http://cygwin.com/cgi-bin2/package-grep.cgi?grep=ctags.exe
Oh boy, how long do we have this collisions? For years, it seems.
FWIW, I'd prefer to keep Exuberant ctags since that's what is part
of most Linux installations as well.
Volker, would you mind a lot to obsolete the xemacs-tags package
in favor of the ctags package?
Thanks,
Corinna
>
> > On Tue, Dec 11, 2012 at 11:55 AM, Alan Thompson
> > <...> wrote:
> >> Hi - Yes, I'm sure:
> >>
> >>> find /bin -name '*tags*' | xargs ls -ldF
> >> -rwxr-xr-x 1 alathompson Domain Users 85504 Jan 31 2009
> /bin/ctags.exe*
> >> -rwxr-xr-x 1 alathompson Domain Users 83968 Jan 31 2009
> /bin/etags.exe*
> >> -rwxr-xr-x 1 alathompson Domain Users 5411 Dec 21 2011
> /bin/ocamltags*
> >> -rwxr-xr-x 1 alathompson Domain Users 68608 Jan 31 2009
> > /bin/ootags.exe*
> >>> ls -ldF /bin/ls /bin/vim /bin/gcc
> >> lrwxrwxrwx 1 alathompson Domain Users 21 Oct 18 12:20 /bin/gcc ->
> >> /etc/alternatives/gcc*
> >> -rwxr-xr-x 1 alathompson Domain Users 101902 Feb 6 2012 /bin/ls*
> >> lrwxrwxrwx 1 alathompson Domain Users 21 Oct 18 12:48 /bin/vim ->
> >> /etc/alternatives/vim*
> >>>
> >>> uname -a
> >> CYGWIN_NT-6.1-WOW64 ALAN-THO-LAP 1.7.16(0.262/5/3) 2012-07-20
> > 22:55 i686 Cygwin
> >>>
> >>
> >> One can see from the timestamp on the links for gcc and vim that I
> >> installed Cygwin on 10/18/2012. However, it seems that both ctags
> and
> >> etags are old versions of the program (circa 2007) and are not the
> >> Exuberant Ctags version. However, the GNU documentation here:
> >> http://directory.fsf.org/wiki/Exuberant_Ctags clearly lists the
> >> Exuberant Ctags, although it has only been updated as of 2004.
> >> However, looking here:
> >> http://cygwin.com/packages/ctags/ctags-5.8-1-src we see that cygwin
> >> has Exuberant Ctags 5.8. Perhaps it is just a packaging issue that
> >> caused the old one to be present and Exuberant Ctags 5.8 to be not
> >> present?
> >>
> >> You can see from this thread:
> >> http://stackoverflow.com/questions/2634001/any-idea-why-ctags-wont-
> > recurse-on-cygwin/13810472#13810472
> >> that I'm not the only one who stumbled onto this problem.
> >> Where should we go from here? Could it just be a packaging problem?
> >> Alan Thompson
> >>
> >>
> >> On Tue, Dec 11, 2012 at 11:24 AM, Thrall, Bryan
> >> <...> wrote:
> >>>
> >>> Are you sure you're using the ctags you think you are?
> >>>
> >>> $ ctags --help
> >>> Exuberant Ctags 5.8, Copyright (C) 1996-2009 Darren Hiebert
> >>> Compiled: Dec 11 2009, 11:42:40 Addresses:
> >>> <dhiebert@users.sourceforge.net>, http://ctags.sourceforge.net
> >>> Optional compiled features: +wildcards, +regex, +internal-sort
> >>> Usage: ctags [options] [file(s)]
> >>> <snip>
> >>> -R Equivalent to --recurse.
> >>> <snip>
> >>>
> >>> Hope this helps!
> >>> --
> >>> Bryan Thrall
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers]
2012-12-12 9:40 ` ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers] Corinna Vinschen
@ 2012-12-12 14:29 ` Warren Young
2012-12-12 14:49 ` Aaron Schneider
2012-12-12 22:41 ` Dr. Volker Zell
2 siblings, 0 replies; 7+ messages in thread
From: Warren Young @ 2012-12-12 14:29 UTC (permalink / raw)
To: cygwin-apps
On 12/12/2012 02:39, Corinna Vinschen wrote:
> Oh boy, how long do we have this collisions? For years, it seems.
There must be a database of package contents behind the packages search
engine on sourceware. If someone that has access to that DB extracts a
raw list of file names, this command will find the other duplicates:
grep -o '/[a-z0-9]+\.exe$' filelist | sort | uniq -d
Some will be harmless, like the two ksh.exe versions. But, maybe
something interesting will turn up.
> Volker, would you mind a lot to obsolete the xemacs-tags package
> in favor of the ctags package?
As long as Exuberant Ctags is a complete superset of the functionality
in xemacs-tags, this seems like a good idea. Anything that depends on
xemacs-tags can depend on the ctags package instead.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers]
2012-12-12 9:40 ` ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers] Corinna Vinschen
2012-12-12 14:29 ` Warren Young
@ 2012-12-12 14:49 ` Aaron Schneider
2012-12-12 14:58 ` Corinna Vinschen
2012-12-12 15:05 ` Jari Aalto
2012-12-12 22:41 ` Dr. Volker Zell
2 siblings, 2 replies; 7+ messages in thread
From: Aaron Schneider @ 2012-12-12 14:49 UTC (permalink / raw)
To: cygwin-apps
On 12/12/2012 10:39, Corinna Vinschen wrote:
> Oh boy, how long do we have this collisions? For years, it seems.
I request a feature to detect package collision, and furthermore suggest
which package to install when an user tries to run a program which is
not installed but is available from a package.
Such feature has been implemented in Ubuntu, for example:
https://blueprints.launchpad.net/ubuntu/+spec/command-not-found-magic
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers]
2012-12-12 14:49 ` Aaron Schneider
@ 2012-12-12 14:58 ` Corinna Vinschen
2012-12-12 15:05 ` Jari Aalto
1 sibling, 0 replies; 7+ messages in thread
From: Corinna Vinschen @ 2012-12-12 14:58 UTC (permalink / raw)
To: cygwin-apps
On Dec 12 15:48, Aaron Schneider wrote:
> On 12/12/2012 10:39, Corinna Vinschen wrote:
> >Oh boy, how long do we have this collisions? For years, it seems.
>
> I request a feature to detect package collision, and furthermore
> suggest which package to install when an user tries to run a program
> which is not installed but is available from a package.
>
> Such feature has been implemented in Ubuntu, for example:
>
> https://blueprints.launchpad.net/ubuntu/+spec/command-not-found-magic
http://cygwin.com/acronyms/#SHTDI
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers]
2012-12-12 14:49 ` Aaron Schneider
2012-12-12 14:58 ` Corinna Vinschen
@ 2012-12-12 15:05 ` Jari Aalto
2012-12-12 15:21 ` Thrall, Bryan
1 sibling, 1 reply; 7+ messages in thread
From: Jari Aalto @ 2012-12-12 15:05 UTC (permalink / raw)
To: cygwin-apps
On 2012-12-12 15:48, Aaron Schneider wrote:
| On 12/12/2012 10:39, Corinna Vinschen wrote:
| >Oh boy, how long do we have this collisions? For years, it seems.
|
| I request a feature to detect package collision, and furthermore
| suggest which package to install when an user tries to run a program
| which is not installed but is available from a package.
This helps:
$ cygcheck --help
...
-f, --find-package find the package to which FILE belongs
$ cygcheck -f /usr/bin/ls
coreutils-8.15-1
I wouldn't want the screen to be filled with messages every time I
mispell a command that might exist in some package.
Jari
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers]
2012-12-12 15:05 ` Jari Aalto
@ 2012-12-12 15:21 ` Thrall, Bryan
0 siblings, 0 replies; 7+ messages in thread
From: Thrall, Bryan @ 2012-12-12 15:21 UTC (permalink / raw)
To: cygwin-apps; +Cc: Thrall, Bryan
Jari Aalto wrote on 2012-12-12:
> On 2012-12-12 15:48, Aaron Schneider wrote: | On 12/12/2012 10:39,
> Corinna Vinschen wrote: | >Oh boy, how long do we have this
collisions?
> For years, it seems. | | I request a feature to detect package
> collision, and furthermore | suggest which package to install when an
> user tries to run a program | which is not installed but is available
> from a package.
>
> This helps:
>
> $ cygcheck --help
> ...
> -f, --find-package find the package to which FILE belongs
>
> $ cygcheck -f /usr/bin/ls
> coreutils-8.15-1
That only works on files whose package is installed, unfortunately.
http://www.cygwin.com/packages is the tool to use for this.
--
Bryan Thrall
Principal Software Engineer
FlightSafety International
bryan.thrall@flightsafety.com
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers]
2012-12-12 9:40 ` ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers] Corinna Vinschen
2012-12-12 14:29 ` Warren Young
2012-12-12 14:49 ` Aaron Schneider
@ 2012-12-12 22:41 ` Dr. Volker Zell
2 siblings, 0 replies; 7+ messages in thread
From: Dr. Volker Zell @ 2012-12-12 22:41 UTC (permalink / raw)
To: cygwin-apps; +Cc: Dr. Volker Zell, Warren Young
>>>>> Corinna Vinschen writes:
> Volker, would you mind a lot to obsolete the xemacs-tags package
> in favor of the ctags package?
I will have a look on the weekend,
> Thanks,
> Corinna
Ciao
Volker
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2012-12-12 22:41 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <786EBDA1AC46254B813E200779E7AD36028CB12E@srv1163ex1.flightsafety.com>
2012-12-12 9:40 ` ctags recursion broken? [ATTN: ctags, xemacs-tags maintainers] Corinna Vinschen
2012-12-12 14:29 ` Warren Young
2012-12-12 14:49 ` Aaron Schneider
2012-12-12 14:58 ` Corinna Vinschen
2012-12-12 15:05 ` Jari Aalto
2012-12-12 15:21 ` Thrall, Bryan
2012-12-12 22:41 ` Dr. Volker Zell
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).