headers
Reiner Steib | 1 Aug 2012 21:11
X-Face

ChangeLog when syncing from Emacs (was: Changes to reftex/ChangeLog, v)

On Mon, Jul 30 2012, Tassilo Horn wrote:

> +	* textmodes/reftex-vars.el (reftex-label-alist-builtin): Add
> +	support for the lstlisting and minted environments, and for the
> +	ctable macro.
> +	* textmodes/reftex.el (reftex-compile-variables): Also recognize
> +	labels written in keyvals syntax.
> +
>  2010-11-06  Ralf Angeli  <angeli <at> caeruleus.net>
>
>  	* lisp/reftex-cite.el (reftex-create-bibtex-file): Make sure that

I think you should adjust the directories of the files.

Bye, Reiner.
--

-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/
Permalink | Reply | 1 comment |
headers
Tassilo Horn | 1 Aug 2012 21:53
Picon
Gravatar

Converting AUCTeX CVS to a modern dVCS

Hi all,

I'd love to move the auctex sources to some modern distributed version
control system.  I now had some time to do some testing, and AFAICS the
conversions look ok.  There are some minor things that need to be fixed,
e.g., there are some old committers I don't know and that aren't listed
on the savannah project page.

It would be good if others have a look at the conversions to check if
everything's allright.

Ok, so there's one conversion to Git.  You can clone it like so:

  % git clone http://tsdh.org/auctex.git

