Richard Stallman <[EMAIL PROTECTED]> writes: > We changed the value of the EMACS envvar so as to fix a bug. That bug > was real and needed to be fixed, but the fix causes another problem. > > Making that fix an option is not a solution, since it just means > people choose between one bug or another bug. > > If people want to reopen this issue, the way to do it is to restudy > the original bug together with the new problems, and find the solution > that is best overall.
The issue is pretty simple: whether to EMACS to "t", or change it. IIUC, the original complaint is that Makefile.in in some projects use the EMACS variable to refer to the emacs executable, and setting the EMACS envvar to "t" confuses such build scripts. On the other hand, changing the EMACS envvar to something else confuses projects that expect "t". It's clearly one or the other. Personally, I think we should revert the changes, and get whichever projects use EMACS in their build scripts to use some other variable name instead. _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
