[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: etags name collision.
From: |
Alfred M. Szmidt |
Subject: |
Re: etags name collision. |
Date: |
Tue, 12 Apr 2022 03:16:50 -0400 |
>> Do one thing and do it right...
>
>And we don't??
ctags is a different "thing" than the emacs "thing" and with the current
support it has is not right (or good enough)... so... no one thing and
not right either...
Not all systems use Exuberant Ctags or Universal Ctags. On the BSDs,
ctags is compatible with the Emacs ctags output (which is why it
exists, AFAIR). Exuberant Ctags etc do not work with either vi(1) or
mg(1) on those systems, and their output is at odds with what is
standardized by POSIX.
So really, you're suggesting to remove a standardized utility and
replace it with non-standard ones that produce incompatible output
from what is generally accepted.
- etags name collision., Ergus, 2022/04/11
- Re: etags name collision., Eli Zaretskii, 2022/04/11
- Re: etags name collision., Dmitry Gutov, 2022/04/11
- Re: etags name collision., Ergus, 2022/04/11
- Re: etags name collision., Eli Zaretskii, 2022/04/11
- Re: etags name collision., Ergus, 2022/04/11
- Re: etags name collision.,
Alfred M. Szmidt <=
- Re: etags name collision., Andreas Schwab, 2022/04/12
- Re: etags name collision., Ergus, 2022/04/12
- Re: etags name collision., Po Lu, 2022/04/12
- Re: etags name collision., Ergus, 2022/04/12
- Re: etags name collision., Dmitry Gutov, 2022/04/12
- Re: etags name collision., Po Lu, 2022/04/12
- Re: etags name collision., Alfred M. Szmidt, 2022/04/12
- Re: etags name collision., Dmitry Gutov, 2022/04/12
- Re: etags name collision., Óscar Fuentes, 2022/04/12
- Re: etags name collision., Ergus, 2022/04/12