Re: [AUCTeX] AUCTeX 11.91 released
> Stefan, can't we simply delete it so that it'll always be generated > and issues like this one cannot occur anymore? We don't trust the packages enough to run their code on elpa.gnu.org, so we don't "make" while building the package. Hence tex-site.el is tracked (and you should manually "make" and commit the result before a new release). Stefan ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] Patch to tex-info.el to support node name completion in @..ref commands, and solve a few other pbs
> Ok, I should have read the *Help* more carefully, it states > (cl-pushnew X PLACE): insert X at the head of the list if not already > there. > and I understood "there" as meaning "head of the list", instead of just > "list". Of course the second sentence clarifies the point, but > I overlooked it. > Maybe it could be rephrased as: > (cl-pushnew X PLACE): insert X at the head of the list PLACE unless X is > already an element of PLACE. > If you agree with the rephrasal, I can implement the change. Fine by me, Stefan "not the maintainer any more" ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] Patch to tex-info.el to support node name completion in @..ref commands, and solve a few other pbs
> interest. Some time ago Stefan Monnier changed add-to-list by pushnew, I > don't know what the motivation was, probably somebody had complained > that add-to-list was taking too much time. add-to-list doesn't work on lexical variables. > However these are not functionally equivalent, pushnew will skip the > replacement only if the node name is already there on top of the list, > while add-to-list will skip it if it is already there at any place. Not so: (cl-)pushnew looks at the whole list as well. I don't have much opinion on this function in general, since I don't use it. All I care about is to not re-introduce the add-to-list abomination (it's fine for use in a user's ~/.emacs to add some element to a global variable, but definitely not when operating on a let-bound variable). Stefan ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] AUCTeX 11.87 released (elpa)
>> Is the elpa emacs branch to ELPA archive an automated procedure/cronjob >> nowadays? > Yes, a nightly cron job. So you probably want to either fix it quickly, > or revert the changes temporarily, work on a separate branch and merge > the result when it's stable. BTW, I've just changed the cron script so that it only creates a new package when the "version" is changed. As long as the "version" is not modified, the script assumes you're still working on the next release and the changes are not good enough to be release in the GNU ELPA archive. I also added a packages/README file that tries to explain it. Stefan ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] AUCTeX 11.87 released (elpa)
> Is the elpa emacs branch to ELPA archive an automated procedure/cronjob > nowadays? Yes, a nightly cron job. So you probably want to either fix it quickly, or revert the changes temporarily, work on a separate branch and merge the result when it's stable. Stefan ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
