HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
franzinc
eli
Emacs Lisp2014–2019
franzinc / eli

eli

Allegro Common Lisp-GNU Emacs Interface

2Distinct people
2Mentions
0Explicit recommenders
12GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Allegro Common Lisp-GNU Emacs Interface

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year2 dated mentions

Observed mentions: 2014-12-10 01:08:56 UTC to 2019-02-10 16:05:05 UTC.

012014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101

What Hacker News says

2 sources
I just got my first developer position writing in Allegro Common Lisp, and I have to say I really enjoy the language, along with having an IDE that hooks into emacs [1][2]. For someone who is new to software development reading through the code is reasonable to do, and having a REPL at my disposal is quite nice. [1]: https://github.com/franzinc/eli [2]: https://franz.com/support/documentation/current/doc/eli.htm
In OpenLisp – A Full and Efficient ISO/IEC 13816:2007(E) ISLISP Implementation
I've been using packages for so long in CL and I never think about them. I think about other stuff. Like, how do I get format to do that thing I want it to do? I always have to look it up. Packages? They just work and work well. I think RMS is having the same problem really smart people have: if it can't be made perfect I don't want it. I regularly see this in some smart people. They reject stuff because it's not the way they want it, without them being able to articulate why they don't want it. In the early 90's I (and others) wrote not a small package and we used prefixes to avoid problems. It was ugly though, and a real package system would have been nice. For those interested, it's here: https://github.com/franzinc/eli
In RMS on why Emacs lisp doesn't have namespaces

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.