revno: 433
revision-id: monn...@iro.umontreal.ca-20130809020004-wchassib8v7g6pcq
parent: jul...@danjou.info-20130805185400-g8udkbpca0ab5ien
committer: Stefan Monnier
branch nick: elpa
timestamp: Thu 2013-08-08 22:00:04 -0400
message
revno: 415
revision-id: monn...@iro.umontreal.ca-20130703233635-19gmox9sjjwd8ge1
parent: jul...@danjou.info-20130629083454-96bacu87k5h4y2qi
committer: Stefan Monnier
branch nick: elpa
timestamp: Wed 2013-07-03 19:36:35 -0400
message
>> Can you describe how does the XEmacs-package-building relates to the
>> VCS repository? Is it that the CVS layout was chosen specifically to
>> match the XEmacs package requirements?
> No. XEmacs was supported after the CVS layout had been established. An
> XEmacs package is assembled in a ta
> The XEmacs package building is sort of an aggravation. An XEmacs
> package contains all necessary files plus info source files in a rigid
> directory layout, possibly not unsimilar to what ELPA or any other
> package would do.
Can you describe how does the XEmacs-package-building relates to the
> So I contemplate giving up on the separate repository and maintaining
> it in the Emacs repository. But this should likely be discussed in
> another thread.
You have my vote,
Stefan
___
auctex-devel mailing list
auctex-devel@gnu.org
http://
ly did nothing when reaching BOB), which
I've just fixed. I also additionally installed the patch below which
circumvents the bug and also avoids slowing things down unnecessarily.
Stefan
=== modified file 'lisp/ChangeLog'
--- lisp/ChangeLog 2010-09-20 21:45:09 +
+++ l
> Since I've never gotten commit access to the Emacs repository I haven't
That should be easy to fix. Get a Savannah account, and from there, ask
for membership to the Emacs group.
> bothered to follow the switch to Bazaar. It might take a while to make
> myself acquainted with it. And unfortu
> Does "drop non-ascii chars" mean that "räksmörgås" becomes "rksmrgs",
> or "raksmorgas"? I'm afraid you mean the former ... But what would
> such a function do to a Greek/Cyrillic/Japanese BibTeX entry? I'd
> guess there is nothing left when you drop non-ascii chars.
Yup, there's nothing left.
>> text-mode:Grüß Gott
>> tex-mode: Gr\"u{\ss} Gott
>> german latex-mode:Gr"u"s Gott
>> html-mode:Grüß Gott
AFAIK, nowadays in LaTeX, you're better off using "Grüß Gott" with the
proper input encoding. For HTML mode as well.
ELISP> (reftex-latin1-to-ascii
>>> One could achieve this with a two-step approach of creating a package and
>>> then installing it, of course.
>>
>> Yes. Although right now there's no code to actually *create* a package ;-)
> I know, and I am wondering if install.el would be the right place for
> including that functionality
> Please also keep in mind people who want to create distribution packages
> (deb or rpm or similar):
This seems orthogonal. Such package management system typically work on the
output of the equivalent of "make install".
> - Compilation will most probably be done at the time the deb/rpm is
>
> As far as I can see the intent is to extract a tar ball at a target
> location, e.g. site-lisp, and then compile everything in place.
Yes, pretty much. The "all-in-one-place" end result is what
really matters. It makes package management tremendously easier:
- no need to track sets of files in
>> That looks OK. If install.el does its job properly it will
>> - untar this into the user's elisp repository (~/lib/emacs or ~/share/emacs
>> if I were to choose).
>> - build the .elc and .info files.
>> - construct a "autoloads" file that contains the relevant autoloads, as well
>> as commands
>> One point of note: install.el is meant to be included in Emacs to help
>> install external packages (it would then be supplemented with a package
>> manager that could list the installed packages, select which ones to
>> (de)activate, deinstall, etc..). I.e. it's not meant to be specific to any
> Would you have any comments and/or would you consider active
> participation in a project to move RefTeX and maybe later AUCTeX to an
> Elisp-based installation?
Sounds like a good idea.
> Is the latest version of your style the one
> on http://www.iro.umontreal.ca/~monnier/elisp/install.el>?
> There will be standalone releases of RefTeX. That means files for
> building and installing RefTeX as well as files like README, INSTALL,
> etc. would have to be added to Emacs' repository.
Those can easily be put into the `admin' subdirectory which is not included
in Emacs releases.
> And we'
> maintenance of RefTeX will likely be continued by the AUCTeX project.
> On the AUCTeX developers list it is currently being discussed how
> maintenance of RefTeX will be done in its own CVS repository.
> Something it hasn't had before. Since RefTeX is also present in the
> CVS repository of Emac
101 - 117 of 117 matches
Mail list logo
