Bug#3013: elvis is too granular and has short description
Bill Mitchell <mitchell@mdd.comm.mot.com> writes:
> I moved ctags out to a single package because I thought that it was even
> sillier to have elvis conflict with emacs. I suggested update-alternatives
> at one time, but got no response. Ian Murdock, you're the emacs maintainer.
> What's your pleasure?
Actually, I'm handling emacs as of 19.31. I don't see any
documentation (at least in anything that's made it to a mirror) that
mentions it, but from the vi and gawk examples, I think I see what it
would do...
Do we need to pick a "real" name, like "tags" and then use something
like --program-transform-name to have xemacs and fsfemacs install
something like ctags-emacs and ctags-xemacs, and likewise for etags,
so that a user just drops the package in place and gets *some* version
of ctags and *some* version of etags? If that makes sense, it solves
this problem as well as the emacs19/xemacs support-program conflicts,
I think...
Let me know if this makes sense, and I'll work it into 19.31.
Reply to: