Thorsten | 13 Feb 10:38 2012

No ESS autoloads?


Hello list, 
I try to mix the emcas24-starter-kit with el-get, i.e. I use el-get for
all the packages I can't get from elpa instead of simply putting the .el
files into the starter-kit src folder like recommended. 

But some el-get recipes did not work for me (magit [on elpa too] and
emacs-goodies-el), others produce no working autoloads (e.g. ESS) so I
have to require the packages.    

Am I the only one having this problems?

cheers
Thorsten

--

-- 
To unsubscribe, send mail to el-get-devel-unsubscribe@...

John Owens | 23 Nov 22:32 2011
Picon

setting path for el-get for running autogen

Hi, I'm running el-get for the first time. It successfully installed wanderlust,
which was great, so now I'm trying auctex.

The auctex install needs a bunch of tex binaries to complete. Fair enough.
I have /usr/texbin set in my .bash_profile and set in my exec-path within 
emacs. However, el-get does not appear to see that directory at all.

How can I specify an additional binary directory for el-get to use when it
runs shell scripts?

(Emacs 24 pretest, OS X 10.7.2)

JDO

--

-- 
To unsubscribe, send mail to el-get-devel-unsubscribe@...

Dimitri Fontaine | 25 Oct 20:53 2011

https://github.com/dimitri/el-get/pull/388

Hi,

Gergely Risko <gergely@...> writes:
> Sorry for the late reply on this, I didn't have time for a while.

No problem, there's no time pressure on this topic :)

> Maybe I'm paranoid, but I don't feel comfortable of getting something
> from emacswiki that can be changed by anyone without any kind of review.
> Therefore for my http based packages, I would like to add a sha1 check.

I can see that need as being worth of integrating properly into el-get
itself rather than hacked around with a more generic facility.