And alternatively, there's a conversion to GNU Bazaar.  Branch the trunk
branch like so (right now, there's no support for cloning a complete
shared repo with all branches, but it's on the bzr TODO list):

  % bzr branch http://www.tsdh.org/auctex.bzr/trunk auctex

I don't have a strong opinion about what dVCS we'll eventually use.  Git
seems to be a bit more popular (I also know it much better) and the Git
repo is about 10 times smaller than the bzr one.  Bazaar on the other
hand is a GNU project like AUCTeX and claims to be easier to use and
probably better supported on Windows.

Opinions, problems, suggestions welcome!

Bye,
(Continue reading)

Permalink | Reply | 23 comments |
headers
Tassilo Horn | 1 Aug 2012 21:54
Picon
Gravatar

Re: ChangeLog when syncing from Emacs

Reiner Steib <reinersteib+gmane <at> imap.cc> writes:

>> +	* textmodes/reftex-vars.el (reftex-label-alist-builtin): Add
>> +	support for the lstlisting and minted environments, and for the
>> +	ctable macro.
>> +	* textmodes/reftex.el (reftex-compile-variables): Also recognize
>> +	labels written in keyvals syntax.
>> +
>>  2010-11-06  Ralf Angeli  <angeli <at> caeruleus.net>
>>
>>  	* lisp/reftex-cite.el (reftex-create-bibtex-file): Make sure that
>
> I think you should adjust the directories of the files.

Good catch!  I'll do that now.

Bye,
Tassilo
Permalink | Reply | 0 comments |
headers
Ivan Andrus | 2 Aug 2012 11:13
Picon
Gravatar

Re: [Mac OS X] Advice on `TeX-view-program-list-builtin'

On Jul 31, 2012, at 7:22 PM, Moritz Ulrich wrote:

> Hello,
> 
> I just stumbled over the following comment in tex.el:
> 
> --8<---------------cut here---------------start------------->8---
> ;; XXX: We need the advice of a Mac OS X user to configure this
> ;; correctly and test it.
> ;;    ((eq system-type 'darwin)
> ;;     '(("Preview.app" "open -a Preview.app %o")
> ;;       ("Skim" "open -a Skim.app %o")
> ;;       ("displayline" "displayline %n %o %b")
> ;;       ("open" "open %o")))
> --8<---------------cut here---------------end--------------->8---
> 
> They seem to generally work on my machine, with the exception of
> displayinline as I don't have it installed.

You do have displayline installed (if you have Skim installed), it's
just that it's inside the Skim.app bundle, and so it's not in your
PATH.  Specifically it's at
Skim.app/Contents/SharedSupport/displayline .

> I'd suggest wrapping the %o in quotation marks as there might be
> problems with spaces in file names.

That's already taken care of on my machine (by escaping the spaces
with a backslash).  No doubt this is done by calling
`shell-quote-argument'.  That said, I can't get AUCTeX to compile a
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ivan Andrus | 2 Aug 2012 11:26
Picon
Gravatar

Re: Converting AUCTeX CVS to a modern dVCS

On Aug 1, 2012, at 9:53 PM, Tassilo Horn wrote:

> Hi all,
> 
> I'd love to move the auctex sources to some modern distributed version
> control system.  I now had some time to do some testing, and AFAICS the
> conversions look ok.  There are some minor things that need to be fixed,
> e.g., there are some old committers I don't know and that aren't listed
> on the savannah project page.

Awesome!  I would love to see this happen, particularly if it can help
development along.  I haven't had much time for AUCTeX development
(and maybe never will), but using a dvcs might make it easier to make
and contribute a few small fixes here and there since I wouldn't have
to worry about getting commit access etc.

Once it's on another VCS it will become easier to install it via MELPA.

> It would be good if others have a look at the conversions to check if
> everything's allright.
> 
> Ok, so there's one conversion to Git.  You can clone it like so:
> 
>  % git clone http://tsdh.org/auctex.git
> 
> And alternatively, there's a conversion to GNU Bazaar.  Branch the trunk
> branch like so (right now, there's no support for cloning a complete
> shared repo with all branches, but it's on the bzr TODO list):
> 
>  % bzr branch http://www.tsdh.org/auctex.bzr/trunk auctex
(Continue reading)

Permalink | Reply | 3 comments |
headers
Tassilo Horn | 2 Aug 2012 15:08
Picon
Gravatar

Re: Converting AUCTeX CVS to a modern dVCS

Ivan Andrus <darthandrus <at> gmail.com> writes:

> Awesome!  I would love to see this happen, particularly if it can help
> development along.

That's one of my main reasons to switch: get Ivan to work! ;-)

>> Opinions, problems, suggestions welcome!
>
> Personally, I'm a big fan of technical rather than political
> decisions.  I don't know either git or bzr very well (I use mostly
> hg), but I would slightly prefer git since there are several other
> projects that I am interested in which use git.

To me, there doesn't seem to be any major technical differences anymore.
Bzr used to be very slow compared to git, but it has become quite usable
in that respect over the time.

> For some reason I thought that AUCTeX would eventually be hosted
> inside the emacs tree.  Is that true at all?

It's still a project goal, yes.

> If that is a long term goal it _might_ be a reason to prefer bzr.

Neither git not bzr have some sync-between-different-repos support, so I
don't think there's any benefit in either direction.

Bye,
Tassilo
(Continue reading)

Permalink | Reply | 2 comments |
headers
David Kastrup | 2 Aug 2012 15:14
Picon
Picon

Re: Converting AUCTeX CVS to a modern dVCS

Tassilo Horn <tsdh <at> gnu.org> writes:

> Ivan Andrus <darthandrus <at> gmail.com> writes:
>
>> Awesome!  I would love to see this happen, particularly if it can help
>> development along.
>
> That's one of my main reasons to switch: get Ivan to work! ;-)
>
>>> Opinions, problems, suggestions welcome!
>>
>> Personally, I'm a big fan of technical rather than political
>> decisions.  I don't know either git or bzr very well (I use mostly
>> hg), but I would slightly prefer git since there are several other
>> projects that I am interested in which use git.
>
> To me, there doesn't seem to be any major technical differences anymore.
> Bzr used to be very slow compared to git, but it has become quite usable
> in that respect over the time.
>
>> For some reason I thought that AUCTeX would eventually be hosted
>> inside the emacs tree.  Is that true at all?
>
> It's still a project goal, yes.
>
>> If that is a long term goal it _might_ be a reason to prefer bzr.
>
> Neither git not bzr have some sync-between-different-repos support, so I
> don't think there's any benefit in either direction.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Tassilo Horn | 2 Aug 2012 15:36
Picon
Gravatar

Re: Converting AUCTeX CVS to a modern dVCS

David Kastrup <dak <at> gnu.org> writes:

