HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
emacs-mirror
emacs
Emacs Lisp2013–2026
emacs-mirror / emacs

emacs

Mirror of GNU Emacs

77Distinct people
90Mentions
0Explicit recommenders
5.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Mirror of GNU Emacs

GitHub

Where it is used

No documented product use was verified in the last source check.

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:49:33 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 year90 dated mentions

Observed mentions: 2013-07-24 03:43:47 UTC to 2026-09-14 20:36:19 UTC.

051015202013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 19 mentions; 3 submissions, 16 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC202
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 UTC202
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC909
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC615
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC817
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC523
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC817
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC19316
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC817
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC817
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC1019

What Hacker News says

8 sources
More documentation in https://github.com/emacs-mirror/emacs/blob/7cb77385d38b96377... The directory is lisp/international, that already tells something ;; CCL is used for code conversion at process I/O and file I/O for ;; non-standard coding-systems. In addition, it is used for ;; calculating code points of X fonts from character codes. And $ find /usr/share/emacs/26.3/lisp/ \! -name ccl.el.gz -name \*.el.gz -exec zgrep ccl- {} + /usr/share/emacs/26.3/lisp/obsolete/pgg-parse.el.gz:(when (fboundp 'define-ccl-program) /usr/share/emacs/26.3/lisp/obsolete/pgg-parse.el.gz: (define-ccl-program pgg-parse-crc24 /usr/share/emacs/26.3/lisp/obsolete/pgg-parse.el.gz: (ccl-execute-on-string pgg-parse-crc24 h string) /usr/share/emacs/26.3/lisp/international/mule.el.gz:specified by the attributes `:ccl-decoder' and `:ccl-
Read the rest
encoder'. /usr/share/emacs/26.3/lisp/international/mule.el.gz:`:ccl-decoder' (required if :coding-type is `ccl') /usr/share/emacs/26.3/lisp/international/mule.el.gz:VALUE is a CCL program name defined by `define-ccl-program'. The /usr/share/emacs/26.3/lisp/international/mule.el.gz:`:ccl-encoder' (required if :coding-type is `ccl') /usr/share/emacs/26.3/lisp/international/mule.el.gz:VALUE is a CCL program name defined by `define-ccl-program'. The /usr/share/emacs/26.3/lisp/international/mule.el.gz: '(:ccl-decoder /usr/share/emacs/26.3/lisp/international/mule.el.gz: :ccl-encoder /usr/share/emacs/26.3/lisp/international/mule.el.gz: (plist-put properties :ccl-decoder (car flags)) /usr/share/emacs/26.3/lisp/international/mule.el.gz: (plist-put properties :ccl-encoder (cdr flags)))) /usr/share/emacs/26.3/lisp/language/vietnamese.el.gz:;; '(ccl-decode-vps . ccl-encode-vps) /usr/share/emacs/26.3/lisp/language/ethiopic.el.gz:(define-ccl-program ccl-encode-ethio-font /usr/share/emacs/26.3/lisp/language/ethiopic.el.gz:(setq font-ccl-encoder-alist /usr/share/emacs/26.3/lisp/language/ethiopic.el.gz: (cons (cons (purecopy "ethiopic") ccl-encode-ethio-font) font-ccl-encoder-alist)) Mule was non-ASCII support in the 1990s before Unicode was a thing.
In Code Conversion Language (2019)
What's of greater importance here is not this specific security issue, but the default configuration of MIME handling in Emacs which can turn any unexpected evaluation bug -which we are likely to see more of- into remote code execution. We've had a previous Org security issue in exactly the same vein [1] and the Emacs MIME defaults are still unsafe. Of course, one can change them (non-trivial and related documentation is extremely confusing, see [2] for a possible solution) but really Emacs should not come with these defaults. The loss of on-by-default functionality such as Org fontification in email message buffers is in no way as important as being wide open to trivial remote code execution. [1] https://github.com/emacs-mirror/emacs/commit/befa9fcaae29a6c... [2] https://xristos.sdf.org/fix-gnus-mime.el.txt
In Arbitrary shell command evaluation in Org Mode (GNU Emacs)
Forever, there was a file included in stock Emacs, `spook.el`, which could be hooked up to automatically add random strings of "interesting" keywords to each of your email or Usenet messages (in signatures, or in headers like `X-Spook`). https://www.gnu.org/software/emacs/manual/html_node/emacs/Ma... Looks like copyright date of 1988: https://github.com/emacs-mirror/emacs/blob/master/lisp/play/... https://github.com/emacs-mirror/emacs/blob/master/etc/spook.... Try `M-x spook RET` in an Emacs buffer.
In The KGB, the Computer and Me – The Cuckoo's Egg Story (1990) [video]

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.