What about a new property :sha1 in `el-get-sources'?

We would then check at install that the package we got has the same
checksum than what's in the property. As Emacs 23 and 24 both have a
sha1 function we could use that against the given file, or a binary
buffer containing the archive if that's what you're offered.

On the first install I guess you wouldn't have any :sha1 property into
your list.  You would get the sha1 from the M-x el-get-checksum command,
that would compute it, message it, and add it to the kill ring.

Now, what happens on update?  Do you want to have to remove your
checksum from the list to be able to update?

Regards,
--

-- 
(Continue reading)

Nap Travel | 14 Oct 19:09 2011

Cruceros temporada 2012

Versión Online | |
<!-- /*<![CDATA[*/ <! .texto {text-align: center; font-family: Tahoma, Geneva, sans-serif; font-size: 12px; } -->/*]]>*/ --> -->
Si usted no visualiza correctamente este e-mail haga clic aqui.
Para dejar de recibir estos mensajes, haga click en el siguiente enlace: desuscribir
Este mensaje fue enviado a el-get-devel-nvISmQEVr2dAfugRpC6u6w@public.gmane.org por NAP TRAVEL
FLORIDA 890, BS AS, Argentina
Lachlan Deck | 11 Oct 19:18 2011
Picon

sync misunderstanding

Hi there,

I've recently set up el-get (which is very useful!) but had a problem where el-get wasn't pulling in newly
added items which I didn't understand as to why not. I'm using the "master" branch  <at>  HEAD

So I've got something like:

(setq el-get-sources
  '(...)
)

(setq msk-el-get-packages
  (append
    '()
    (mapcar 'el-get-source-name el-get-sources)
))

(el-get 'sync msk-el-get-packages)
(el-get 'wait)

i.e., I was trying to define everything via el-get-sources which seemed to work to a point. e.g., I had the
starter-kit listed from github etc

Anyway, I went to enable another feature of the starter-kit, starter-kit-lisp which had a few
dependencies. So I added
    (:name starter-kit
     <...>
     :depends (elisp-slime-nav
               idle-highlight-mode
               inf-ruby
               paredit)
     :after (lambda ()
             (progn
              (require 'idle-highlight-mode)
              (require 'paredit)
              (require 'starter-kit-lisp)
              etc)))
    (:name idle-highlight-mode
           :type elpa)

Except it didn't pull down idle-highlight-mode at all. Any ideas why?

Lachlan Deck
lachlan.deck@...

--

-- 
To unsubscribe, send mail to el-get-devel-unsubscribe@...

Themba Fletcher | 9 Sep 16:46 2011
Picon

Initial install broken due to github redirect

https://github.com/dimitri/el-get/blob/master/README.asciidoc has lazy install 
instructions as follows:

;; So the idea is that you copy/paste this code into your *scratch* buffer,
;; hit C-j, and you have a working el-get.
(url-retrieve
 "https://github.com/dimitri/el-get/raw/master/el-get-install.el"
 (lambda (s)
   (end-of-buffer)
   (eval-print-last-sexp)))

As of this morning this was not working. curl showed me that the above url was 
being redirected by github to https://raw.github.com/dimitri/el-get/master/el-
get-install.el

Changing the url and eval'ing the following code seems to have worked:
(url-retrieve
 "https://raw.github.com/dimitri/el-get/master/el-get-install.el"
 (lambda (s)
   (end-of-buffer)
   (eval-print-last-sexp)))

Not sure if this is a recent change by github or if the redirect should have 
worked on my system. Just in case,

tif <at> whiskey-five:~$ uname -a
Linux whiskey-five 2.6.38-11-generic #48-Ubuntu SMP Fri Jul 29 19:02:55 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

tif <at> whiskey-five:~$ emacs --version
GNU Emacs 23.2.1
-snip-

tif <at> whiskey-five:~$ openssl version
OpenSSL 0.9.8o 01 Jun 2010

Followups via email as necessary please, as I am not subscribed to this group.

Regards,

Themba

--

-- 
To unsubscribe, send mail to el-get-devel-unsubscribe@...

David Abrahams | 24 Jun 06:59 2011
Picon
Picon

el-get is broken **again**


I just updated and this is what happens when I start emacs.

Debugger entered--Lisp error: (error "el-get can not find a recipe for package \"test-recipe\".")
  signal(error ("el-get can not find a recipe for package \"test-recipe\"."))
  error("el-get can not find a recipe for package \"%s\"." "test-recipe")
  (if filename (el-get-read-recipe-file filename) (error "el-get can not find a recipe for package
\"%s\"." package))
  (let ((filename ...)) (if filename (el-get-read-recipe-file filename) (error "el-get can not find a
recipe for package \"%s\"." package)))
  el-get-read-recipe("test-recipe")
  (cond ((or ... ...) (el-get-read-recipe package)) ((null ...) (loop with def = ... for ... on source by ...
do ... finally return def)) (t source))
  (let ((source ...)) (cond (... ...) (... ...) (t source)))
  el-get-package-def("test-recipe")
  (let* ((source ...) (method ...) (deps ...)) (if (and ... ...) (cons ... deps) deps))
  el-get-dependencies(test-recipe)
  (remove-if (quote el-get-package-initialized-p) (el-get-dependencies psym))
  (let ((non-installed-dependencies ...)) (dolist (dep non-installed-dependencies)
(el-get-add-generic-event-task ... ...) (el-get-add-generic-event-task ... ...) (el-get-install
dep)) (unless non-installed-dependencies (el-get-demand1 psym)))
  (if (memq (el-get-package-state psym) (quote ...)) nil (el-get-set-package-state psym (quote
installing)) (let (...) (dolist ... ... ... ...) (unless non-installed-dependencies ...)))
  (unless (memq (el-get-package-state psym) (quote ...)) (el-get-set-package-state psym (quote
installing)) (let (...) (dolist ... ... ... ...) (unless non-installed-dependencies ...)))
  (let* ((psym ...) (pname ...)) (unless (memq ... ...) (el-get-set-package-state psym ...) (let ... ... ...)))
  (condition-case err (let* (... ...) (unless ... ... ...)) ((debug error) (el-get-installation-failed
package err)))
  (if (el-get-package-is-installed package) (message "el-get: `%s' package is already installed"