>> Neither git not bzr have some sync-between-different-repos support,
>> so I don't think there's any benefit in either direction.
>
> Hm? git has submodule support.  You can pull to and push to a
> submodule.  To make this useful with regard to Emacs/AUCTeX, the Emacs
> part of AUCTeX would have to be contained in a separate subdirectory.

You mean in emacs there was lisp/textmodes/auctex/ and in auctex we'd
move the lisp files into a separate directory auctex/lisp/ (a
submodule), and between those we could sync?

> I don't know if Bazaar has anything akin to that.

There's a ticket: https://bugs.launchpad.net/bzr/+bug/769629

> Any kind of automatic repository sync would require a compatible
> directory organization, and I somewhat doubt that this would be easy
> to achieve.

Probably.

Bye,
Tassilo
Permalink | Reply | 0 comments |
headers
Ralf Angeli | 17 Aug 2012 10:40

Re: Problème with AUCTeX Manual

* Tassilo Horn (2012-08-17) writes:

> vincent.belaiche <at> gmail.com (Vincent Belaïche) writes:
>
>> Recently I tried to compile the AUCTeX manual. I am using latest
>> Texinfo compiler texi2any based on perl, and there were several
>> compilation errors. I double checked with Patrice Dumas who is the
>> main developper of texi2any and he proposed the attached patch.
>
> Committed with some minor modifications to the ChangeLog entry.

Note that the  <at> LaTeX macro is not available with all versions of
Texinfo.  I think it was introduced some time around 4.8.  Not sure if
this version is still used actively.  Probably not, so it should not be
a problem.

--

-- 
Ralf
Permalink | Reply | 0 comments |
headers
Jason Hemann | 30 Aug 2012 03:01
Picon

Windows experience installing auctex

Hi,

You all had written asking for Windows users to write in with what worked, what didn't so that you all'd be able to improve for future releases. I'm including the steps I went through in getting my install going. I didn't quite make it, but I overcame a couple of issues I was having, hopefully this'll be useful. 

I'm on Windows 7 x64, using the version of gswin32c packaged with Lyx, emacsW32 (pre-built for windows: http://ourcomments.org/Emacs/EmacsW32.html) with the git bash shell, based upon MSYS. 


1. I have multiple texmf directories. One managed by MikTeX and one local I manage myself. It'd be nice to not have to worry about that. 

2. The Git Bash uses the MSYS program; many windowzers might already have it without having to download&install MSYS. 

3. Many windows folk used the pre-patched windows emacs intalls available here: it might be worthwhile to mention it, so folk aren't scared off thinking auctex is incompatible with them


4. Under the --infodir=DRIVE:/PATH/... option, it stipulates that 'If you are installing into an Emacs directory, do X'. It wasn't initially clear to me what an 'emacs directory' is. 


5.** ./configure. The makefile generated in the /doc, etc can't find files listed in /c/Program Files/... or anything outside my basic user directory 

I had to rename /c/Program\ Files/MiKTeX\ 2.9/miktex/bin/x64/dvips to "C:\\Program Files\\MiKTeX 2.9\\miktex\\bin\\x64\\dvips" to make it work. Note those quotes were a part of the variable assignment.

6. I had to do the same with the calls to tex and pdflatex and latex

For some reason I couldn't get them to work in that exact fashion (i think it may have been a privilege or rights problem, but I couldn't ascertain -- I was running as an elevated user) Anyway, what I ended up doing was symlinking the MiKTeX binary directory to some place in my userspace, and then changed the filenames to point to that. 

7. Even after successfully make-ing, make install gave me some interesting issues. basename program wasn't running on the command line as it ought. 
I think there might be an issue with backtick running under MSYS or git bash on windows. I just renamed the file to what its supposed to be in my instance "tex-site.el". Yucky, though.

8. I got as far as mv-ing the generated file to site-tex.el not working, just a *few* steps away, and I just don't have any more time to putting into this.

Thanks so much, and hope this helps somebody. Lemme know if I can offer more clarification or help in some fashion.

Best, 

JBH
_______________________________________________
auctex-devel mailing list
auctex-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
Permalink | Reply | 0 comments |

Gmane