Hi Juanjo,

2018-04-17 18:26 GMT+02:00 Juan Jose Garcia-Ripoll
<[email protected]>:
> Dear all,
>
> please excuse my ignorance. I am a long time user of AucTeX, and I love it
> enough to have written a 300 page book and 120 articles with it.

Great to hear this!

>  However,
> throughout the lifetime of the project and my migration back to Windows, I
> have found some minor problems that I do not want to solve using local hacks
> of your functions.
>
> These include:
>
> * TeX-error-summary is arbitrarily closed by AucTeX before compilation,
> causing a new window to be created. In general the philosophy of how this
> buffer is handled deviates from that of other buffers (Help, manuals,
> compilations, etc)
>
> * AucTeX fails to parse error messages on MikTeX due to various issues,
> including spurious ^M characters sometimes popping up in packages.
>
> I would like to debug and work on both locally and contribute patches for
> both issues, but I find it very obscure how to do this. For starters, the
> ELPA package of AucTeX does not seem to match the sources that are available
> on Git.

The ELPA package is built from the git repo, but indeed you can't use
the ELPA package to develop the package itselft.

> My ideal workflow would be:
> * Develop on top of my git branch
> * Let Emacs do the importing of that branch

Actually, the question has been already asked a few times before, here
you can find a quick & dirty solution:
https://lists.gnu.org/archive/html/auctex/2013-08/msg00005.html.  At
https://savannah.gnu.org/git/?group=auctex you can find the
information about how to clone the git repository.

> P.S.: As a side question, why does the ELPA package eliminate all references
> to xemacs? Is this done automatically?

I'm not sure what "references" you're referring to.  AUCTeX dropped
support for XEmacs in version 12.

I'm looking forward to seeing your contributions!

Bye,
Mosè

_______________________________________________
auctex mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/auctex

Reply via email to