package) (condition-case err (let* ... ...) (... ...)))
  el-get-install("test-recipe")
  (while (consp --cl-var--) (setq p (car --cl-var--)) (el-get-install p) (push p --cl-var--) (setq
--cl-var-- (cdr --cl-var--)))
  (let* ((--cl-var-- to-install) (p nil) (--cl-var-- nil)) (while (consp --cl-var--) (setq p ...)
(el-get-install p) (push p --cl-var--) (setq --cl-var-- ...)) (nreverse --cl-var--))
  (catch (quote --cl-block-nil--) (let* (... ... ...) (while ... ... ... ... ...) (nreverse --cl-var--)))
  (cl-block-wrapper (catch (quote --cl-block-nil--) (let* ... ... ...)))
  (block nil (let* (... ... ...) (while ... ... ... ... ...) (nreverse --cl-var--)))
  (loop for p in to-install do (el-get-install p) collect p)
  (append (loop for p in to-install do (el-get-install p) collect p) (loop for p in to-init do (el-get-init p)
collect p))
  (let* ((--cl-var-- ...) (p nil) (--cl-var-- nil)) (while (consp --cl-var--) (setq p ...) (push p
--cl-var--) (setq --cl-var-- ...)) (nreverse --cl-var--))
  (catch (quote --cl-block-nil--) (let* (... ... ...) (while ... ... ... ...) (nreverse --cl-var--)))
  (cl-block-wrapper (catch (quote --cl-block-nil--) (let* ... ... ...)))
  (block nil (let* (... ... ...) (while ... ... ... ...) (nreverse --cl-var--)))
  (loop for p in (append (loop for p in to-install do ... collect p) (loop for p in to-init do ... collect p))
collect p)
  (let* ((required ...) (installed ...) (to-init ...) (to-install ...)) (el-get-verbose-message
"el-get-init-and-install: init %S" to-init) (el-get-verbose-message "el-get-init-and-install:
install %S" to-install) (loop for p in (append ... ...) collect p))
  el-get-init-and-install()
  apply(el-get-init-and-install nil)
  (prog1 (apply (quote el-get-init-and-install) packages) (when progress (let* ... ... ...)) (unless
el-get-outdated-autoloads (el-get-eval-autoloads)))
  (let ((previously-installing ...) (progress ...) (el-get-default-process-sync sync)) (prog1 (apply
... packages) (when progress ...) (unless el-get-outdated-autoloads ...)))
  el-get()
  eval-buffer(#<buffer  *load*≤2>> nil "/Users/dave/.emacs.d/el-get/elhome/startup/10-el-get.el"
nil t)  ; Reading at buffer position 355
  load-with-code-conversion("/Users/dave/.emacs.d/el-get/elhome/startup/10-el-get.el"
"/Users/dave/.emacs.d/el-get/elhome/startup/10-el-get.el" nil t)
  load("/Users/dave/.emacs.d/el-get/elhome/startup/10-el-get" nil t)
  (lambda (file) (load file nil t))("/Users/dave/.emacs.d/el-get/elhome/startup/10-el-get")
  mapc((lambda (file) (load file nil t))
("/Users/dave/.emacs.d/el-get/elhome/startup/00-me-minor-mode"
"/Users/dave/.emacs.d/el-get/dwamacs/startup/01-global-keybindings"
"/Users/dave/.emacs.d/el-get/elhome/startup/05-after-load"
"/Users/dave/.emacs.d/el-get/elhome/startup/10-el-get"
"/Users/dave/.emacs.d/el-get/elhome/startup/20-initsplit"
"/Users/dave/.emacs.d/el-get/elhome/startup/30-elhome-settings" "/Users/dave/.emacs.d/el-get/dwamacs/startup/99-sugar"))
  elhome-init()
  eval-buffer(#<buffer  *load*≥ nil "/Users/dave/.emacs.d/init.el" nil t)  ; Reading at buffer position 389
  load-with-code-conversion("/Users/dave/.emacs.d/init.el" "/Users/dave/.emacs.d/init.el" t t)
  load("/Users/dave/.emacs.d/init" t t)
  #[nil "\205\264

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

--

-- 
To unsubscribe, send mail to el-get-devel-unsubscribe@...

Dimitri Fontaine | 22 Jun 23:02 2011

el-get-sources is just another recipe source

Hi,

After some more pondering about it, I've recently pushed a series of
changes in el-get.  The main commit would be the following:

  commit 8f886c07d267894263e5c9818c60ada480aa7e0a
  Author: Dimitri Fontaine <dim@...>
  Date:   Wed Jun 22 11:38:40 2011 +0200

    `el-get' now defaults to caring about packages known "required" and "installed" from the status file.

    This should bring a much easier to understand semantics, near of that of
    apt-get and friends: by default, any installed package is automatically
    initialized at next startup without special care.  If you don't need local
    recipes, you don't need to edit and maintain any `el-get-sources'.

    It's still possible to manually prepare a list of packages to install, so
    that you can share your setup between multiple installations.  To do that,
    give the package list (names or symbols) to the (el-get) call in your setup.
    This way you can also maintain specific lists depending on system or network
    or whatever is useful for you.  That's the advanced setup, documented.

That means that I believe the problem and difficulties reported by
Richard are now solved, in a way that still allow advanced users to
still be able to sync several Emacs installations.

Basic usage involves caring about the load-path to be able to require
el-get and then place a call to (el-get 'sync), and that's about it.
You install packages using M-x el-get-install, you restart Emacs and
there you go.

But if you want to share the package list then you might need something
a little more involved.  Here's what the emacs-kicker is now looking
like:

    ;; set local recipes
    (setq el-get-sources
     '((:name magit
    	  :after (lambda ()
    		   (global-set-key (kbd "C-x C-z") 'magit-status)))))

    ;; now set our own packages    
    (setq my:el-get-packages '(el-get escreen ...))

    (setq my:el-get-packages
          (append
           my:el-get-packages
           (loop for src in el-get-sources collect (el-get-source-name src))))

    ;; install new packages and init already installed packages
    (el-get 'sync my:el-get-packages)

Regards,
-- 
dim

--

-- 
To unsubscribe, send mail to el-get-devel-unsubscribe@...

buildbot | 20 Jun 17:52 2011
Picon

buildbot failure in BoostPro FOSSbot on el-get-23.3-linux-elisp

The Buildbot has detected a new failure on builder el-get-23.3-linux-elisp while building Boost.Modularize.
Full details are available at:
 http://bbot.boostpro.com/builders/el-get-23.3-linux-elisp/builds/0

Buildbot URL: http://bbot.boostpro.com/

Buildslave for this Build: boostpro-ubu11.04x64-2

Build Reason: scheduler
Build Source Stamp: [branch fossbot-test] c1a3f4092da5f227a8a74e82e948e87c5048e838
Blamelist: Dave Abrahams <dave <at> boostpro.com>

BUILD FAILED: failed git

sincerely,
 -The Buildbot

buildbot | 20 Jun 17:52 2011
Picon

buildbot failure in BoostPro FOSSbot on el-get-23.3-win64-elisp

The Buildbot has detected a new failure on builder el-get-23.3-win64-elisp while building Boost.Modularize.
Full details are available at:
 http://bbot.boostpro.com/builders/el-get-23.3-win64-elisp/builds/0

Buildbot URL: http://bbot.boostpro.com/

Buildslave for this Build: boostpro-win08x64-2

Build Reason: scheduler
Build Source Stamp: [branch fossbot-test] c1a3f4092da5f227a8a74e82e948e87c5048e838
Blamelist: Dave Abrahams <dave <at> boostpro.com>

BUILD FAILED: failed git

sincerely,
 -The Buildbot

Dimitri Fontaine | 16 Jun 10:41 2011

Re: el-get - found the main problem

Richard Riley <rileyrg@...> writes:
> Phew. Finally. I think I found a major cause of confusion.
>
> if el-get-standard-packages is saved in custom.el then el-get-sources is
> not processed at next startup! The whole customisation area need some
> thinking about I think - it's been really hard to get all my system

Ok, that's the culprit I had in mind too: that's very recent code that
I'm still wanting to review.  My idea is now to rework it so that :

 - el-get-sources is only another recipe location
 - el-get-packages is the list of packages that you want installed
 - el-get-install/remove takes care of dealing with el-get-packages
 - el-get-packages is automatically saved using custom

So now it's simple and clear and we're always using custom, that should
mean less bugs and that's the behaviour you wanted so much I think.

I know I said to Dave I did refuse to handle things to custom interface
in a systematic way before, but after seeing how we are now I'll give up
on that.  Better setup `custom-file' to a separate place than where I
keep my `user-init-file'.

> migrated. One issue I raised was that grep+.el was downloaded as html :-
> I deleted it and reinstalled it and this time it was ok! Go figure! No
> idea what could cause that - but again there is the confusion between
> grep+.el and grep%2b.el.

I think that's about html entities in the parsing of this page:

  http://www.emacswiki.org/cgi-bin/wiki?action=index;match=%5C.(el%7Ctar)(%5C.gz)%3F%24

> Another issue is that of ordering. Can one say that one el-get object
> must be loaded after another one? 

There's now a notion of dependencies, that's part of what I need to get
reviewing.

> e.g something, I dont know what, was causing gnus to be loaded BEFORE
> el-get had loaded the nognus recipe and therefore the wrong gnus was
> being loaded. I put nognus at the front of el-get-sources, *deleted* the
> el-get-standard-packages entry in custom.el, restarted emacs and it was
> fine again.

I would have guessed that your own init sequence was responsible for
that, but the mention of custom and el-get-standard-packages leaves me
wondering.  I can't answer without proper reviewing though.

> I am still fighting with gnus - the *insinuate* functions seem not be
> loaded on the autoload chain. I'll track it down and let you know.

I guess you mean bbdb here, and here's my gnus setup about it:

 (require 'bbdb)
 (bbdb-initialize 'gnus 'message)
 (add-hook 'gnus-startup-hook 'bbdb-insinuate-gnus)
 (setq bbdb/gnus-summary-user-format-letter nil
       bbdb/gnus-summary-in-bbdb-format-letter nil)

I'm of course using nognus and el-get, and it works here™.  I add to add
those last two lines when switching to bbdb-3.0 though, IIRC.

Regards,
-- 
dim

--

-- 
To unsubscribe, send mail to el-get-devel-unsubscribe@...


Gmane